Stuck on step 2.5 (Guide to get out of the Boot Loop)

[louga31]

Hello,

When I run EnableCKS.exe, everything goes well, and it says:

[+] Succeeded to open "HKLM\SYSTEM\Setup".
[+] Succeeded to set "CmdLine" value.
[+] Succeeded to set "SetupType" value.

Reboot is required. Are you ready to reboot? [y/N]

After that, when I press y to reboot, my PC enter a boot loop state with a little CMD opemening eveytime (actually its EnableCKS.exe with -setupmode argument).
In this cmd, this text is written:

[+] Succeeded to open "HKLM\SYSTEM\CurrentControlSet\Control\ProductOptions".
[+] Succeeded to get size of "ProductPolicy" value. SIZE: 57804 (0x0000E1CC)
[+] Succeeded to set "ProductPolicy" value.

From what I understand, it should work but soon after that, PC reboot and start again.

The only way I found to reboot the PC successfully was to set the CmdLine value to empty and SetupType to 0 (The values put by EnableCKS.exe) through recovery environment.

Do you have any idea on how to solve this issue ?
Thanks in advance

louga31

[louga31]

1. You need to boot a live windows or use the Windows installer USB key (you can also use the windows recovery environment if you can still boot on it)
2. Open RegEdit (Use the CMD for that)
3. Load the installed Windows HKLM/System Hive (File->Load Hive...->Select Windows\System32\config\SYSTEM)
4. Change these keys in the opened hive:

• Hive/Setup/CmdLine (Clear it's value)
• Hive/Setup/SetupType (Set this one to 0)

5. Try to reboot Windows, it should work (don't hesitate to ask if it still doesn't works)

[ownageontoast]

1. You need to boot a live windows or use the Windows installer USB key (you can also use the windows recovery environment if you can still boot on it)
2. Open RegEdit (Use the CMD for that)
3. Load the installed Windows HKLM/System Hive (File->Load Hive...->Select Windows\System32\config\SYSTEM)
4. Change these keys in the opened hive:

• Hive/Setup/CmdLine (Clear it's value)
• Hive/Setup/SetupType (Set this one to 0)

1. Try to reboot Windows, it should work (don't hesitate to ask if it still doesn't works)

Literally just got it myself then noticed that you replied, thank you. This is the exact method that I used.

[louga31]

At least, it can serve as a guide for future users that get stuck (I will update the title to reflect the semi-solved state)

[ownageontoast]

At least, it can serve as a guide for future users that get stuck (I will update the title to reflect the semi-solved state)

That is a great idea, thanks again and for the speedy replies.

Also for anyone still stuck and doesn't understand the instructions above, this is the guide I used to get into the registry files for my hard drive.

https://www.techrepublic.com/blog/windows-and-office/use-the-recovery-drive-command-prompt-to-edit-the-registry-or-recover-data/#postComments

[Oragi]

1. You need to boot a live windows or use the Windows installer USB key (you can also use the windows recovery environment if you can still boot on it)
2. Open RegEdit (Use the CMD for that)
3. Load the installed Windows HKLM/System Hive (File->Load Hive...->Select Windows\System32\config\SYSTEM)
4. Change these keys in the opened hive:

• Hive/Setup/CmdLine (Clear it's value)
• Hive/Setup/SetupType (Set this one to 0)

5. Try to reboot Windows, it should work (don't hesitate to ask if it still doesn't works)

I accidentally used it together with valinet/ssde and to get out of the boot loop I had to delete these 2 keys too, in addition to setting CmdLine and SetupType

Hive\ControlSet001\Services\ckspdrv
Hive\ControlSet001\Services\ssde

[zcubedmusic]

Kind of late to the party here but I am having the same issue and tried the hive fix you guys mentioned but I am still stuck in a boot loop. The keys appear to reset themselves when I reboot and I'm not sure what else I can do to get out of this one. I've tried disabling fast boot because I heard that can cause registry files to reset sometimes but any other tips? I am accessing via the recovery menu btw if that makes any difference.

Edit: False alarm, I decided to just do a system restore I had made earlier today and that seemed to work for now. I'll have to come back to this kernel business when I have more time to troubleshoot lol.