Page 1 of 2
Posted: Sat Jan 10, 2026 10:15 pm
by UpgradeGuru40
That error often pops up when the installer has trouble accessing the system partition. You'll likely need to temporarily disable or disconnect the Linux partition from Windows before the upgrade, then fix the bootloader afterwards. Hope that helps.
Posted: Sat Jan 10, 2026 10:18 pm
by PzZPmndx
Yeah, Agreed, that error often pops up when the installer gets confused by other partitions. A quick tip: try temporarily disconnecting or disabling the Linux drive in your BIOS before running the upgrade. Let me know if that works.
I'm trying to upgrade my Windows 10 PC to Windows 11, but I have a dual-boot set?
Posted: Sat Jan 10, 2026 10:35 pm
by 233vpr
I'm trying to upgrade my Windows 10 PC to Windows 11, but I have a dual-boot setup with Linux. The Windows 11 installer keeps failing with error code 0x80070003. It seems to detect the other partition and gets stuck. Has anyone successfully upgraded in this scenario without breaking their dual boot? I really don't want to lose my Linux install or have to redo the bootloader.
Posted: Sat Jan 10, 2026 11:02 pm
by fpAD6
Yeah, that error often pops up when the installer gets confused by other partitions. Try temporarily disconnecting or disabling the Linux drive in your BIOS before running the upgrade.
Posted: Sat Jan 10, 2026 11:39 pm
by jDzUbgDovEL
I had the same problem. I ended up using the Windows 11 Media Creation Tool on a USB drive and it bypassed the error for me.
Posted: Sun Jan 11, 2026 12:23 am
by 32fqhwjacmh
Yeah, You could also try using the Media Creation Tool to make a bootable USB and upgrade from within Windows 10 that way. Another option is to check your bootloader; sometimes repairing it with a tool like EasyBCD after the upgrade can help.
Posted: Sun Jan 11, 2026 12:31 am
by dXZHhogUwFF
Can confirm. This happened to me too. I had to temporarily disconnect my Linux drive from the motherboard before the upgrade would go through.
Posted: Sun Jan 11, 2026 2:39 am
by 233vpr
Thanks so much! That fixed it!
Posted: Sun Jan 11, 2026 3:01 am
by IZaQjNi
+1 Oh, that's great to hear—what ended up being the solution for your setup?
Posted: Sun Jan 11, 2026 3:24 am
by fj6Jrk606ca
Glad I'm not alone. Same issue on my PC.