Error

It went to 78% but then again failed with error: Download error - 0x800f0982

CBS log attached again.
 

Attachments

Hi,

Please attempt to update again with Process Monitor running, and attach the PML file with a new copy of the CBS log.

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,

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 SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
62151e1bebac4-SFCFix-Txt-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.
Afterwards attempt to update and post the result. If it fails attach a new copy of the CBS log(s).
 

Attachments

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

Deployment Image Servicing and Management tool
Version: 10.0.20348.681

Image Version: 10.0.20348.1129

[===========================84.9%================= ]
[===========================88.7%=================== ]
[==========================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 Configure a Windows Repair Source.

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

Attachments

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

Deployment Image Servicing and Management tool
Version: 10.0.20348.681

Image Version: 10.0.20348.1129

[===========================84.9%================= ]
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
 

Attachments

Great, please attempt to update. If it fails attach a new copy of the CBS log(s).
 
Wouter VH said:
I installed a new server 2022 2 months ago
Click to expand...
Was this a clean install or an upgrade from Windows 2016, this because the CBS log is reporting files which belong to Server 2016? And more important, were there any issues with Server 2016 before the upgrade?
 
Yes this was a clean install of windows server 2022, I migrated a server 2016 AD to it and some other services
 
I would suggest to try an repair install (in-place-upgrade) of Server 2022 with the ISO mounted, this is the safest way to fix this server in my opinion.
 
Usually not, the installation procedure will show a summary of possible problems, otherwise you could clone this server first. And then try to perform a repair install on the clone.

  • Mount the Windows Server ISO and run Setup.exe. You can use the Microsoft Evaluation Centre to download the ISO files.
  • Use the option Download updates, drivers, and optional features (recommended) and click Next.
  • Depending on your Windows Server version and license, you may see a screen prompting you to enter the licensing key.
  • In the next screen, select the image of the installed Windows Server edition and click Next.
  • Then accept the EULA. To perform a in-place upgrade, you need to check keep personal files and apps. Then click Next.
  • The installation process will perform a compatibity check, please read this part carefully.
  • If you agree with the changes, click Next.
  • After clicking Next, an upgrade process will start checking for updates, when this is ready click install to start the in-place upgrade.
 
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