If it is not green, you should click search button and browse to the efi partition.on winntsetup the "EFI PART" was red instead of green.
I dont think it mattered in your case becuase the boot files on the efi part created by your earlier installation seem to point at the windows partition.
There is a different issue in your case.
Does win7 work fine on a sata ssd or a mechanical hd on that same machine?
i dont have a sata ssd to try but im am using windows 7 right now on a mechanical drive!
Did you try installing something else to your new nvme, win10 for example ?
checking if there is problem with your new nvme
I have come across a bsod recently.
diskgenius warned of damaged efi partition and offered to fix it, and it worked fine after fixing, no more bsod.
Worth having a look at the nvme disk with diskgenius just in case
https://www.diskgenius.com/download.php
i can install windows 8.1/10/11 onto it just fine, i have been using the ssd for about a year now, but ill try diskgenius!
diskgenius did not find anything wrong
- - - Updated - - -
what should i do next?
Last edited by casey7; 08 Jan 2022 at 18:30.
If your win7 on the mechanical hd has the nvme updates and can see the nvme disk - you could try migrating the os from there onto the nvme.
The mechanical disk will have to be gpt partition style to do it this way.
Click os migration in diskgenius top pane , select the target disk (the nvme) , select "hot migration"
it is quite obvious, screenshots here
select os migration
select target disk
accept the existing partition sizes, or optionally change them
click "hot migration"
it has failed, i dont really know why.
Neither do I. It happens when using win7 bcdboot.exe across modes (e.g. bios>efi) , but it shouldnt happen in the same mode.
You can try and update the boot parameters manually
there is no /f uefi switch in win7 bcdboot.exe , so use the one below
bcdboot-10586.zip
copy the device path of the esp partition
admin cmd prompt:
bcdboot winpartitionletter:\windows /s device path /f uefi
example:
bcdboot m:\windows /s \Device\HarddiskVolume6 /f uefi
that creates the boot critical files and the boot menu entry for windows on partition m on the esp partition \Device\HarddiskVolume6
Last edited by SIW2; 08 Jan 2022 at 23:51.
hello, i redid the migration while in PE and this time it completed it successfully but still didnt make a entry to boot into, so i will use your tutorial to add one myself :)
hopefully that will do it.i will use your tutorial to add one myself
I dont know why you have had that difficulty. I havent got the same hardware to test it here, closest thing I have is a 365 motherboard. Never had any problems with win7 on it.
hi SIW2,
great news! it worked! it was hard to tell if it booted into the SSD but i was able to figure it out
my only issue is the user profile it loads into seems to be the one from the hard drive instead of the SSD, so everything points toward the hard drive. I would like to have my hard drive clean a nd im afraid of breaking the SSD installation, i am not sure what to do.
one idea is to swap the drive letters so when it points to C which is the hard drive, it actually points to the SSD then, leaving the hard drive unused. i am currently in the winPE but i dont actually know how to swap drive letters or if this is the correct solution, please advise and thank you very much.
as for why it bsod' before, my only guess is that maybe because installation wasn't finished yet that it wouldnt load the updates in therefore it couldn't apply the hotfix, but i honestly don't know. im just happy to have win7 on modern hardware finally.
Quote
