Windows 10 update problem

Hi there!
I have a dual boot system: openSuse 15.1 (KDE Plasma desktop) on /dev/sda, and Windows 10 on /dev/sdb.
Every time Windows 10 is updated, I can’t restart in openSuse if I don’t restart in Windows 10 first.
This does not happen with updates from other operating systems such as Winsows7.
Can someone tell me why this happens and if I can avoid it?
Thank you in advance!

No, this is Windows specific.

Hi
Is this Legacy or UEFI booting? If UEFI are you sharing the same /boot/efi partition, or do you have separate ones?

It’s a legacy (BIOS) boot system.

Hi
Can you post the output from (as root user);


lsblk
fdisk -l
os-prober

I really do not know about this stuff, so this is for discussion only. Not a recommendation.

Could this be something to do with Microsoft demanding control over the MBR on the primary (first) hard drive?

Is it possible to easily swap the primary and secondary drives? Hopefully you are using UUIDs and not physical drive and partition labels.

I no longer have Windows 10 installed. I installed Windows 7 instead. (That’s why I know that the problem does not happen with Windows 7.)
Anyway here is what he asked for:


adrian@octans:~> sudo lsblk     
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 931.5G  0 disk  
├─sda1   8:1    0   271M  0 part /boot
├─sda2   8:2    0   7.5G  0 part [SWAP]
├─sda3   8:3    0  93.1G  0 part /
└─sda4   8:4    0 830.7G  0 part /home
sdb      8:16   0 931.5G  0 disk  
├─sdb1   8:17   0   549M  0 part  
├─sdb2   8:18   0  99.5G  0 part  
├─sdb3   8:19   0   300G  0 part  
└─sdb4   8:20   0 531.5G  0 part /DATA
sdc      8:32   0 465.8G  0 disk  
└─sdc1   8:33   0 465.8G  0 part /backup
sr0     11:0    1  1024M  0 rom   
adrian@octans:~> sudo fdisk -l  
**Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors**
Disk model: WDC WD10EZEX-60Z
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x0009f7f7

**Device****Boot****    Start****       End****   Sectors****  Size****Id****Type**
/dev/sda1  *         2048     557055     555008   271M 83 Linux
/dev/sda2          557056   16181247   15624192   7.5G 82 Linux swap / Solaris
/dev/sda3        16181248  211492863  195311616  93.1G 83 Linux
/dev/sda4       211492864 1953525167 1742032304 830.7G 83 Linux


**Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors**
Disk model: WDC WD10EZEX-08W
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xfe37e8d0

**Device****Boot****    Start****       End****   Sectors****  Size****Id****Type**
/dev/sdb1  *         2048    1126399    1124352   549M  7 HPFS/NTFS/exFAT
/dev/sdb2         1126400  209715199  208588800  99.5G  7 HPFS/NTFS/exFAT
/dev/sdb3       209715200  838860799  629145600   300G  7 HPFS/NTFS/exFAT
/dev/sdb4       838860800 1953521663 1114660864 531.5G  7 HPFS/NTFS/exFAT


**Disk /dev/sdc: 465.8 GiB, 500107862016 bytes, 976773168 sectors**
Disk model: SAMSUNG HD502HJ  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x23ae1fa4

**Device****Boot****Start****      End****  Sectors****  Size****Id****Type**
/dev/sdc1        2048 976773167 976771120 465.8G 83 Linux


adrian@octans:~> sudo os-prober
/dev/sdb1:Windows 7:Windows:chain
adrian@octans:~> 


Hi
So in the BIOS it’s likely switched the boot order to sdb, as can be seen the asterisk (*) on both drives is bootable, I would run fdisk /dev/sdb and remove the boot flag (press a from memory) and save/exit and check the output on /dev/sdb removes the *. Fire up YaST bootloader and ensure the probe foreign os is box is checked. Then reboot and in the BIOS set the boot order to use sda first.

Thank you, malclmlewis.
I’ll try it.