[SOLVED] Windows 10 not updating

F

fettsvett201

Well-known member
Joined
Feb 19, 2022
Posts
57
Hello,

Trying to update Windows 10 and am having problems.

Running Windows update returns Error Code (0x80073712).

Tried to use Microsoft Media Creation Tool to update that way but that also freezes.

I ran sfc /scannow and it got stuck at 76% for 2 and a half hours. I had to kill it.

Ran SFCFix and it got stuck at 3.8%. When I returned several hours later, the computer had restarted (likely due to OS crash). Re-ran SFCFix and it completed this time.

Log files as requested:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-02-20 10:53:02.401
Microsoft Windows 10 Insider Slow, Build 19042 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 3
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2022-02-20 10:58:24.953
----------------------EOF-----------------------


Thank you for your time,
Fetts

EDIT: I should note the OS is a Windows Insider Build (Version 20H2 Build 19042.746). I've been trying off and on for a year to get off this Insider build with no luck. The past few days it has been crashing multiple times a day.
 

Attachments

Last edited:
Rich (BB code): 
2022-02-20 10:53:15, Info                  CBS    FLOW: Entering stage: CheckCsi 
2022-02-20 10:53:53, Info                  CSI    00000007 Warning: Unable to repair manifest for component ([l:99 ml:140]'amd64_microsoft-windows-web-app-host.resources_31bf3856ad364e35_10.0.19041.1_fr-ca_e937b39bfe540ae2') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-02-20 10:54:05, Error                 CSI    00000008@2022/2/20:16:54:05.402 (F) onecore\base\wcp\sil\ntsystem.cpp(3044): Error STATUS_FILE_CORRUPT_ERROR originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
[gle=0x80004005]
2022-02-20 10:54:05, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CBS.log to WER report.
2022-02-20 10:54:05, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20220220165312.log to WER report.
2022-02-20 10:54:05, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20220219224539.cab to WER report.
2022-02-20 10:54:05, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20220219190155.cab to WER report.
2022-02-20 10:54:05, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20220219044802.cab to WER report.
2022-02-20 10:54:05, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20220219043754.cab to WER report.
2022-02-20 10:54:05, Info                  CBS    Not able to add current session file to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-02-20 10:54:05, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-02-20 10:54:05, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-02-20 10:54:05, Info                  CBS    Not able to add poqexec.log to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-02-20 10:54:05, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-02-20 10:54:05, Error                 CSI    00000009 (F) STATUS_FILE_CORRUPT_ERROR #1267930# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowFileNotFound|AllowSharingViolation|AllowTransactionalConflict), handle = {provider=NULL, handle=0, name= ("null")}, da = (FILE_GENERIC_READ), oa = @0xa6de6fbbc8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[118]'\SystemRoot\WinSxS\wow64_microsoft-windows-dot3gpui_31bf3856ad364e35_10.0.19041.746_none_7dd5922827f647c9\dot3gpui.dll'; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xa6de[gle=0xd0000102]
2022-02-20 10:54:05, Error                 CSI    6fbc28, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd0000102]
2022-02-20 10:54:05, Error                 CSI    0000000a (F) STATUS_FILE_CORRUPT_ERROR #1267929# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingFile(...)[gle=0xd0000102]
2022-02-20 10:54:05, Error                 CSI    0000000b (F) STATUS_FILE_CORRUPT_ERROR #1267928# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingFile(flags = (MissingFileIsOk|SharingViolationIsOk|TransactionalConflictIsOk), da = (FILE_GENERIC_READ), oa = @0xa6de6fc270->SIL_OBJECT_ATTRIBUTES {s:40; on:"dot3gpui.dll"; a:(OBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_SYNCHRONOUS_IO_NONALERT|FILE_NON_DIRECTORY_FILE|FILE_OPEN_FOR_BACKUP_INTENT), file = NULL, disp = Invalid)[gle=0xd0000102]
2022-02-20 10:54:05, Error                 CSI    
[gle=0xd0000102]
2022-02-20 10:54:05, Info                  CSI    0000000c Direct SIL provider: Number of files opened: 38258.
2022-02-20 10:54:05, Error                 CSI    0000000d (F) STATUS_FILE_CORRUPT_ERROR #233# from CCSDirect::EnumStoreCorruptions(...)[gle=0xd0000102]
2022-02-20 10:54:05, Error                 CSI    0000000e (F) HRESULT_FROM_WIN32(1392) #232# from Windows::COM::CStorePendingStoreRepairTxn_IStorePendingStoreRepairTransaction::Detect(Flags = 4, cancelEvt = 2c8 (''), disp = 0)[gle=0x80070570]
2022-02-20 10:54:05, Error                 CBS    Rept: Failed to call CSI detect. [HRESULT = 0x80070570 - ERROR_FILE_CORRUPT]
2022-02-20 10:54:05, Info                  CBS    Failed to check CSI store. [HRESULT = 0x80070570 - ERROR_FILE_CORRUPT]

Rich (BB code): 
2022-02-20 06:58:08, Info                  CSI    00000258 StoreCorruptionRepair transaction begun. WcpVersion: [l:38]'10.0.19041.1525 (WinBuild.160101.0800)'.
2022-02-20 06:58:08, Info                  CSI    00000259@2022/2/20:12:58:08.684 Starting corruption detection (InnerFlags=10)
2022-02-20 06:58:27, Error                 CSI    0000025a@2022/2/20:12:58:27.927 (F) Attempting to mark store corrupt with category [l:15 ml:16]'CorruptManifest'[gle=0x80004005]
2022-02-20 06:58:27, Error                 CSI    0000025b@2022/2/20:12:58:27.927 (F) onecore\base\wcp\componentstore\storelayout.cpp(3043): Store corruption detected in function ComponentStore::CRawStoreLayout::FetchManifestContent expression: 0
  MissingFileSystemResource on resource '\winsxs\manifests\amd64_microsoft-windows-web-app-host.resources_31bf3856ad364e35_10.0.19041.1_fr-ca_e937b39bfe540ae2.manifest'[gle=0x80004005]
2022-02-20 06:58:27, Info                  CSI    0000025c Direct SIL provider: Number of files opened: 18441.
2022-02-20 06:58:27, Error                 CSI    0000025d (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #2515112# from CCSDirect::EnumStoreCorruptions(...)[gle=0xd015001a]
2022-02-20 06:58:27, Error                 CSI    0000025e (F) HRESULT_FROM_WIN32(14098) #2515111# from Windows::COM::CStorePendingStoreRepairTxn_IStorePendingStoreRepairTransaction::Detect(Flags = 20, cancelEvt = f04 (''), disp = 0)[gle=0x80073712]
2022-02-20 06:58:27, Error                 CBS    Rept: Failed to call CSI detect. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-02-20 06:58:27, Info                  CBS    Failed to check CSI store. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]



SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
 

Attachments

Apologies. I've been away from my computer all this week. I will try early next week. Thanks.
 
(Apologies for the multiple posts).

I have some time today so here is what's happening.

I ran the tool a few days ago by dragging the zip file to the exe file. I let it run for a few hours but nothing seemed to happen and no document was generated.

Restarted the computer and ran it again. Came back a few days later and the same thing happened.

Checked my settings and realized I was in "Selective Startup" mode. I originally did this a week ago as I was trying to remove all the factors that could be causing the problem. I rebooted the computer in "Normal Startup" and ran "SFCFix" by itself.

It detected no errors.

I ran Windows update and it seems to have been working as it was installing "2022-02 Cumulative Update for Windows 10 Version 20H2 for x64-based Systems (KB5010342)". It got to 100% installing and then an error occurred stating "Some update files are missing or have problems". Error code is 80073712.

I re-ran sfc /scannow and Verification got past 7% (it always froze at that point in the past). Got to 76% and then displayed "Windows Resource Protection could not perform the requested operation."

Thank you for your time.
 
Could you please run SFCFix with the .zip file again? It will replace those missing manifest files identified in my post.
 
I ran the program as requested with the zip file.

No document was generated and it just stayed on a screen stating:

Welcome to SFCFix by niemiro and sysnative.com.

Checking for updates . . .
No new update is available at this time.

Processing directive 1 of 1 (PowerCopy::)

It ran for several hours until I had to go. When I came back, my OS had restarted (it does that a lot).
 
Could you please try one more time please? Make sure nothing else is running too. Could you please check the following directory for any dump files?

Rich (BB code): 
%systemroot%\Minidump
 
No Minidump on C:, but I have a Minidump folder on C:Windows/Minidump. I will run the program again as instructed.

Before running, I did a search on my computer with the program "Everything" (searches your computer instantly for file names by VoidTools) for the files you are trying to copy over. Here are the results incase SFCFix already did it.

I will start the program now.
 

Attachments

  • Manifests.png
    Manifests.png
    55.7 KB · Views: 4
  • WinSxS.png
    WinSxS.png
    113.9 KB · Views: 3
Last edited:
The files will already exist but they're corrupt. Did you manage to run SFCFix?

fettsvett201 said:
No Minidump on C:, but I have a Minidump folder on C:Windows/Minidump
Click to expand...
The %systemroot% environment variable points to C:\Windows. I assume the folder was empty?
 
Ran the program with the zip file for 16 hours. No text file generated.

After the computer restarted, I reran SFCFix by itself. It got to image verification but failed. It pointed to a dsim.log file for more information. I have enclosed the file in case you want it.

SFCFix successfully processed all directives and No corruptions were detected.

As for the Minidump folder, I have enclosed the files that were inside the folder. Note I had to add the extension .txt after .dmp for Chrome to access the file.
 

Attachments

fettsvett201 said:
Ran the program with the zip file for 16 hours. No text file generated.
Click to expand...
That's not right, something unusual is going on here.

Could you please just zip up and attach the dump files from the Minidump folder? I won't be able to open them with WinDbg otherwise. Those crashes appear to be very recent too.
 
Could you please remove avast using their official removal tool, it appears to be causing possible issues and it may be why SFCFix appears to be hanging for so often.

Rich (BB code): 
7: kd> lmvm aswbidsdriver
Browse full module list
start             end                 module name
fffff800`71af0000 fffff800`71b4b000   aswbidsdriver T (no symbols)        
    Loaded symbol image file: aswbidsdriver.sys
    Image path: \SystemRoot\system32\drivers\aswbidsdriver.sys
    Image name: aswbidsdriver.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Feb 15 15:13:51 2022 (620BC32F)
    CheckSum:         000628F0
    ImageSize:        0005B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

That particular build has actually caused issues for another user too.

SYSTEM SERVICE EXCEPTION

Just checked the second most recent dump file and that crash actually occurred while your servicing stack (responsible for managing Windows Update) was running too.
 
Removed Avast using the program you recommended in Safe mode (which is recommended by the program itself).

Restarted computer and ran SFCFix with zip file. Its been running 5 hours now.

Says its "Processing directive 1 of 1 (PowerCopy::)".

No text file has been generated on desktop.

Thank you for taking the time to help with this.
 
It looks like from the app you just want to copy over a manifest file and a .dll file to a specific file location. Looking at those file paths, it looks like the manifest file was successfully copied over (with a modified date of 3/15/2022), but not the dll file (with a modified date of 1/14/2022). If you like, I can copy over the file manually (Digital Forensic Examiner with 8 years experience).

Actually, as I was writing that, SFCfix finally finished. Seemed to happen at the same time I double-clicked the .dll file located at "C:\Windows\WinSxS\wow64_microsoft-windows-dot3gpui_31bf3856ad364e35_10.0.19041.746_none_7dd5922827f647c9\dot3gpui.dll". I clicked on it as the icon looks to be a folder with an X on it (not the normal .dll icon). The window froze up and I had to restart Windows Explorer (probably because Explorer didn't know how to interpret the file).

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-03-15 15:17:42.321
Microsoft Windows 10 Insider Slow, Build 19042 - amd64
Using .zip script file at E:\Fetts\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\Manifests\amd64_microsoft-windows-web-app-host.resources_31bf3856ad364e35_10.0.19041.1_fr-ca_e937b39bfe540ae2.manifest
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\wow64_microsoft-windows-dot3gpui_31bf3856ad364e35_10.0.19041.746_none_7dd5922827f647c9

WARNING: File C:\WINDOWS\WinSxS\Manifests\amd64_microsoft-windows-web-app-host.resources_31bf3856ad364e35_10.0.19041.1_fr-ca_e937b39bfe540ae2.manifest was not backed up as that would replace the current backup.
Successfully copied file C:\Users\Fetts\AppData\Local\niemiro\Archive\Manifests\amd64_microsoft-windows-web-app-host.resources_31bf3856ad364e35_10.0.19041.1_fr-ca_e937b39bfe540ae2.manifest to C:\WINDOWS\WinSxS\Manifests\amd64_microsoft-windows-web-app-host.resources_31bf3856ad364e35_10.0.19041.1_fr-ca_e937b39bfe540ae2.manifest.
Failed to read file attributes for file C:\WINDOWS\WinSxS\wow64_microsoft-windows-dot3gpui_31bf3856ad364e35_10.0.19041.746_none_7dd5922827f647c9\dot3gpui.dll.
Failed to copy file C:\Users\Fetts\AppData\Local\niemiro\Archive\WinSxS\wow64_microsoft-windows-dot3gpui_31bf3856ad364e35_10.0.19041.746_none_7dd5922827f647c9\dot3gpui.dll to C:\WINDOWS\WinSxS\wow64_microsoft-windows-dot3gpui_31bf3856ad364e35_10.0.19041.746_none_7dd5922827f647c9\dot3gpui.dll with error code 0x570.

Successfully restored ownership for C:\WINDOWS\WinSxS\Manifests\amd64_microsoft-windows-web-app-host.resources_31bf3856ad364e35_10.0.19041.1_fr-ca_e937b39bfe540ae2.manifest
Successfully restored permissions on C:\WINDOWS\WinSxS\Manifests\amd64_microsoft-windows-web-app-host.resources_31bf3856ad364e35_10.0.19041.1_fr-ca_e937b39bfe540ae2.manifest
Successfully restored ownership for C:\WINDOWS\WinSxS\wow64_microsoft-windows-dot3gpui_31bf3856ad364e35_10.0.19041.746_none_7dd5922827f647c9
Successfully restored permissions on C:\WINDOWS\WinSxS\wow64_microsoft-windows-dot3gpui_31bf3856ad364e35_10.0.19041.746_none_7dd5922827f647c9
PowerCopy:: directive failed to complete successfully.




Failed to process all directives successfully.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2022-03-15 15:39:00.431
Script hash: J1c2xM0ranbw8bXpIteCC54NKcztodTHFarJbI2Cpbo=
----------------------EOF-----------------------
 
Looking more at that specific file, anytime its interacted with (even if I cursor over it) it stalls Windows explorer. When the file path is viewed on command line (with admin rights), the file doesn't even show up.

Specifically dot3gpui.dll on systemroot

The file does show up in PowerShell (with admin rights). Has the attributes of Directory, Archive, and System. But when interacted with (remove-item and rename-item), powershell stops. This file has to be the reason why everything seems to stall.

The file may have to be deleted in safe mode or boot into a Linux OS and delete the file manually.

I will hold on doing anything until you write back.

Thanks.
 
Last edited:
That's very odd, wonder why it's become corrupted like that? It must be the reason why SFCFix was taking so long to complete too. The fix was only two files so it should take a matter of seconds to complete.

Does the forensics tool you mentioned restore the permissions back correctly? The main reason to use SFCFix is because it'll restore the ownership back to the TrustedInstaller.
 
I believe the file to be too corrupted to salvage. I would delete the file using Paladin (a linux based forensic OS) and replace it with the file inside the SFCFix zip file you provided.
 
Actually, we can try and delete the file using SFCFix and then replace it within the same fix "cycle". If for some reason it can't open a file handle to the corrupt file, we'll delete the parent directory of the file and then replace the entire folder.

SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
 

Attachments

You must log in or register to reply here.

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

Back
Top