Windows 10 stuck at kernel boot, spinning circle

Check if the recovery environment recognizes the windows installation partition as C:.
Otherwise change C: in the DISM command and in the last part of the following commands with the correct drive letter.
I.e., the drive letter in the second and last config path (C:\WINDOWS\system32\config).
(The first command could return an error)
Code: 
reg load HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/EFI/Microsoft/Boot/BCD C:\EFI\Microsoft\Boot\BCD
reg load HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/system32/config/COMPONENTS C:\WINDOWS\system32\config\COMPONENTS
reg load HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/system32/config/DEFAULT C:\WINDOWS\system32\config\DEFAULT
reg load HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/system32/config/DRIVERS C:\WINDOWS\system32\config\DRIVERS
reg load HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/system32/config/SAM C:\WINDOWS\system32\config\SAM
reg load HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/system32/config/SECURITY C:\WINDOWS\system32\config\SECURITY
reg load HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/system32/config/SOFTWARE C:\WINDOWS\system32\config\SOFTWARE
reg load HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/system32/config/SYSTEM C:\WINDOWS\system32\config\SYSTEM
reg load HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/system32/smi/store/Machine/schema.dat C:\Windows\system32\smi\store\Machine\schema.dat
reg load HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/Default/NTUSER.DAT C:\Users\Default\NTUSER.DAT

DISM /image:C: /cleanup-image /revertpendingactions
If dism still fails, re-try with the backslash (after C:)
Code: 
DISM /image:C:\ /cleanup-image /revertpendingactions
 
Last edited:
I ran all those commands in the provided order. I attached log file
Check if the recovery environment recognizes the windows installation partition as C:.
Click to expand...
I think it does recognize it. There is a mention of C:\Windows in the SrtTrail log
 

Attachments

I had some registry backups which I made after the system got corrupt(yeah...) Something was wrong with the SOFTWARE hive. After I restored that backup, DISM works.

I ran the revertpendingactions command, it said it completed successfully.

I ran the command second time to generate some logs
 

Attachments

It said it can't repair.

It doesn't boot. Right after POST, it tries to boot. There is a loading circle, but it eventually freezes

Here is a latest SrtTrail
 

Attachments

Let's try to get some more logs.
The first command (should) create the SomeLOGS folder on c:.
You can choose another path of your choice, obviously.
After you created the logs, zip them up and upload the file.
Code: 
md "c:\SomeLOGS"
c:\windows\system32\bcdedit > "c:\SomeLOGS\bcdedit.txt"
c:\windows\system32\msinfo32 /nfo "c:\SomeLOGS\msinfo32.nfo"
c:\windows\system32\systeminfo > "c:\SomeLOGS\systeminfo.txt"
c:\windows\system32\dxdiag /whql:on /t "c:\SomeLOGS\dxdiag.txt"
c:\windows\system32\wevtutil epl system "c:\SomeLOGS\system-event-viewer.evtx"
c:\windows\system32\wevtutil epl application "c:\SomeLOGS\application-event-viewer.evtx"
(c:\windows\system32\driverquery /fo table && c:\windows\system32\driverquery /fo list && c:\windows\system32\driverquery /fo csv && c:\windows\system32\driverquery /si) > "c:\SomeLOGS\driverquery.txt"

In the meanwhile, you could try a chkdsk c: /v
And if it says there are errors, post the result.
 
It has got events from the recovery environment. o_O

Code: 
copy C:\Windows\System32\winevt\Logs\system.evtx c:\SomeLOGS
copy C:\Windows\System32\winevt\Logs\application.evtx c:\SomeLOGS
Zip them up then send the file.


Anyway...

MSinfo32 shows Size 1.63 TB (1,790,026,240,000 bytes) and Free Space 33.28 GB (35,735,953,408 bytes).
I hope you have already saved the data (that you need) somewhere else.
Microsoft calculator says that the percentage of free space on your WD Blue SN570 NVMe SSD (WDS200T3B0C - M.2 2280 - PCIe Gen3 x4 - NVMe v1.4) is precisely 1.9963927125448172201095778350154% (ok, about 2%).
To give you a real example, my system partition size is (just under) 100GB and the free space is 53.1GB (i.e., about 53% - I recently increased the pagefile to 12GB).
A simple Google search can show you that this percentage should be no less than 5% according to the most extreme people, 10-25% according to everyone else.

Maybe it's time to free up some space on that SSD...? :unsure:
 
Last edited:
xilolee said:
It has got events from the recovery environment. o_O

Code: 
copy C:\Windows\System32\winevt\Logs\system.evtx c:\SomeLOGS
copy C:\Windows\System32\winevt\Logs\application.evtx c:\SomeLOGS
Zip them up then send the file.


Anyway...

MSinfo32 shows Size 1.63 TB (1,790,026,240,000 bytes) and Free Space 33.28 GB (35,735,953,408 bytes).
I hope you have already saved the data (that you need) somewhere else.
Microsoft calculator says that the percentage of free space on your WD Blue SN570 NVMe SSD (WDS200T3B0C - M.2 2280 - PCIe Gen3 x4 - NVMe v1.4) is precisely 1.9963927125448172201095778350154% (ok, about 2%).
To give you a real example, my system partition size is (just under) 100GB and the free space is 53.1GB (i.e., about 53% - I recently increased the pagefile to 12GB).
A simple Google search can show you that this percentage should be no less than 5% according to the most extreme people, 10-25% according to everyone else.

Maybe it's time to free up some space on that SSD...? :unsure:
Click to expand...

:D I attach correct logs from the locations you provided

About the space on the drive - I have 195,31 GB of unallocated space on that drive :D I was told that this way space will be reserved for the drive to use so it won't choke on itself

I hope it works that way?
 

Attachments

I'm not sure I understood what you've been told... I don't think Windows or the SSD would be able to use that space by themselves.
Try to extend the windows partition to the maximum, using that unallocated space.
 
xilolee said:
I'm not sure I understood what you've been told... I don't think Windows or the SSD would be able to use that space by themselves.
Try to extend the windows partition to the maximum, using that unallocated space.
Click to expand...

I tried to look it up and it seems to be somewhat valid. Unallocated space can be used as a space for the drive to use for its stuff. Software on Crucial and Samsung drives does it for example.
It also makes it easier to keep that 10% of space always available, as I can't write data to it as a user

I guess I will free up some space on the partition :D
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top