Problem with Windows Update - KB5035962 fails with 0x8000ffff

Mingle

Active member
Joined
Jul 24, 2022
Posts
39
Hello,

I am currently having problems installing Windows updates on a Windows Server 2016 Standard image. KB5035962 and KB5035855 fail with 0x8000ffff

I've run the following already:

1. sfc /scannow
2. DISM /online /cleanup-image /scanhealth and /checkhealth is: no component store corruption
3. A repair via dism /online /cleanup-image /restorehealth

Are you able to help? Thanks!
 

Attachments

Hi,

Upload your COMPONENTS hive.
  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • Please copy this file to your desktop.
  • Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
  • Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Hi,

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

Please reboot the server and attempt to update again. If it fails attach a new copy of the CBS logs.
 
Hi,

Start the
577bf0efb8088-FRST.png
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.

Afterwards reboot the server and attempt to update again. If it fails attach a new copy of the CBS logs.
 

Attachments

Hi,

Please run the following command in an elevated prompt and copy - paste the result in your next post.
Code:
DISM /online /cleanup-image /AnalyzeComponentStore
 
It finished with the below. I've attached the dism.log if needed.

Error: 0x8000ffff

DISM failed. No operation was performed.
For more information, review the log file.

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

Attachments

Rich (BB code):
2024-04-10 10:25:27, Error                 DISM   DISM Package Manager: PID=848 TID=3432 Failed processing package changes with session option CbsSessionOptionAnalyzeStore - CDISMPackageManager::AnalyzeComponentStore(hr:0x800704c7)
2024-04-10 10:25:27, Error                 DISM   DISM Package Manager: PID=848 TID=3432 Failed to analyze component store. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800704c7)
2024-04-10 10:25:27, Error                 DISM   DISM Package Manager: PID=848 TID=3432 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800704c7)
2024-04-10 10:25:27, Info                  DISM   DISM Package Manager: PID=848 TID=3432 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2024-04-10 10:25:27, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800704C7

Please provide the latest CBS logs as well as a copy of the Component Based Servicing Hive.

Export CBS (Component Based Servicing) hive
  • Click on the Start button and type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
    Code:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (*.*).

    622dbef75cd3a-Export-CBS-hive.png

  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send > Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Rich (BB code):
2024-04-10 10:02:22, Info                  CBS    Failed checking if package is deeply superseded:  [Package_for_KB4091664~31bf3856ad364e35~amd64~~10.0.5.0] [HRESULT = 0x8000ffff - E_UNEXPECTED]

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
  • Open the startmenu and type the command cmd.
  • After you find the Command Prompt, right click on it and select Run as Administrator.
  • Copy and paste the following into the Command Prompt and press enter.
Code:
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
Right-click on the file FRST64.exe and choose Run as administrator.
  • Copy and paste the following (code) into the Search box and click the Search Registry button.
Code:
KB4091664
  • When the scan is complete, a message will display that SearchReg.txt is saved in the same folder FRST was started from.
  • Post the logfile SearchReg.txt as attachment in your next reply.
 
Hi,

First, make a backup of this server and the perform the following steps:

Follow these instructions to boot the server into the Recovery Environment
  • Info: Use WinRE to troubleshoot startup issues - Windows Server
  • Boot the server from the correct Windows ServerISO, you can also use an evaluation version of the ISO - which you can download from the Evaluation Center.
  • When the setup screen appears click Next and Repair your computer, in the next screen select Troubleshoot and subsequently the Command Prompt.
  • Run the following command to find the drive letter of the Windows partition:
    Code:
    BCDedit
  • Now run the following command: (replace D: with the correct driveletter which showed by the previous command).
    Code:
    DISM /Image:D:\ /Cleanup-Image /RevertPendingActions /scratchdir:D:\windows\temp
  • Normally you will see the following message:
    Reverting pending actions from the image...
    The operation completed. Any revert of pending actions will be attempted after reboot.
    The operation completed successfully.
  • Please post the result, especially when you get another (error) message.
 
I'm using a citrix virtual desktop environment and cannot perform these steps. I'll likely rebuild the image from scratch using a newer OS. This can be closed.
 
That might be the only option for such environments if you cannot revert to a stable image.
 

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

Back
Top