[SOLVED] Problem installing Cumulative Updates on Server 2019

ebertandy03 · Mar 13, 2024

Been having issues updating my new Windows Server 2019 Standard server with updated Cumulative Updates. Get similar issues as others on this forum have reported.

Fault bucket 1572099324822013148, type 5
Event Name: CbsPackageServicingFailure2
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17763.5084
P2: Package_for_ServicingStack_5084
P3: 17763.5084.1.2
P4: amd64
P5: unknown
P6: 800f0982
P7: Stage
P8: Installed
P9: Installed
P10: WindowsUpdateAgent

Fault bucket 2032441022521218626, type 5
Event Name: WindowsWcpOtherFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17763.5084:3
P2: wcp\componentstore\storelayout.cpp
P3: ComponentStore::CRawStoreLayout::AddComponentFile
P4: 2264
P5: 800f0982
P6: 0x5a12b49d
P7:
P8:
P9:
P10:

Attached CBS file logs. SFC /Scannow and component scanner did not resolve unfortunately.

ebertandy03 · Mar 23, 2024

Gary R · Mar 25, 2024

Logs supplied are not really telling too much, so can you please do the following ....

Click Search button and type Command Prompt
From the results, right click on the Command Prompt icon, and select Run as administrator
A Command Window will open.
Copy paste the command below into it, then press Enter
Dism /Online /Cleanup-Image /RestoreHealth
Once DISM has finished running ...
- Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
If the file is too large, upload it to a file sharing service, and post me the link.
Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

ebertandy03 · Mar 25, 2024

Thank you Gary for your response. Attached is the CBS.Log file after running the DISM command you requested.

Gary R · Mar 25, 2024

Latest log not flagging anything.

Please try updating your computer again.

If successful please let me know.

If not (and I kinda expect you won't be) please post the CBS.log created after the update attempt, so we can see if anything is being flagged this time.

ebertandy03 · Mar 25, 2024

Here is the link for WeTransfer

CBS.log

Thanks Gary

Gary R · Mar 25, 2024

OK, that one's thrown something up

So can you please post me a copy of your COMPONENTS hive file ....

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.
The file will likely be too large to upload here, if so please upload to a file sharing service.
Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Please post me the link to the file

ebertandy03 · Mar 26, 2024

Here is the link. Thank you Gary

COMPONENTS.zip

Gary R · Mar 26, 2024

OK, I think I can see what the problem is, however I'm having problems trying to source the necessary resources to patch it, so I'm going to need to consult with my colleagues to see what they can suggest.

This may take a while, but I will get back to you as soon as I can.

Gary R · Mar 26, 2024

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

Download SFCFix.exe and save it to your desktop.
Download the attachment SFCFix.zip and also save it on your desktop.
Save any work you have open, and close all programs.
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
Open the file, then copy and paste its content in your next reply.

Next ...

Click Search button and type Command Prompt
From the results, right click on the Command Prompt icon, and select Run as administrator
A Command Window will open.
Copy paste the command below into it, then press Enter
Dism /Online /Cleanup-Image /RestoreHealth
Once DISM has finished running ...
- Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
If the file is too large, upload it to a file sharing service, and post me the link.
Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

ebertandy03 · Mar 26, 2024

SFCFix version 3.0.2.1 by niemiro.
Start time: 2024-03-26 13:16:53.273
Microsoft Windows Server 10 Build 17763 - amd64
Using .zip script file at C:\Users\administrator.TCK0\Desktop\SFCFix.zip [0]

PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS

Successfully created directory tree \\?\C:\Windows\WinSxS\amd64_microsoft-windows-sms-proxy.resources_31bf3856ad364e35_10.0.17763.1911_ja-jp_fbcac8d5e52013ec\r.
Successfully created directory tree \\?\C:\Windows\WinSxS\amd64_microsoft-windows-sms-proxy.resources_31bf3856ad364e35_10.0.17763.1911_ja-jp_fbcac8d5e52013ec\n.
Successfully created directory tree \\?\C:\Windows\WinSxS\amd64_microsoft-windows-sms-proxy.resources_31bf3856ad364e35_10.0.17763.1911_ja-jp_fbcac8d5e52013ec\f.

Successfully copied file C:\Users\administrator.TCK0\AppData\Local\niemiro\Archive\amd64_microsoft-windows-sms-proxy.resources_31bf3856ad364e35_10.0.17763.1911_ja-jp_fbcac8d5e52013ec\r\microsoft.storagemigration.proxyresource.dll.mui to C:\Windows\WinSxS\amd64_microsoft-windows-sms-proxy.resources_31bf3856ad364e35_10.0.17763.1911_ja-jp_fbcac8d5e52013ec\r\microsoft.storagemigration.proxyresource.dll.mui.
Successfully copied file C:\Users\administrator.TCK0\AppData\Local\niemiro\Archive\amd64_microsoft-windows-sms-proxy.resources_31bf3856ad364e35_10.0.17763.1911_ja-jp_fbcac8d5e52013ec\n\microsoft.storagemigration.proxy.common.resources.dll to C:\Windows\WinSxS\amd64_microsoft-windows-sms-proxy.resources_31bf3856ad364e35_10.0.17763.1911_ja-jp_fbcac8d5e52013ec\n\microsoft.storagemigration.proxy.common.resources.dll.
Successfully copied file C:\Users\administrator.TCK0\AppData\Local\niemiro\Archive\amd64_microsoft-windows-sms-proxy.resources_31bf3856ad364e35_10.0.17763.1911_ja-jp_fbcac8d5e52013ec\f\microsoft.storagemigration.proxyresource.dll.mui to C:\Windows\WinSxS\amd64_microsoft-windows-sms-proxy.resources_31bf3856ad364e35_10.0.17763.1911_ja-jp_fbcac8d5e52013ec\f\microsoft.storagemigration.proxyresource.dll.mui.

Successfully restored ownership for C:\Windows\WinSxS
Successfully restored permissions on C:\Windows\WinSxS
PowerCopy:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2024-03-26 13:16:57.866
Script hash: T4Wtk31xuQOkpN217+Ge/PnDuTS0ls6fv4vQAlY/ymg=
----------------------EOF-----------------------

Gary R · Mar 26, 2024

Nothing being flagged in your latest CBS.log, so please try updating your machine.

If successful please let me know.

If not please post the CBS.log created after your update attempt.

ebertandy03 · Mar 27, 2024

Thank you Gary. Unfortunately, the install did not succeed. Attached is the log taken right after the failure.

Thanks for your continued support!

Gary R · Mar 27, 2024

Going to have to set up and update a new VM to the necessary state to source the resources I need. This will take me some time, so may be a while before I'm able to get back to you.

Question .... is Japanese the install language for your machine, or do you just have the Japanese language pack installed ?

Gary R · Mar 27, 2024

No need to answer my last question, I've managed to source what I needed.

So .....

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

Download the attachment SFCFix.zip and save it on your desktop.
Save any work you have open, and close all programs.
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
Open the file, then copy and paste its content in your next reply.

Next ...

Click Search button and type Command Prompt
From the results, right click on the Command Prompt icon, and select Run as administrator
A Command Window will open.
Copy paste the command below into it, then press Enter
Dism /Online /Cleanup-Image /RestoreHealth
Once DISM has finished running ...
- Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
If the file is too large, upload it to a file sharing service, and post me the link.
Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

ebertandy03 · Mar 27, 2024

Thank you Gary. Previously, I removed all language packs and just left the EN-US language Pack. Shocked me to think that Japanese was still installed. I installed it once in settings to see if I could resolve it and when it didn't I removed it.

Here is the output of the latest fix you provided.

Thanks!
Andy

-----------------------

SFCFix version 3.0.2.1 by niemiro.
Start time: 2024-03-27 09:34:01.775
Microsoft Windows Server 10 Build 17763 - amd64
Using .zip script file at C:\Users\administrator.TCK0\Desktop\SFCFix.zip [0]

PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-sms-proxy.resources_31bf3856ad364e35_10.0.17763.1911_ja-jp_fbcac8d5e52013ec.manifest

Successfully copied file C:\Users\administrator.TCK0\AppData\Local\niemiro\Archive\amd64_microsoft-windows-sms-proxy.resources_31bf3856ad364e35_10.0.17763.1911_ja-jp_fbcac8d5e52013ec.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-sms-proxy.resources_31bf3856ad364e35_10.0.17763.1911_ja-jp_fbcac8d5e52013ec.manifest.

Successfully restored ownership for C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-sms-proxy.resources_31bf3856ad364e35_10.0.17763.1911_ja-jp_fbcac8d5e52013ec.manifest
Successfully restored permissions on C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-sms-proxy.resources_31bf3856ad364e35_10.0.17763.1911_ja-jp_fbcac8d5e52013ec.manifest
PowerCopy:: directive completed successfully.

RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-sms-proxy.resources_31bf3856ad364e35_10.0.17763.1911_ja-jp_fbcac8d5e52013ec.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.5568 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-sms.resources_31bf3856ad364e35_ja-jp_719613ce4a5b4f68.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.5568 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-sms.resources_31bf3856ad364e35_ja-jp_719613ce4a5b4f68.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.5568 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-sms.resources_31bf3856ad364e35_ja-jp_719613ce4a5b4f68\v!10.0.17763.1911.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1b71c1e41bc..262307cf262_31bf3856ad364e35_10.0.17763.1911_15ab363898eff242.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-sms-proxy.resources_31bf3856ad364e35_10.0.17763.1911_ja-jp_fbcac8d5e52013ec.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.5568 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-sms.resources_31bf3856ad364e35_ja-jp_719613ce4a5b4f68.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.5568 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-sms.resources_31bf3856ad364e35_ja-jp_719613ce4a5b4f68.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.5568 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-sms.resources_31bf3856ad364e35_ja-jp_719613ce4a5b4f68\v!10.0.17763.1.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.5568 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-sms.resources_31bf3856ad364e35_ja-jp_719613ce4a5b4f68\v!10.0.17763.1911.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.5568 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-sms.resources_31bf3856ad364e35_ja-jp_719613ce4a5b4f68\v!10.0.17763.1911.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1b71c1e41bc..262307cf262_31bf3856ad364e35_10.0.17763.1911_15ab363898eff242.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-sms-proxy.resources_31bf3856ad364e35_10.0.17763.1911_ja-jp_fbcac8d5e52013ec.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.5568 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-sms.resources_31bf3856ad364e35_ja-jp_719613ce4a5b4f68.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.5568 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-sms.resources_31bf3856ad364e35_ja-jp_719613ce4a5b4f68\v!10.0.17763.1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.5568 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-sms.resources_31bf3856ad364e35_ja-jp_719613ce4a5b4f68.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.5568 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-sms.resources_31bf3856ad364e35_ja-jp_719613ce4a5b4f68\v!10.0.17763.1911.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1b71c1e41bc..262307cf262_31bf3856ad364e35_10.0.17763.1911_15ab363898eff242.
RegistryScript:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 7 datablocks.
Finish time: 2024-03-27 09:34:06.055
Script hash: vJ2BrTUyW6hkouTnm334jy66YONc/BgR/Bcvvvd53wE=
----------------------EOF-----------------------

Gary R · Mar 27, 2024

Please try updating again.

If successful please let me know.

If not, please post the CBS.log created after your uodate attempt.

ebertandy03 · Mar 27, 2024

Attempted again, but still threw a fit.

Attached

Gary R · Mar 27, 2024

Few new things to patch. May take me a while to source them, will get back to you ASAP.

ebertandy03 · Mar 27, 2024

No worries at all. Thank you so much for all your effort!

[SOLVED] Problem installing Cumulative Updates on Server 2019

Active member

Attachments

Active member

Forum Moderator, Security Analyst, Windows Update Analyst

Active member

Attachments

Forum Moderator, Security Analyst, Windows Update Analyst

Active member

Forum Moderator, Security Analyst, Windows Update Analyst

Active member

Forum Moderator, Security Analyst, Windows Update Analyst

Forum Moderator, Security Analyst, Windows Update Analyst

Attachments

Active member

Attachments

Forum Moderator, Security Analyst, Windows Update Analyst

Active member

Attachments

Forum Moderator, Security Analyst, Windows Update Analyst

Forum Moderator, Security Analyst, Windows Update Analyst

Attachments

Active member

Attachments

Forum Moderator, Security Analyst, Windows Update Analyst

Active member

Attachments

Forum Moderator, Security Analyst, Windows Update Analyst

Active member