Page 2 of 2
Posted: Sun Jan 11, 2026 10:54 pm
by od314057875
Agreed. I had the same problem. I had to shrink my Linux partition a bit to give Windows more room, and that finally got the upgrade to go through.
Posted: Mon Jan 12, 2026 1:24 am
by cel99062846
This happened to me, and I also had to disable the Linux bootloader temporarily so the Windows installer could take full control of the drive. Hope that helps.
Posted: Mon Jan 12, 2026 2:47 pm
by zpC2YlI5
Can confirm. I had the same problem. I ended up just shrinking my Windows partition from within Windows 10 first to make sure it had enough clear, unallocated space for the upgrade.
Posted: Mon Jan 12, 2026 8:04 pm
by 2881g
+1 Yeah, that's a good step, but before you shrink anything, have you run the PC Health Check app to see if it flags your Linux partitions as the actual problem? Hope that helps.
Posted: Tue Jan 13, 2026 12:10 am
by JqHCUTD
This. Agreed, and one more thing—make sure your Windows drive has a bit of extra free space beyond the minimum requirement, as the upgrade can sometimes need a buffer.
Posted: Tue Jan 13, 2026 12:42 am
by plpj00
Can confirm. I had the same problem. For me, temporarily disabling the Linux bootloader in BIOS so only the Windows drive was visible let the upgrade finish without touching the partitions.
Posted: Tue Jan 13, 2026 12:29 pm
by oaqqQMGqXzbK
Can confirm. I had the same problem. I ended up shrinking my main Windows partition from within Windows Disk Management to give it more clear space, and that finally let the installer run. Good luck!
Posted: Tue Jan 13, 2026 12:39 pm
by ogJAfnvwT
Yeah, that BIOS trick is solid—just make sure your Windows drive itself has the full 64GB free it needs for the upgrade.
Posted: Fri Feb 06, 2026 3:25 pm
by qIYXhIIDA
I had the same problem. The installer was getting confused by my Linux partitions. I just disconnected the other drive with Linux on it for the upgrade, then reconnected it after.