[SOLVED] Dism error (0x800f081f) The source files could not be found (RGW)

[saa]

Hello,

After installing Windows current monthly updates succesfully, i get the DISM error 0x800f081f.

sfc /scannow -> Good!
Dism /RestoreHealth -> Error: 0x800f0906, The source files could not be downloaded. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log.
dism and CBS logs are attached.



Any idea on how to fix this issue?

Many Thanks

 

[Maxstar]

Hi,

Step 1. Download

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.

• 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.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[saa]

Thanks for the fix. I ran the SFCFix and i got the error 0x800f0906 the source files could not be downloaded. Kindly find a new copy of CBS log attached.

 

[Maxstar]

Could you please post the result of SFCFix (SFCFix.txt)? It seems the fix dit not complete successfully.

 

[saa]

Sorry, i forgot to attach the SFCFix file. Kindly find it attached.

 

[Maxstar]

Please do the following to check some files.

Download the

Farbar Recovery Scan Tool and save it to your Desktop:

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

• 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.

 

[saa]

Thanks for your quick reply. I ran the FRST tool, kindly find the Fixlog.txt attached.

 

[Maxstar]

C:\Windows\Servicing\Packages\Package_2096_for_KB5035855~31bf3856ad364e35~amd64~~10.0.1.11.cat
Catalog: Error1: CreateFileW function failed
Bestand niet getekend
MD5:  <==== AANDACHT (nul byte bestand/map)

All the three *.cat files are corrupted (unreadable) files, so please run the following script to delete them.

Download the

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.

 

[saa]

Thank you. I ran the script and got the fixlog. It says the three files could not be moved.

 

[Maxstar]

Please open the following folder "C:\Windows\Servicing\Packages\" and take a screenshot of the following files.

C:\Windows\Servicing\Packages\Package_2096_for_KB5035855~31bf3856ad364e35~amd64~~10.0.1.11.cat
C:\Windows\Servicing\Packages\Package_2099_for_KB5035855~31bf3856ad364e35~amd64~~10.0.1.11.cat
C:\Windows\Servicing\Packages\Package_2121_for_KB5035855~31bf3856ad364e35~amd64~~10.0.1.11.cat

 

[Maxstar]

P.s. if you are able could you please provide copies of these files to look at.

 

[saa]

I couldn't take a printscreen in the mentioned folder as it has a huge amount of files. In stead, i made a text file with the result of the dir commando. I found the mentioned files:

08-04-2024 12:13 10.591 Package_2096_for_KB5035855~31bf3856ad364e35~amd64~~10.0.1.11.cat
08-04-2024 12:13 10.411 Package_2099_for_KB5035855~31bf3856ad364e35~amd64~~10.0.1.11.cat
08-04-2024 12:13 11.727 Package_2121_for_KB5035855~31bf3856ad364e35~amd64~~10.0.1.11.cat

 

[Maxstar]

Okay, please make a copy of these files to upload them here, and then run the following script.

Start the

Farbar Recovery Scan Tool again.

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.

 

[saa]

Thank you. I ran the script and got the fixlog.txt attached. I'm not able to copy the packages files. I got errors with the copy en robocopy commando's:

copy -> File or folder is damaged and unreadable.
robocopy -> The syntax of the file name, folder name, or volume name is incorrect.

Total commander app was also unable to open the folder C:\Windows\Servicing\Packages\ as it has a huge amount of files.

 

[saa]

Thank you. I ran the script and got the fixlog.txt attached. I'm not able to copy the packages files. I got errors with the copy en robocopy commando's:

copy -> File or folder is damaged and unreadable.
robocopy -> The syntax of the file name, folder name, or volume name is incorrect.

Total commander app was also unable to open the folder C:\Windows\Servicing\Packages\ as it has a huge amount of files.

It says the same as before. Files cannot be unlocked, files cannot be moved.

 

[Maxstar]

Yes, I'm from the Netherlands too so it was clear what the log reported!

Let's try to delete one of the files as follows to see if it will work. Open an elevated command prompt, run the following commands and post the result.

takeown /f "C:\Windows\Servicing\Packages\Package_2096_for_KB5035855~31bf3856ad364e35~amd64~~10.0.1.11.cat"
icacls "C:\Windows\Servicing\Packages\Package_2096_for_KB5035855~31bf3856ad364e35~amd64~~10.0.1.11.cat" /grant administrators:(F) /t
del /f /q "C:\Windows\Servicing\Packages\Package_2096_for_KB5035855~31bf3856ad364e35~amd64~~10.0.1.11.cat"

 

[saa]

Aha, i see the location in your account info. Good to know . I ran the code but i got the following errors:

takeown /f "%systemroot%\Servicing\Packages\Package_2096_for_KB5035855~31bf3856ad364e35~amd64~~10.0.1.11.cat"

ERROR: File or folder is damaged and unreadable.

icacls "%systemroot%\Servicing\Packages\Package_2096_for_KB5035855~31bf3856ad364e35~amd64~~10.0.1.11.cat" /grant administratorsF) /t

File or folder is damaged and unreadable. Successfully processed 0 files; Failed processing 1 files

del /f /q "%systemroot%\Servicing\Packages\Package_2096_for_KB5035855~31bf3856ad364e35~amd64~~10.0.1.11.cat"

ERROR: File or folder is damaged and unreadable.

 

[Maxstar]

Hmm, let's try to remove these files with FRST using PSExec with System Privileges.

Please follow these instructions to run the

Farbar Recovery Scan Tool with system privileges.

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 PsExec from Microsoft Sysinternals to your desktop.
• Unzip PsTools.zip to its own directory on the system drive, for example: C:\Tools\PsTools
• Navigate in an elevated command prompt to the PsTools directory: cd C:\Tools\PsTools.
• Now copy and paste the following command into the command prompt and press enter. Click on the Agree button when the licence agreement of PsExec appears.
• Note: Ensure that both FRST64.exe and the Fixlist.txt file are on your desktop! Otherwise you'll need to ammend the command to the right location.
  

  psexec -i -d -s "%userprofile%\desktop\FRST64.exe"

• FRST will make a new backup of the registry first, please wait until this process is completed.
• Ensure the provided Fixlist.txt is in the same location as FRST64.exe and then 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.

 

[saa]

I ran the code in the PStool but i got the same result unfortuantly

 

[Maxstar]

Hmm, is this a Citrix image? If so are you able to delete the *.cat files from a recovery environment?

C:\Windows\Servicing\Packages\Package_2096_for_KB5035855~31bf3856ad364e35~amd64~~10.0.1.11.cat
C:\Windows\Servicing\Packages\Package_2099_for_KB5035855~31bf3856ad364e35~amd64~~10.0.1.11.cat
C:\Windows\Servicing\Packages\Package_2121_for_KB5035855~31bf3856ad364e35~amd64~~10.0.1.11.cat