F5F Stay Refreshed Software Operating Systems Windows 7 on NVMe drive continues to restart repeatedly after chkdsk completes.

Windows 7 on NVMe drive continues to restart repeatedly after chkdsk completes.

Windows 7 on NVMe drive continues to restart repeatedly after chkdsk completes.

Pages (2): Previous 1 2
_
_Firestorm
Junior Member
13
07-05-2016, 07:19 PM
#11
Thank you for the update! The command used was correct. When the OS-partition was detected as E, it booted from the USB drive. After checking Diskpart, it showed the partition with Windows active. The system failed to start due to a specific error code 0xc0000001. I noticed that the boot process ended on C: despite having D: as the USB stick.
_
_Firestorm
07-05-2016, 07:19 PM #11

Thank you for the update! The command used was correct. When the OS-partition was detected as E, it booted from the USB drive. After checking Diskpart, it showed the partition with Windows active. The system failed to start due to a specific error code 0xc0000001. I noticed that the boot process ended on C: despite having D: as the USB stick.

R
Rony2003
Junior Member
14
07-11-2016, 01:12 PM
#12
So if everything was set right, it seems both the bootloader setup and the actual files are faulty. You might try using a working Windows installation from another OS version—like Windows 7 or later. Test it with Windows 8 by removing the boot folder from your Windows 7 drive and replacing it with the new one. Once back in Windows 10, locate the installation partitions for both systems. I’ll refer to your Windows 7 partition as C and the other as H. You mentioned you didn’t see a boot folder during testing; it’s probably just overwritten. Run the command `bcdboot h:\windows /s c: /f BIOS` to add the boot entry for the alternative Windows on your C drive, which will also copy the bootloader from H to C during the reboot.
R
Rony2003
07-11-2016, 01:12 PM #12

So if everything was set right, it seems both the bootloader setup and the actual files are faulty. You might try using a working Windows installation from another OS version—like Windows 7 or later. Test it with Windows 8 by removing the boot folder from your Windows 7 drive and replacing it with the new one. Once back in Windows 10, locate the installation partitions for both systems. I’ll refer to your Windows 7 partition as C and the other as H. You mentioned you didn’t see a boot folder during testing; it’s probably just overwritten. Run the command `bcdboot h:\windows /s c: /f BIOS` to add the boot entry for the alternative Windows on your C drive, which will also copy the bootloader from H to C during the reboot.

M
machino25
Member
50
07-11-2016, 06:25 PM
#13
You're welcome for your assistance. A functional W7 was achieved, and the additional drive was connected. The commands were followed, and a reboot was performed. However, the system only reached: "The user has accepted that it won't boot again and we have extracted all files from the drive."
M
machino25
07-11-2016, 06:25 PM #13

You're welcome for your assistance. A functional W7 was achieved, and the additional drive was connected. The commands were followed, and a reboot was performed. However, the system only reached: "The user has accepted that it won't boot again and we have extracted all files from the drive."

S
SirDragon_
Member
51
07-11-2016, 07:02 PM
#14
Now considering this, it seems Windows 7 might not require copying anything from E to C since files didn’t need updating to run it. In contrast, Windows 8 did? So if you still have that disk, trying a newer version like Windows 8 or 10 could help (just a guess).
S
SirDragon_
07-11-2016, 07:02 PM #14

Now considering this, it seems Windows 7 might not require copying anything from E to C since files didn’t need updating to run it. In contrast, Windows 8 did? So if you still have that disk, trying a newer version like Windows 8 or 10 could help (just a guess).

Pages (2): Previous 1 2