Lost Windows 10 boot

So, after ages working exclusively with Windows environment, I decide to get back and mess around in Linux systems. I opted for OpenSuse 15.3 and so far so good.
The problem is, I still need to work in Windows, but, as a good noob, I did something wrong when deciding the partitions scheme. I opted for what the installer recommended.
What I know is, I don’t know anymore what I’m doing.

My first choice would be restore the Windows boot to get back to that instalation.

I found some articles, that gave me a little hope to achieve what I want. How to propperlly dual-boot (https://unix.stackexchange.com/questions/316602/how-to-properly-dualboot-opensuse-and-windows-10) and (http://woshub.com/how-to-rebuild-bcd-file-in-windows-10/) both gave me a shred of hope to achieve what I want to. regain access to my Windows installation and keep OpeSuse installed.

I prefer to avoid reinstalling everything.

Is it possible?


The most likely problem is a disagreement on whether to use UEFI booting or BIOS/MBR booting. Unless both Windows and Linux boot the same way, you won’t get a grub menu entry for Windows.

Post the output from:

fdisk -l

(run that as root, and post the output with CODE tags.

Thanks for the reply.
I was afraid that the problem was that.

Sorry my ignorance. What do you mean “CODE tags”?
I don think is anything very critical to security so, here it go.

thiago@localhost:~> sudo fdisk -l
[sudo] password for root:
Disk /dev/sda: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: ST3250312AS
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: 0xfc083a51

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 1026047 1024000 500M 7 HPFS/NTFS/exFAT
/dev/sda2 1026048 203816884 202790837 96.7G 7 HPFS/NTFS/exFAT
/dev/sda3 203816960 204799999 983040 480M 27 Hidden NTFS WinRE

Disk /dev/sdb: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000DM006-2DM1
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: gpt
Disk identifier: A6AAA680-E5D1-436A-B518-287E704C2968

Device Start End Sectors Size Type
/dev/sdb1 34 32767 32734 16M Microsoft reserved
/dev/sdb2 32768 3828910079 3828877312 1.8T Microsoft basic data
/dev/sdb3 3828910080 3829434367 524288 256M EFI System
/dev/sdb4 3829434368 3902834687 73400320 35G Linux filesystem
/dev/sdb5 3902834688 3907029134 4194447 2G Linux swap

Partition 1 does not start on physical sector boundary.

Again, sorry my ignorance if it is going hard to read…

Best to enclose output between [noparse]


[/noparse] tags (refer to the ‘#’ button in advanced forum editor)…like this…

~> sudo /sbin/fdisk -l 
[sudo] password for root:  
**Disk /dev/sda: 20 GiB, 21474836480 bytes, 41943040 sectors**
Disk model: VBOX HARDDISK    
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: gpt 
Disk identifier: 71817168-6290-4A4E-A3FA-0976BA386E47 

**Device****   Start****     End**** Sectors****Size****Type**
/dev/sda1      2048    18431    16384   8M BIOS boot 
/dev/sda2     18432 37746687 37728256  18G Linux filesystem 
/dev/sda3  37746688 41943006  4196319   2G Linux swap

Your output would have been easier to read with CODE tags.

From what I can see, “/dev/sda” is using standard DOS partitioning, and it looks as if Windows is there.

The second drive ("/dev/sdb") is using GPT partitioning and UEFI booting. However, there is something a bit unusual. You have a small 16M partition starting at sector 34. That’s uncommon, but allowed.

It looks as if Windows is on the first drive, so booting with BIOS/MBR, while linux is on the second drive and likely booting with UEFI.

I’ll suggest you go into BIOS settings, and see if you can tell the BIOS to boot the first drive with BIOS/MBR booting, The BIOS might call that CSM (Compatibility Support Module). If you can switch it to that mode, you can probably boot Windows, but perhaps you cannot boot linux unless you switch it back. I’m suggesting you test this. If that’s the issue, then you can switch linux to booting with CSM, and that will solve your problem.

No that 16MB is normal for Windows 10, type 0c01 MS Reserved, it use to be 128MB.

Thanks deano_ferrariI got it waht you asked.

Thanks nrickert. Through BIOS, I was able to start Windows and grab a couple files to finish my backup.

Now, back to scracth and rebuild everything in the proper way.

Thanks a lot guys.