Windows 10 Pro 19043 - freezes when starting

C

chapmasc

Member
Joined
Mar 2, 2022
Posts
9
I'm having an issue with a desktop that keeps freezing when turning on. It freezes at the screen with the loading circle. I'm unable to get past this. I am able to boot into safe mode and tried to run your sfcFix.exe but received the below error.

Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.
Click to expand...

I proceeded to then try to run the "dism /online /clean-image /RestoreHealth" (received same error as above then) to then get an image using the MS download tool (since I'm only able to boot into safemode and unable to boot to safe mode with networking - it freezes there too) from another PC, to then transfer to this PC so I could run the dism command and specify the WIM. This still had me result in the same error. I've now removed the HD from the desktop and placed in an external drive reader so I could run "dism /Image:G:\ /Cleanup-Image /RestoreHealth" this way it was able to access whatever it needed to online now. Still no luck though; exact same error still and even looking at the dism log it too seems to have the same error info in the log. I would like to run the sfcFix.exe from my laptop if possible, but I could not find any documentation on how to tell your tool to run against my external hard drive that has the OS instead of running against my laptop's active OS. I've also included the logs I have from running the dism commands. I also tried running the below sequence

dism /Image:G:\ /cleanup-image /StartComponentCleanup
Click to expand...

followed by

sfc /scannow /offwindir=G:\windows /offbootdir=H:\
Click to expand...

to then run the dism restore health command again

dism /Image:G:\ /Cleanup-Image /RestoreHealth
Click to expand...

I even tried specifying the WIM path in case that was the issue.
dism /Image:G:\ /Cleanup-Image /RestoreHealth /source:WIM:C:\Temp\install.wim:6 /LimitAccess
Click to expand...

Before any of the above, I had restored a previous restore point that was before the windows update that caused all of my issues. I thought for sure this would fix my issue; but to my surprise it did not. At that point, I then proceeded to run the sfc /scannow and then sfcfix.exe and the dism commands above.

Please help. I would love to know what I should to looking for too, to be able to troubleshoot this on my own as well.
 

Attachments

I forgot to mention, when running the below command, it will go to 20% but then stop and state that the operation completed successfully. I don't think it is actually completing successfully though as I would imagine it should get to 100%. I also included the results of the sfc /scannow below.

PS C:\WINDOWS\system32> dism /Image:G:\ /cleanup-image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.928

[=========== 20.0% ]
The operation completed successfully.
PS C:\WINDOWS\system32> sfc /scannow /offwindir=G:\windows /offbootdir=H:\

Beginning system scan. This process will take some time.


Windows Resource Protection did not find any integrity violations.
Click to expand...
 
I noticed this was moved from the windows update thread to here. Not sure if it is related or not, however I noticed I forgot to include some additional details which is that the PC was working fine until a Windows Update was performed and the PC was rebooted. After that, I could no longer get into windows as it would always freeze on the loading screen. It could be just coincidental; but that was why I placed it under the windows update form as I believe that was the root cause. As mentioned in my above post, the first thing I tried was to restore to a previous working version; however, that did not resolve my issue. I'm looking forward to working with someone on resolving this issue.
 
Have you tried deleting the GPU drivers?

Since you can boot in safe mode.

Is it a laptop? If yes, try disabling the dedicated GPU and run on the integrated one.
 
Regarding NumberFiveee's questions....Thank you for looking into this. I did actually try deleting the display adapters driver. It is a desktop. I'm just using my laptop to run the dism scan against the desktop's drive so it would have access online when running the scan. When in safe mode I opened device manager, expanded "display adapters" and uninstalled the adapter's driver; then rebooted. It still froze on boot loading screen and still could not get into safe mode with networking. This was done early on though, shortly after performing the system restore.
 
So you can boot in safe mode, but not in safe mode with networking?

Were the Ethernet or WLAN controller updated?
 
NumberFiveee, thank you for the suggestion. I checked and device manager's events for the different network adapters. All three show that they have not been updated since 7/31/2021. Which is the last time I performed the clean install when upgrading from windows 7 to windows 10.
 
FreeBooter, thank you for the suggestion. I had not tried that yet. I followed the instructions you provided in your link and the computer still froze on the loading screen (before the prompt for the user to provide their password).
 
I have viewed the CBS.log file, there are no corrupted system files.

2022-02-20 04:53:29, Info CSI 00000006 [SR] Verifying 1 components
2022-02-20 04:53:29, Info CSI 00000007 [SR] Beginning Verify and Repair transaction
2022-02-20 04:53:29, Info CSI 00000008 [SR] Verify complete
2022-02-20 04:53:29, Info CSI 00000009 [SR] Verifying 1 components
2022-02-20 04:53:29, Info CSI 0000000a [SR] Beginning Verify and Repair transaction
2022-02-20 04:53:29, Info CSI 0000000b [SR] Verify complete
2022-02-20 04:53:29, Info CSI 0000000c [SR] Verifying 1 components
2022-02-20 04:53:29, Info CSI 0000000d [SR] Beginning Verify and Repair transaction
2022-02-20 04:53:29, Info CSI 0000000f [SR] Verify complete
2022-02-20 04:53:29, Info CSI 00000010 [SR] Verifying 1 components
2022-02-20 04:53:29, Info CSI 00000011 [SR] Beginning Verify and Repair transaction
2022-02-20 04:53:29, Info CSI 00000012 [SR] Verify complete
2022-02-20 04:53:29, Info CSI 00000013 [SR] Verifying 1 components
2022-02-20 04:53:29, Info CSI 00000014 [SR] Beginning Verify and Repair transaction
2022-02-20 04:53:30, Info CSI 00000015 [SR] Verify complete
2022-02-20 04:53:30, Info CSI 00000016 [SR] Verifying 1 components
2022-02-20 04:53:30, Info CSI 00000017 [SR] Beginning Verify and Repair transaction
2022-02-20 04:53:30, Info CSI 00000018 [SR] Verify complete
2022-02-27 06:12:08, Info CSI 00000006 [SR] Verifying 1 components
2022-02-27 06:12:08, Info CSI 00000007 [SR] Beginning Verify and Repair transaction
2022-02-27 06:12:08, Info CSI 00000008 [SR] Verify complete
2022-02-27 06:12:08, Info CSI 00000009 [SR] Verifying 1 components
2022-02-27 06:12:08, Info CSI 0000000a [SR] Beginning Verify and Repair transaction
2022-02-27 06:12:08, Info CSI 0000000b [SR] Verify complete
2022-02-27 06:12:08, Info CSI 0000000c [SR] Verifying 1 components
2022-02-27 06:12:08, Info CSI 0000000d [SR] Beginning Verify and Repair transaction
2022-02-27 06:12:08, Info CSI 0000000e [SR] Verify complete
2022-02-27 06:12:08, Info CSI 0000000f [SR] Verifying 1 components
2022-02-27 06:12:08, Info CSI 00000010 [SR] Beginning Verify and Repair transaction
2022-02-27 06:12:08, Info CSI 00000011 [SR] Verify complete
2022-02-27 06:12:08, Info CSI 00000012 [SR] Verifying 1 components
2022-02-27 06:12:08, Info CSI 00000013 [SR] Beginning Verify and Repair transaction
2022-02-27 06:12:09, Info CSI 00000014 [SR] Verify complete
2022-02-27 06:12:09, Info CSI 00000015 [SR] Verifying 1 components
2022-02-27 06:12:09, Info CSI 00000016 [SR] Beginning Verify and Repair transaction
2022-02-27 06:12:09, Info CSI 00000017 [SR] Verify complete
Click to expand...

Try Startup Repair tool from Windows Recovery Environment also try restoring Windows 10 to date where there was no login problem.
 
FreeBoooter, thank you for reviewing the logs. If everything seems fine in the logs, then do you have any idea what is causing the "dism /online /clean-image /RestoreHealth" command to fail? In regard to the Startup Repair tool from Windows Recovery; I had initially tried that, and it stated it could not repair. As far as the restore point, there was only one restore point I could chose, and it was from before 2/23/2022 when I started having issues. Although it stated it successfully restored (and no restore points show up anymore when I go to that section), the PC still freezes when loading.
 
If you are executing the Dism tool from Safe Mode without internet connection, it will fail what is important is SFC tool have not found any problems with Windows system files so no need to execute Dism command.

Please attach the C:\Windows\System32\Logfiles\Srt\SrtTrail.txt startup repair log file to your next post.
 
Not sure if this changes anything but I did attach the drive to a working pc that has internet access and ran the dism command with the switch to tell it to scan my offline drive instead of my current system's OS. That too had the same error as when I ran it via safe mode (without networking/ie internet access). Please see the attached srtTrail.txt you requested.
 

Attachments

chapmasc said:
Not sure if this changes anything but I did attach the drive to a working pc that has internet access and ran the dism command with the switch to tell it to scan my offline drive instead of my current system's OS. That too had the same error as when I ran it via safe mode (without networking/ie internet access). Please see the attached srtTrail.txt you requested.
Click to expand...
Code: 
DISM /Online /Cleanup-Image /RestoreHealth


The above command will not work if Windows Update service not working correctly. You will be prompted to use /source parameter to specify the location of the files that are require to restore the damage or missing files.

lgSdJee.jpg



The Install.wim is the source of where these corrupted or missing files located.
The Windows Imaging Format (WIM) is a file-based disk image format. It was developed by Microsoft to help deploy Windows Vista and subsequent versions of Windows operating system family.
The following command can be executed to extract corrupted or missing Windows Component Store files.

Code: 
DISM  /Online  /Cleanup-Image   /RestoreHealth     /Source:WIM:X:\Sources\Install.wim:1    /LimitAccess

Replace the X:\Sources folder path with a folder path where Install.wim image file is stored.
The /LimitAcess parameter tells DISM utility to not to use Windows Update service to retrieve corrupted or missing files.
The /Index parameter tells DISM utility to retrieve the corrupted or missing files from which edition of Windows OS. The Install.wim file can contain more than one edition of the Windows OS. You can execute following command to found out index number of your Windows OS edition that you want to repair.

Code: 
Dism  /Get-WimInfo  /Wimfile:"L:\sources\install.wim"

34j6bVp.jpg


Replace the L:\sources with directory path where Install.wim stored. As you can see there is two editions of Windows 10 and all have index number.
 

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

Back
Top