Windows Update Removes Dual-Boot Configuration

rAIner-linux

New Member
Joined
Aug 5, 2023
Messages
18
Reaction score
6
Credits
172
It looks like a windows-update has removed the dual boot configuration where I also had a Mint distribution installed.

Now, I have two questions for you:
1. Is anybody aware of existing law suites agains Microsoft regarding this behaviour?
2. Are there any honourable lawyers in this forum, who are happy to share ideas and resulting profits?

And a third bonus question would be:
3. Who can help me to get access to my Linux files. My current situation is:
a. My dual-boot windows/mint laptop refuses to boot with Linux (Invalid signature detected. If this error persists, seek technical assistance.) So, some of you may have correctly understood: yes, I was running a Mint distribution on this laptop, which I had not verified.
b. I have no other Linux system in my LAN
c. I have two old Macbooks, the newer one is from 2015 and is running macOS Monterey 12.7.6
 


Which Linux Mint is installed. version.....LM21.3 ?,,,,,22.1..? etc
 
Read this from top to bottom:

Use the usb stick with Linux Mint XX on it that you first used to install.
Boot the pc to that usb stick. Then look for 'Boot Repair' in the menu... Open it....just click through...the latest version is not important It will scan...may take a few minutes
Click 'no' if it offers to modify the mount point of any EXTRA drive/s you have installed. You only want to fix the boot for the drive your OS is installed on.
It will scan again.
It will then come to a smallish screen saying :
Repair the boot of the computer
Click on recommended repair
It will do its thing automatically

Anything on screen, after it has finished the repair is window dressing....it is unnecessary to write stuff down etc etc etc
Just REBOOT. Allow the pc to do its normal boot up routine

That should do it.

EDIT TO ADD: If you running Linux Mint 22, boot repair is already installed on it.....you would not need to boot to a usb stick....Just type boot repair into the menu and then follow the steps I outlined above.

Also, this : https://help.ubuntu.com/community/Boot-Repair
 
Thanks Condobloke,

wow, that sounds like a pretty precise and therefore probably working solution for my third, i.e. bonus, question. Thanks a lot.
 
Which Linux Mint is installed. version.....LM21.3 ?,,,,,22.1..? etc
The USB stick, used to install Linux, reads Mint 21.3 Cinnamon.But after the initial installation, I have allowed updates... so I am not sure what version of Mint actually is installed on that laptop.
 
You can't access that Linux install at all....

Ok....the download from the link below, "attached" to a usb stck with either rufus or balena etcher should do the trick.....Very similar to the way you used to make the usb stick that you have.

BUT
before you try the above....boot your pc to that usb stick you already have.
When you have it booted......click on menu, and type in BOOT REPAIR.
If you are lucky it will be installed and available from there.

IF NOT.... : https://sourceforge.net/p/boot-repair/home/Home/
A short distance down the page...looks like the screenshot below:
1745725862552.png

In the above scenario, you would be booting to the usb stick you already have....then installing boot repair to that usb stick (assuming it is not in the menu as described above).....then using Boot Repair as described in my blurb described in post #3
 
It looks like a windows-update has removed the dual boot configuration
Don't panic, this is a well-known side effect of some Windows updates, and has been going on for years,

for Debian based distros, start Linux by using the boot menu [you may need to disable secure boot first] open a terminal and enter

sudo update-grub

followd by a full update sudo apt update && apt upgrade -y then reboot


it should now work you can now re-set secure boot in windows if you wish
 
Don't panic, this is a well-known side effect of some Windows updates, and has been going on for years,

for Debian based distros, start Linux by using the boot menu [you may need to disable secure boot first] open a terminal and enter

sudo update-grub

followd by a full update sudo apt update && apt upgrade -y then reboot


it should now work you can now re-set secure boot in windows if you wish
Hi Brickwizard,

I am not panicing at all. I have already decided to install Linux as a single boot configuration so I will not have to face that problem again. The recovery of my Linux files is just a nice-to-have.

But I am really serious about the lawsuit... I think if Microsoft can be forced to easier allow other search engines than bing, Microsoft can also be forced to retain existing boot configurations rather than replacing them with Windows stuff.

It is simply unacceptable that an update of one OS on a computer is basically switching other OSs off.
 
@rAIner-linux , g'day from DownUnder.

Question for you since you are a Mint User. Were you taking Timeshift snapshots?

If so, do you remember if they included Home or not?

I am thinking that if you have been doing so, then the simplest solution of all may be to run the Live Mint USB stick, launch Timeshift, navigate to where you stored your snapshots, and choose Restore.

If, however, you were not including Home in the snapshots, then you may lose your settings, Documents &c.

Let me know, and allow for my being east coast Australia.

... I think if Microsoft can be forced

I can dream.

It is simply unacceptable that an update of one OS on a computer is basically switching other OSs off.

Totally agree. I "divorced" MS in September 2014 and haven't looked back.

Chris Turner
wizardfromoz
 
Problem with windows updates is windows always thinks it the only OS on a machine and overwrites the boot sector. You'll have to go in and reinstall grub/UEFI boot from the live linux usb. These pages may be of help
Good Luck. I'm not a lawyer but don't think your lawsuit would go anywhere as you most likely agreed to this behavior when to accepted Window in the first place.
 
Some years ago I had this problem with win 8 updates. The second link from kc1di was very useful that time, and I think I used the command bcdedit /set {bootmgr} path \EFI\ubuntu\grubx64.efi with some adaptations. See also:

I have tried boot repair a couple of times. Once with success; once with following disaster, with new installation of both win10 and Linux. But with no data loss - I am using linux :-)
 
I no longer recommend boot repair. as it sometimes does not repair but makes things much worse.
 
Is anybody aware of existing law suites agains Microsoft regarding this behaviour?

For better or worse, that one cracked me up. I can relate a bit to your pain, but I haven't used MSFT's software for a long time.

Anyhow, you don't own Windows. You license it, even if you got it for free. (Technically, we don't own Linux, but the FOSS licenses ensure we get to continue using it.) I can assure you that MSFT has this covered in their usage agreement. If nothing specific is mentioned, it'd be covered in their bit where they disclaim responsibilities for any harms committed.

So, no... Nobody has sued or this.

To be fair, the bit about not being responsible for harm has been fought in courts before. If you can prove negligence and financial harm, you might be able to spend millions of dollars to take MSFT to court. Your odds or winning are pretty low, even with the best lawyers you can hire. The courts are usually pretty much in agreement regarding indemnification.

I'm not a lawyer. I am not your lawyer. None of this is legal advice.

I have read and had explained to me in great detail many contracts. In my opinion, your contract with MSFT (when you agreed to their terms of service/use) would not make it far in the courts. My advice is to just fix it by telling GRUB to update.

Also, for what it's worth, I've never had boot repair break anything - but I've not needed to use it in quite a while. If you have backups, you can try that.
 


Follow Linux.org

Members online


Top