Alright so I tried your solution, and it had a very interesting effect…

Now both boot partitions boot straight to Windows. Entirely skipping systemd-boot and Arch.

On the plus side it does mean that just copying Windows’s bootloader files to Arch’s bootloader partition will boot Windows no problem.

On the downside, my issue remains the same, I can’t get dual boot to work.

Both Windows and Linux (as well as their boot partitions) are on the same drive. I’ve never had problems with my PC automatically recognizing the Linux boot partitions and adding it to the boot list until this PC.

Edit: didn’t work, check new response.

So potentially that solution could work on the same drive with two separate boot partitions like I did earlier then?

Bit of a hacky way to go about it, but if it works it works.

And I guess that would potentially prevent the issue where a Windows update breaks the Linux bootloader from happening as well. Not that this has ever happened to me, but it’s an issue I’ve seen people talk about for years.

I’ll wait a bit longer to see if anyone has any suggestions/fix as to why slapping GRUB/systemd-boot in the same partition as Windows’ bootloader doesn’t seem to work, and if not or if it doesn’t work I’ll go with that.

Thank you!

Our Lord Gaben is a Benevolent God.

Weren’t there a few (ex?) employees that came forward shortly after the initial accusations surfaced and confirmed it was true?

I could be misremembering things but I also vaguely recall the initial accusations being backed up with receipts. Wasn’t there an Imgur album with a whole bunch of screenshots of conversations proving the accusations weren’t made up? Or am I confusing two completely different situations together?

I didn’t follow the situation super closely, and moved on and forgot about it until I saw this post.

Edit: looks like i was indeed wrong and confusing two separate situations.

Current owner of 4 and a half years (love the car, it’s not perfect but then again nothing is, but the company is ass and don’t even get me started on the CEO).

In my experience, Tesla will only force an update if it contains a “recall” hotfix. The car requires to be connected to a WiFi network to download the update (it won’t use the onboard data even if you pay for the premium plan).

I’ve seen people claim that the car will automatically download an update on its own if it sits ignored long enough (even without WiFi or premium data plan), but I’ve had an update sit for 3 months and my car never attempted to download/install it on its own so I’m not sure what “long enough” means.

If you really wanted to, I’m sure you could completely prevent it from phoning home by pulling a fuse or finding the data antenna and disconnecting it, but I never looked into it myself.

Edit: My car also puts a 2min countdown on the screen when you start an update, that should give anyone plenty of time to leave the vehicle.