Originally Posted by Stone Free:
“I think you might be right, because this thread on that error code you mentioned says to have the windows partition as active - http://answers.microsoft.com/en-us/i...84a17c1?auth=1”
“I think you might be right, because this thread on that error code you mentioned says to have the windows partition as active - http://answers.microsoft.com/en-us/i...84a17c1?auth=1”
Well I'm making some progress anyway.
I marked the Windows partition as active in Disk Management, then found the computer wouldn't boot, so used the repair options on the Windows 10 installation DVD that I'd made previously (any Windows disk would have done) to put Windows back on the MBR, using a combination of the bootrec commands in Command Prompt and the start-up repair option.
Now the computer boots straight into Windows 8.1, and Windows Update is now happily downloading the Windows 10 upgrade, which it wouldn't before.
Whether it'll carry on and do the upgrade now remains to be seen.
Yes, I could have saved the downloading and used the installation disk to upgrade, but by the time I remembered that WU was already downloading.

I've temporarily lost access to the Linuxes, but I know how to reinstall grub to get them back, once I'm sure Windows 10 is installed and working.
Or I might use EasyBCD to add them to the Windows boot (might save future hassle?)
Why this computer insisted that Windows was on the MBR and the other one didn't is a mystery?
Still think it might be something to do with the UEFI BIOS, although it's not being used as such.







