Bios error

[Lucky]

I just upgraded my motherboard  cpu and video card. Now when I boot up I get this error

an operating system was not found.  Try disconnecting any drives that contain an. Operating qsystem 

press Carl+alt+del to restart

anyone seen this error and how do I fix it

 

Edited March 7, 2022 by Lucky

[Svsmokey]

If you are running an OEM version of Windows , which is one-time use , it is seeing itself installed on a new computer . Get a new key , and reinstall via creating a Windows Media usb stick .

[CptBligh]

Upgrading a motherboard is pretty much always going to require a reinstall of Windows

[SkateZilla]

make sure the boot sequence is correct,

But if the Windows was installed in UEFI or MBR Mode on one PC and moved to another that is using a different mode it will not see the partitions.

[FR4GGL3]

2 hours ago, SkateZilla said:

But if the Windows was installed in UEFI or MBR Mode on one PC and moved to another that is using a different mode it will not see the partitions.

Pretty much this. If you enabled UEFI Mode and have Windows on a GPT Storage (most People did because they wanted to use Resizable Bar / SAM), make sure that your new MoBo is in UEFI Mode.

[BitMaster]

vor 6 Stunden schrieb SkateZilla:

make sure the boot sequence is correct,

But if the Windows was installed in UEFI or MBR Mode on one PC and moved to another that is using a different mode it will not see the partitions.

 

vor 4 Stunden schrieb FR4GGL3:

Pretty much this. If you enabled UEFI Mode and have Windows on a GPT Storage (most People did because they wanted to use Resizable Bar / SAM), make sure that your new MoBo is in UEFI Mode.

Likely the above.

 

You can move an install around many different boards and even architectures ( Intel vs AMD ) and it will work. I will perform a driver(s) install on first boot, then reboot and done.

It is wise to deinstall things the new board does not have before you do the change and it may pay back to place the driver files on the desktop so you have LAN drivers ready if you need that. I have done this many many times and if you do it right there is no drawback. A fresh install has it's hurdles for many, so this approach is indeed a valid one.

 

Make sure you pick the right drive to boot from, in wcs you have to try each one. But before this can happen, make sure as said above that the UEFI mode is set properly. It will not boot if incorrect but this can be easily corrected in Bios.

 

Just went through s similar thing last weekend, HP ProL server refused to accept the new NAS drives....and refused Ubuntu server install....3h later it booted, with Sata at AHCI, SAS off, etc... Just don't give up

[72westy]

Upgrading the motherboard will require reinstall of the OS due to the new motherboard being completely different than previous one.

[BitMaster]

No, the times of Windows HAL are long gone. Since Windows 7 ( maybe Vista too, not sure ) you can move an install. A clean install is always better if you are able to and also  have the time. If it needs to be quick & dirty you can move the install. You can since then also take virtual machines across Intel-AMD barrier, a thing that wouldnt work before with Windows as the VM still sees the architecture underneath. XP would not boot on AMD if it came from an Intel machine. I often move between Intel and AMD have zero issues with VMware and I sometimes carry an install over for certain reasons that void an immediate clean install.

 

Edited March 9, 2022 by BitMaster

[SkateZilla]

Windows 7 started the Linked Microsoft Account Activations,

But depending on the license you only get so many activations now with OEM, where as before you only received 1 Activation, the license was not transferable once activated.
Retail Licenses can be deactivated and transferred.

 

[BitMaster]

Am 10.3.2022 um 03:54 schrieb SkateZilla:

Windows 7 started the Linked Microsoft Account Activations,

But depending on the license you only get so many activations now with OEM, where as before you only received 1 Activation, the license was not transferable once activated.
Retail Licenses can be deactivated and transferred.

 

It's even more complicated than that. If you i.e. use a Retail Lic for VMware it is stuck in the virtual world, at least mine cannot be transferred to "real" hardware. bound machines. I can move them between Hyper-V, VMware and VirtualBox...but not to real HW. 

I just moved an OEM 10 to a new aftermarket Board and upgraded it to 11, which worked despite I thought "OEM, that may go south!" I needed to tiue the OEM 10 to a MS account to do so,

if you forget that step before doing the move you have no chance activating anything.

Edited March 11, 2022 by BitMaster

[SkateZilla]

13 hours ago, BitMaster said:

It's even more complicated than that. If you i.e. use a Retail Lic for VMware it is stuck in the virtual world, at least mine cannot be transferred to "real" hardware. bound machines. I can move them between Hyper-V, VMware and VirtualBox...but not to real HW. 

I just moved an OEM 10 to a new aftermarket Board and upgraded it to 11, which worked despite I thought "OEM, that may go south!" I needed to tiue the OEM 10 to a MS account to do so,

if you forget that step before doing the move you have no chance activating anything.

 

Retail licenses need to be deactivated before moving.

Moving from Virtual Machine to Virtual Machine isnt changing your hardware so it assumes it's the same system.

[BitMaster]

The way I do it is recall the license via the MS control page that opens when you click "troubleshoot" the activation with "I have recently changed my hardware". Among the devices listed I pick the one I want to use the license from and choose " I do not use this HW anymore ( or similar, it's german on my end ).

When moving between my AMD and Intel machine the CPU changes and I doubt MS sees this as "1" machine. Nonetheless, I can move them freely between those 2 rigs.

I could reactivate all my Win10 when I shortly used Hyper-V but not the 2016 SRV, it also allowed me to re-reactivate them on VMware again once I found out that it wont take my 2016 into the Hyper-V world. 

Anyway, it's still a hairy process and sometimes it just won't allow you to activate a machine for no obvious reasons.