Is there a way to prevent windows update replace manjaro boot loader?

I want to update windows 10 and the update will remove the grub. I know how to restore it but I don't want to do it after every time I update windows. Can I install grub in the root partition and configure windows 10 boot loader to boot from this partition?
Thanks in advance

Yes.
This is often the way grub is installed. And win/lin are both selectable from that bootloader.
But that doesnt stop windows from screwing up the EFI stub.
(which most people do not overwrite from the original windoze install ... dont know if it would matter anyways)
This is windoze being windoze. If you share data/partitions/space with it .. well .. its like sharing a room with a crazed ax murderer. There are things to expect.

Though .. I think I remember a thread here where someone outlined possible solutions to protect yourself from said psychoOS. Cant find them at the moment.

2 Likes

I remember installing Windoze on a separate disk and hitting F12 to select the boot device rather than have the bootloader handle it - if Windoze boots from its own bootloader then there's no issue right? If I were doing this now, I'd invest in a separate SSD - rather than move one to a HDD.

If you on a single disk then maybe avoid having the grub on sda1 - install with grub to a separate location then choose F12 to select which bootloader to load. Windows always goes to sda1 if I remember, but the simplest solution is to use completely separate efi and boot partitions assuming it's a UEFI setup.

My condolences with you not being able to put Windoze to rest.

2 Likes

In an attempt to avoid Manjaro gone missing - the guide to dual-boot Manjaro and Windows mentions the option to create a separate $esp for Manjaro.

1 Like

But I already installed Manjaro

I reckon it should still be doable - albeit a little extra work :grin:

In Manjaro, what show:

sudo parted -l
sudo blkid
findmnt -s
findmnt /boot/efi
efibootmgr -v

?

If I were to, heavens forbid, dual boot Windows, I would install a device like this in my computer. This way, you can physically switch off the drives used by Windows, and the drives used by Linux. You can never be too safe.

However, I am of the opinion that Windows, at least Win10, belongs in a VM, it deserves no hardware to run. The OS itself is a virus, it needs confinement.

Paranoid? Perhaps, but just because I'm paranoid, that does not mean they're not out to get me.

2 Likes

No truer words have ever been said. Though it doesn't bode well for gaming which needs a dedicated GPU.

I think the rant over Microsoft Windows deserves its own thread. Or forum?
Just saying!
:wink:

I had this issue too - it was set for a daily timeshift, depending on how much work you did since then you might do a timeshift on demand, then you can do a fresh install, fresh bootloader, and restore your timeshift.

@Marte - even in 2007 MS being the default of the world was quoted as #1 bug for Linux users :))) but some people can't do without it... but sure, for many it's essential.

1 Like

Ha ha, that's too funny. I wired in micro switches to a block off plate to control 4 hard drives just like that over 15 years ago to physically turn off my hard drives running different OS's. It worked perfectly for many years, but I no longer have need for that.

I now use a 4 Bay SSD hot swap rack that fits in a standard size CD/DVD bay. The hot swap racks can be had for $75 (on sale) and small 120 GB SSD's can be had for as cheap as $25 these days. Dual booting creates nothing but problems, the best method is to completely separate the OS's with a hardware solution.

There are even 6 bay versions that fit in a standard DVD bay:

1 Like
sudo parted -l
Model: ATA KINGSTON SA400S3 (scsi)
Disk /dev/sda: 240GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name                          Flags
 1      1049kB  524MB   523MB   ntfs            Basic data partition          hidden, diag
 2      524MB   629MB   105MB   fat32           EFI system partition          boot, esp
 3      629MB   646MB   16.8MB                  Microsoft reserved partition  msftres
 4      646MB   94.4GB  93.7GB  ntfs            Basic data partition          msftdata
 5      94.4GB  163GB   68.2GB  ext4
 6      163GB   165GB   2097MB  linux-swap(v1)                                swap
 7      165GB   240GB   75.4GB  ntfs            Basic data partition          msftdata


Model: ATA HGST HTS725032A7 (scsi)
Disk /dev/sdb: 320GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size   File system  Name            Flags
 1      1049kB  320GB  320GB  ntfs         Test Partition  msftdata
sudo blkid
/dev/sda1: LABEL="Recovery" BLOCK_SIZE="512" UUID="9AE6DDF2E6DDCE9F" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="2212421a-3ca8-42fc-bcc3-9b95356dcfed"
/dev/sda2: UUID="24E0-3396" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="089def14-5926-4e70-b335-67b3754ed424"
/dev/sda4: LABEL="Windows SSD" BLOCK_SIZE="512" UUID="AEB21B15B21AE19F" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="41eaded0-7e0d-4fcd-8353-962efe663199"
/dev/sda5: UUID="39856306-4408-4083-afe5-2ce1e509ec21" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="44bd984f-2f29-254d-b6bf-c5385410ad89"
/dev/sda6: UUID="298a412d-6b7b-44b1-815e-3496b35b7d54" TYPE="swap" PARTUUID="3ea7f97f-228e-8e43-ab0a-5827bc16a357"
/dev/sda7: LABEL="SSD" BLOCK_SIZE="512" UUID="543CE6163CE5F342" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="67b873d7-a221-43c6-9d47-573a58802b7b"
/dev/sdb1: LABEL="HDD" BLOCK_SIZE="512" UUID="48686EF1686EDCE6" TYPE="ntfs" PARTLABEL="Test Partition" PARTUUID="a4bf7324-344e-8602-e206-21ad1c89476a"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/sda3: PARTLABEL="Microsoft reserved partition" PARTUUID="8480acaa-9f54-4f55-b152-5f9957c1dfe6"
/dev/loop2: TYPE="squashfs"
findmnt -s
TARGET    SOURCE                           FSTYPE OPTIONS
/boot/efi UUID=24E0-3396                   vfat   umask=0077
/         UUID=39856306-4408-4083-afe5-2ce1e509ec21
                                           ext4   defaults,noatime
/tmp      tmpfs                            tmpfs  defaults,noatime,mode=1777
findmnt /boot/efi
TARGET    SOURCE    FSTYPE OPTIONS
/boot/efi /dev/sda2 vfat   rw,relatime,fmask=0077,dmask=0077,codepage=437,io
efibootmgr -v
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0003,0004,0002,0000,0001,2001,2002,2003
Boot0000* Network Boot: Realtek PXE B08 D00     BBS(128,,0x0).......................................................................
Boot0001* SATA HDD    : HGST HTS725032A7E630                    BBS(HD,,0x500)................-.o.......o.A.o...................................T#...
Boot0002* SATA HDD    : KINGSTON SA400S37240G                   BBS(HD,,0x500)................-.h.......h.A.h..................................._#...
Boot0003* manjaro       HD(2,GPT,089def14-5926-4e70-b335-67b3754ed424,0xfa000,0x32000)/File(\EFI\manjaro\grubx64.efi)
Boot0004* Windows Boot Manager  HD(2,GPT,089def14-5926-4e70-b335-67b3754ed424,0xfa000,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...,................
Boot2001* EFI USB Device        RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network   RC

Could you please edit your post and re-post the output of the commands as text and not screensots for better readability? Please do as follows:
Copy the terminal output as text, paste it in your reply, highlight it and click the </> button to format.

1 Like

I edited it

1 Like

I want to update windows 10 and the update will remove the grub.

Honestly, this might not actually be the case. I used to share the same ESP between Windows and other Linux operative systems and no updates to Windows ever overwrote the Grub. However there might be an slight possibility for this at the time of upgrading Windows. But I cannot tell you for sure since nowadays I actually create a separate ESP for every OS installed. I like this setup better with the benefit of eliminating any potential risk of interference.

With that said, if you feel adventurous, you could go ahead and perform the updates in your windows. You could, if you want, backup the folder Manjaro in /boot/efi to copy back if something bad happen to it during the update.

If you want you can still create another ESP on your disk dedicated to Manjaro's Grub. So the choice is yours. If you want this let me know to walk you through the procedure.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by