This entry in your BIOS implies that HDD1 (Hard Disk Drive 1) which might be your new SSD contains an EFI (Extensible Firmware Interface) boot partition.
UEFI B001:
HDD1-Windows Boot Manager
This boot partition is usually hidden from the user (no drive letter) but can be viewed after you've booted into Windows using the Disk Management tool or other drive management programs.
On the Windows 10 computer I'm using right now, this EFI boot partition is a mere 100MB in size, but it forms a critical part of the boot up process.
If your BIOS is set to 'Legacy Mode' only, also known as CSM (Compatibility Support Mode), the computer will ignore this EFI boot partition and the computer will not boot into Windows.
https://superuser.com/questions/1284392/what-exactly-is-uefi-with-csm-boot-mode
If you check through your BIOS, you should find an option to enable UEFI booting in addition to, or instead of Legacy/CSM.
Some BIOS screens allow you to enable both UEFI and Legacy/CSM at the same time. In some cases you can set the order, e.g. Legacy/CSM boot first, UEFI second, or vice versa.
I use these options on older computers with a mix of Windows XP (released before UEFI was invented) and Windows 7/10. If I set the BIOS to UEFI only, I cannot boot into my Windows XP drive. If I set the BIOS to Legacy/CSM only, I won't be able to boot into my Windows 10 drive if it relies on an EFI boot partition. Catch 22. On modern systems, the normal setting is UEFI.
Chances are your old hard disk and new SSD both have a small (hidden) EFI partition, requiring the UEFI boot option to be set in the BIOS, but somehow your boot settings have got scrambled.
We need to stop the BIOS from attempting to boot from a PXE server. It's quite possible network booting is a 'fall-back' option in the BIOS, if it fails to find a bootable disk drive, bootable USB memory stick, bootable optical disk, etc. In other words, the BIOS may have tried to boot from your SSD, failed dismally, worked its way down the list of various options until it found PXE boot, tried that and finally admitted defeat.
The first thing to do is enable UEFI. Make it higher priority than Legacy/CSM. N.B. If you're running Windows 7 or 10, there's a vague chance your drive (HHD or SSD) was setup with UEFI disabled in the BIOS, in which case there won't be a small EFI partition on the disk (I'm pretty sure I have a few of these setups). In this case, Legacy/CSM would have to be enabled.
Second, if you have more than one disk installed, move the SSD up to the top of the list.
Third, you may need to enable Windows Boot Manager for the SSD (assuming this is one of the options allowed).
On one of my computers, I can see two different Windows Boot Manager options in the BIOS. One of them is the EFI partition on my M.2/NVMe drive, the other is the EFI partition on my backup SATA SSD, in case the M.2 drive stops working.
It can all get horribly confusing, so the best thing to do is disconnect all disk drives (HDD, SSD, optical, USB) apart from your main boot drive (new SSD) and play around in the BIOS.
If you've never successfully booted from the SSD, fit the old HDD in its place and see if you can get that to work again.
If you cloned the HDD to the SSD but forgot to disconnect the HDD before restarting from the newly cloned SSD, the boot partition may still be located on the HDD, with the remainder of the OS on the new SSD. When you disconnect the HDD, the computer will no longer be able to boot Windows from the SSD, because the boot partition has disappeared.
I hope this helps.
Facebook
Twitter
Instagram