Server 2016 update error (0x80070006)

Psycho Ned

Member
Joined
Nov 2, 2022
Posts
5
Hi

I've got a 2016 std server which is failing to update (was working ok till this months updates).

sfc /scannow initially found corruption but now is coming back ok.

Dism /Online /Cleanup-Image /RestoreHealth fails with the error:

2022-11-02 09:58:59, Info DISM DISM Package Manager: PID=6244 TID=5064 Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error
2022-11-02 09:58:59, Error DISM DISM Package Manager: PID=6244 TID=7588 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)
2022-11-02 09:58:59, Error DISM DISM Package Manager: PID=6244 TID=7588 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2022-11-02 09:58:59, Error DISM DISM Package Manager: PID=6244 TID=7588 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)
2022-11-02 09:58:59, Error DISM DISM Package Manager: PID=6244 TID=7588 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2022-11-02 09:59:12, Error DISM DISM Package Manager: PID=6244 TID=7588 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f081f)
2022-11-02 09:59:12, Error DISM DISM Package Manager: PID=6244 TID=7588 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)

I've ran it with the /source option pointing to a fully patched 2016 install.wim but still get the same error about source files not found.

I've also tried resetting the windows components and renaming the download and datastore folders in software distribution.
 

Attachments

Hi and welcome to Sysnative,

Step 1. 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.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Hi,

Please attach the latest CBS log(s).
  • Open Windows Explorer and browse to the C:\Windows\Logs folder.
  • Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
618e949e09fef-CBS-Folder.png

  • Attach the file CBS.zip to your next reply.
 
Which update (KB number) is failing, an update for .NET Framework perhaps?
 
KB8018411 2022-10 Cumulative update for 2016

If I run windows update I immediately get the 0x80070006 error before it even finds the update.
 
Hmm, unfortunately the CBS log provides no useful information. So could you please try to update again with Process Monitor is running.
Other question, which security software is installed on this server?

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below.



4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
 
Hi,

In this case Windows Update failed with the same error, so my advice would be to uninstall Sophos completely and the try to update again.
 

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

Back
Top