[SOLVED] Windows 2019 Server - Unable to run MS Updates
- Thread starter sfg
- Start date
Hi,
Here's the next fix.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
Here's the next fix.
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.
Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
Hi,
In cases like this we'll need to replace multiple components, so here's the next fix.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
In cases like this we'll need to replace multiple components, so here's the next fix.
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.
Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
Here's the next fix.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
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.
Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
Here's the next fix.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
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.
Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
Hi,
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
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.
Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
Hi,
As mentioned earlier, we need to repair several components to resolve this issue. That said this is a common issue with server 2019 which were installed with an (evaluation) ISO containing certain language packs which were not fully installed. This involves mostly asian language packs, like the example below.
Note: the guide provided by Microsoft will not work most of the times, so the remaining option is to replace all the components manually reported into the CBS.log.
Please let me know what you want to do, this because I have a VM running to provide all the components.
Source: June 11, 2019—KB4503327 (OS Build 17763.557) - Microsoft Support
As mentioned earlier, we need to repair several components to resolve this issue. That said this is a common issue with server 2019 which were installed with an (evaluation) ISO containing certain language packs which were not fully installed. This involves mostly asian language packs, like the example below.
Note: the guide provided by Microsoft will not work most of the times, so the remaining option is to replace all the components manually reported into the CBS.log.
Please let me know what you want to do, this because I have a VM running to provide all the components.
Rich (BB code):
2024-05-10 08:45:40, Error CSI 00000063 (F) Can not identify matching versions for component Microsoft.Windows.ServerManager.Common.resources, version 10.0.17763.5328, arch msil, culture [l:5]'ja-JP', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2024-05-10 08:45:40, Error CSI 00000064@2024/5/10:13:45:40.832 (F) Attempting to mark store corrupt with category [l:21 ml:22]'CorruptComponentValue'[gle=0x80004005]
2024-05-10 08:45:40, Error CSI 00000065@2024/5/10:13:45:40.832 (F) onecore\base\wcp\componentstore\storelayout.cpp(2264): Error 800f0982 [Warning,Facility=15 (0x000f),Code=2434 (0x0982)] originated in function ComponentStore::CRawStoreLayout::AddComponentFile expression: ((SCODE) (((unsigned long)(1)<<31) | ((unsigned long)(15)<<16) | ((unsigned long)(0x982))) )
[gle=0x80004005]Source: June 11, 2019—KB4503327 (OS Build 17763.557) - Microsoft Support
| After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND." | This issue is addressed by updates released June 11, 2019 and later. We recommend you install the latest security updates for your device. Customers installing Windows Server 2019 using media should install the latest Servicing Stack Update (SSU) before installing the language pack or other optional components. If using the Volume Licensing Service Center (VLSC), acquire the latest Windows Server 2019 media available. The proper order of installation is as follows:
Note Updating your device will prevent this issue, but will have no effect on devices already affected by this issue. If this issue is present in your device, you will need to use the workaround steps to repair it. Workaround:
Note If reinstalling the language pack does not mitigate the issue, use the In-Place-Upgrade feature. For guidance, see How to do an in-place upgrade on Windows, and Perform an in-place upgrade of Windows Server. |
Okay, let's go! Here's the next fix.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
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.
Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
Good morning even though it is almost evening here..
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
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.
Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
Here's the next fix.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
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.
Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
Hi,
Here's the next fix.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
Here's the next fix.
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.
Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
Has Sysnative Forums helped you? Please consider donating to help us support the site!