[SOLVED] Server 2019 Version 1809 Build 17763.2114 Windows Update errors

[TomasNetit]

Still waiting ... 14 hours ...

 

[TomasNetit]

Undoing Changes... I will send CBS.log.

 

[TomasNetit]

Log

 

[Maxstar]

2024-04-12 09:40:28, Error                 CBS    Startup: A possible hang was detected on the last boot. [HRESULT = 0x800f0920 - CBS_E_HANG_DETECTED]

Hi,

Please run the following command in an elevated prompt and copy and paste the result in your next post.

DISM /online /cleanup-image /AnalyzeComponentStore

 

[TomasNetit]

Hi,

C:\windows\system32>DISM /online /cleanup-image /AnalyzeComponentStore

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.5696

[===========================99.9%========================= ]

Component Store (WinSxS) information:

Windows Explorer Reported Size of Component Store : 29.99 GB

Actual Size of Component Store : 26.74 GB

Shared with Windows : 7.77 GB
Backups and Disabled Features : 18.27 GB
Cache and Temporary Data : 687.91 MB

Date of Last Cleanup : 2024-01-09 00:10:50

Number of Reclaimable Packages : 3
Component Store Cleanup Recommended : Yes

The operation completed successfully.

It look OK now, the question now how should I process it on the production server. Do you have some idea ?

Thank you and I make some donations to your support.

Tomas

 

[Maxstar]

Please run the following command first.

DISM /online /cleanup-image /StartComponentCleanup

Then we can try to update again to see if the update will install without rollback this time.

Thanks for your donation to Sysnative...

 

[TomasNetit]

Oki so i make new fresh copy of production server, run the DISM command and i send you the cbs.log ? Or should i try the 3 fix you already made ?

 

[Maxstar]

There's no need to make a new clone, just run the /StartComponentCleanup command on the current VM and then try to update again to see if it will complete this time.

When successful we can look at the production server...

 

[TomasNetit]

I think this testing server is up-to-date no addtional updates were found, i need to test it again from the ground up before i do it on the production server. Therefore, the question of how to proceed is whether to gradually apply your fix once again or just the last one.

 

[Maxstar]

Ah okay, please post the CBS logs of the production server to look which fix we'll need to apply first.

 

[TomasNetit]

CBS.log prod.

 

[Maxstar]

Please provide the previous (CbsPresist) logs as well.

 

[TomasNetit]

CbsPersist.log

 

[Maxstar]

Is this the only CbsPersist log? This because it does not reported any errors.

 

[TomasNetit]

Its the production Server didnt run the DISM /online /cleanup-image /StartComponentCleanup command there. I will make a copy of it run the command and send you the logs.

 

[Maxstar]

Did you get an error after running this command?

 

[TomasNetit]

After all, our entire communication was about this problem, so when I make a copy of the production server, I will once again get the error code that we solved here, but since you sent 3 versions of the fix, I need to test it once more how to proceed. so I will run DISM /online /cleanup-image /StartComponentCleanup command and send you CBS.log. I hope I wrote it clearly.

 

[TomasNetit]

OK so fresh copy of the prod. VM, run this command :
DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1697

Image Version: 10.0.17763.2114

[==========================100.0%==========================]
Error: 0x800f081f

CBS.log as attachment, just please write me which patch of the three you sent me I should activate.
Thank you

Tomas

 

[Maxstar]

Please run the following fix first.

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.

• 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

 

[TomasNetit]

C:\windows\system32>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1697

Image Version: 10.0.17763.2114

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