[SOLVED] Windows Update Errors, cannot run sfc, scfix does not resolve

luisjahn

Contributor
Joined
Nov 19, 2022
Posts
11
Hello, from some time ago everytime I go to windows update I get "There were problems downloading some updates, but we'll try again later. If you keep seeing this, try searching the web or contacting support for help. This error code might help: (0x800703e6)", if I retry I get the same every time so the computer does not update (trying to download Feature Update to Windows 10, version 22H2).

If I try to run sfc /scannow I get "Resource protection could not start the repair service"

If I try to run DISM I get "the component store cannot be repaired"

If I try to run sfcfix I get "SUMMARY: No corruptions were detected. AutoAnalysis:: directive completed successfully."

I tried downloading the windows image and creating an installation, but after a while it says Windows 10 cannot be installed.

I have run malwarebytes and hitman pro and they found nothing.

So I am stuck, anybody has any idea that could help me update this computer without a clean install?
 
Hello, my computer has WIndows 10 and since about a month I started having problems updating it.

When you go to windows update, you get:

1669815106381.png

Using the instructions of the forum I tried to use SFC and DISM, none of them work, see the images:
1669815205262.png

1669815228546.png

The componen scanner did not find any corruptions:
1669815330412.png

I have attached the CBS log directory contents as requested.

Please help!

Thanks
 

Attachments

Hi,

I have merged both threads, there was no need to start a new thread...

Please do the following.

Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

Warning: This script was written specifically for this system. Do not run this script on another system.

  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Hello, thanks a lot for your reply, I followed the instructions and I am attaching the Fixlog.txt file.

Please let me know if I need to do anything else.
 

Attachments

Rich (BB code):
2022-11-30 09:18:31, Info                  CBS    Loaded Servicing Stack v10.0.19041.1790 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\cbscore.dll
2022-11-30 09:18:31, Info                  CBS    Build: 19041.1.amd64fre.vb_release.191206-1406
2022-11-30 09:18:31, Info                  CBS    Failed to load WCP DLL: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\wcp.dll [HRESULT = 0x800703e6 - ERROR_NOACCESS]
2022-11-30 09:18:31, Info                  CBS    Failed to load WCP DLL. [HRESULT = 0x800703e6 - ERROR_NOACCESS]
2022-11-30 09:18:31, Info                  CBS    Failed to initialize the Core DLL: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\\cbscore.dll [HRESULT = 0x800703e6 - ERROR_NOACCESS]

Open an elevated command prompt and run the following command and copy and paste the result in your next post.
Code:
icacls "C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\*" /T /Q /C /RESET
 
I opened a command prompt as administrator and ran the command, these are the results:

Code:
Microsoft Windows [Version 10.0.19044.1766]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>icacls "C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\*" /T /Q /C /RESET
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\amd64_installed: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\CbsCore.dll: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\CbsMsg.dll: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\cmiadapter.dll: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\cmiaisupport.dll: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\dpx.dll: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\drupdate.dll: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\drvstore.dll: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\EdgeAI.dll: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\GlobalInstallOrder.xml: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\msdelta.dll: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\mspatcha.dll: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\poqexec.exe: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\ReserveManager.dll: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\smiengine.dll: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\smipi.dll: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\TiFileFetcher.exe: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\TiWorker.exe: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\turbostack.dll: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\updateagent.dll: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\WcmTypes.xsd: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\wcp.dll: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\wdscore.dll: Access is denied.
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\wrpint.dll: Access is denied.
Successfully processed 0 files; Failed processing 24 files
 
Download
56f31e53c97da-SFCFix.PNG
SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.
 

Attachments

The Servicing Stack folder is succesfully replaced as it seems, please try to run the System File Checker. If it fails attach a new copy of the CBS.log.
Code:
SFC /Scannow
 
Now sfc seems to be working, can I try tu update now?

Code:
Microsoft Windows [Version 10.0.19044.1766]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
 
Please run the following DISM command first and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 
results of the dism command, I am attaching the DISM log file:

Code:
Microsoft Windows [Version 10.0.19044.2251]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19044.2251

[==========================100.0%==========================]
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 https://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
 

Attachments

Update: In the meantime Windows started processing updates properly!!!

Let me know if there's anything left to do.

Thanks a million for your time to help me solve this issue.

I will donate to your site, it's amazing!
 
That's great and you're welcome, I assume that build 22H2 is also installed without any issues?

Many thanks for considering a donation to Sysnative, this is very much appreciated!

If everything is up and running, we can mark this thread as solved...
 
Everything works now, thanks to you!

If you don't mind me asking, is there a known cause for this windows update corruption? Because otherwise, the computer worked fine.

1669837086006.png

Yes you can mark this as closed, since finally all updates completed at last.

Best regards and thanks again!
 
Hi,

There are several reasons for this kind of corruptions, although it is difficult to ascertain what the exact cause was. To avoid these problems or even worse, I would recommend to make regular backups.

- Third-party cleaning tools such as registry cleaners and/or doubtful optimizing tools.
- Power and system failures or forced shutdowns during the Windows Update process.
- Hardware issues such as a malfunctioning harddrive or memory corruptions.

Best regards and thanks again!

You're welcome. Glad we could help to resolve this problem...
 

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

Back
Top