[SOLVED] Windows Server 2012R2 not updating

x BlueRobot · Apr 25, 2022

kogermd said:
One thing that I noticed is that there is no 6.3.9600.19991 folder under C:\Windows\Servicing\Version.

It shouldn't be now since you've attempted to install the later SSU which is version 20332, although, it seems that a registry transaction hasn't completed properly so the system is in limbo state.

SFCFixScript.txt
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a log should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.[/list]

Afterwards, please attempt to install the failed update again.

kogermd · Apr 25, 2022

Here's the output from running the SFC script:

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-04-25 14:32:40.417
Microsoft Windows Server 2012 R2  - amd64
Using .txt script file at D:\SFCFixScript.txt []




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\c6689d4e730..5e4bfc79fcc_31bf3856ad364e35_6.3.9600.19991_3f75ba6a149c6a3a.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\c6689d4e730..5e4bfc79fcc_31bf3856ad364e35_6.3.9600.19991_3f75ba6a149c6a3a.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\c6689d4e730..5e4bfc79fcc_31bf3856ad364e35_6.3.9600.19991_3f75ba6a149c6a3a.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2022-04-25 14:32:43.918
----------------------EOF-----------------------

After running the script, I was able to install the latest SSU through Windows Update and I now see the 6.3.9600.20332 folder under C:\Windows\Servicing\Version. I then tried to re-run Windows Update to see if it found any new updates, but it's still not finding any. Attached is the CBS log from that run. What should I do next?

kogermd · Apr 25, 2022

One other note, I am now seeing this in my CBS log file:

Code:

=================================
Checking System Update Readiness.

(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\dpx.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\poqexec.exe
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\mspatcha.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\cmiadapter.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\TiFileFetcher.exe
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\timezoneai.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\msdelta.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\CbsMsg.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\cleanupai.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\CbsCore.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\luainstall.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\cmitrust.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\winsockai.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\CntrtextInstaller.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\smiengine.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\drvstore.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\cmiaisupport.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\bfsvc.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\wdscore.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\ws2_helper.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\smipi.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\TiWorker.exe
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\DrUpdate.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\cmiv2.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\wcp.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\wrpint.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\fveupdateai.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\GlobalInstallOrder.xml
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_9e1b57abe2cf97f2\securebootai.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\dpx.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\poqexec.exe
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\mspatcha.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\cmiadapter.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\TiFileFetcher.exe
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\timezoneai.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\msdelta.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\CbsMsg.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\cleanupai.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\CbsCore.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\luainstall.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\cmitrust.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\winsockai.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\CntrtextInstaller.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\smiengine.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\drvstore.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\cmiaisupport.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\bfsvc.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\wdscore.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\ws2_helper.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\WcmTypes.xsd
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\smipi.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\TiWorker.exe
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\DrUpdate.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\cmiv2.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\x86_installed
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\wcp.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\wrpint.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\fveupdateai.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\GlobalInstallOrder.xml
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_9df11c11e2ef1b5b\securebootai.dll
Repair failed: Missing replacement payload.

x BlueRobot · Apr 26, 2022

Let's address those corrupted files first, please find the attached SFCFix below. This is probably a result of that incomplete transaction error you had in your earlier CBS log.

Afterwards, please run sfc /scannow and if reports no errors then please attempt to check for updates again. If no updates appear, then please attach the latest CBS log.

kogermd · Apr 26, 2022

It looks like those "Missing replacement payload" errors went away. I'm still not pulling any Windows Updates after running the SFCFixScript and sfc /scannow. I also ran DISM and it stated that it found/repaired some component store corruption. I ran Windows Update after that as well, still no new updates. Attached is the CBS log from both of those runs (sfc / DISM).

x BlueRobot · Apr 27, 2022

Your CBS log looks okay to me.

kogermd said:
I also ran DISM and it stated that it found/repaired some component store corruption.

Does DISM return with no errors now? If it does, then I'm wondering if you've got that applicability issue you had with the SSU update, here's what I do:

Check what the last update (excluding the SSU updates) was which installed successfully
Find the next available update after that; here's a list of all the updates released for Windows Server 2012 R2
Download the update package from Windows Update catalog
Run the standalone installer (.msu) by double clicking on it while a Process Monitor trace is running
If you get the "not applicable" error then please post the Process Monitor log and the KB you were trying to install

kogermd · Apr 27, 2022

x BlueRobot said:
Does DISM return with no errors now?

Actually, DISM now returns "The component store corruption was repaired." every time that I run it. It also looks like maybe there are some missing packages being reported by DISM/CBS (?). I attached both logs for review. Thanks.

x BlueRobot · Apr 28, 2022

Could you please open a command prompt and enter the following command:

Rich (BB code):

reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex" /s

You can ignore the lines with (w), those are simply warnings and shouldn't cause any issues.

x BlueRobot · Apr 29, 2022

Don't worry about the previous post, I went through the thread and found an older CBS hive you uploaded, and it seems that the PackageIndex is empty, could you please run the attached SFCFixScript? It's very large and therefore SFCFix may appear as it's not doing anything but it is. Please allow it to complete. It can take up to an hour or two, possibly more.

kogermd · Apr 29, 2022

Ran the SFCFixScript your provided. I attached the results from that since it was rather large. Like you mentioned, it did take quite a while to run and complete (over an hour). I tried checking for updates once complete - still no luck there. I then ran DISM and got the same error stating that the "component store corruption was repaired". Still no luck with the updates. Also ran sfc, and same results there. Last thing I did was run Process Monitor while attempting to install the first missing update for the server - attached is the scan from that. I also attached the CBS and DISM logs for review. One thing that I'm seeing in the DISM log now is this:

Code:

2022-04-29 15:44:10, Error                 DISM   DISM Package Manager: PID=6880 TID=4328 Failed opening package @Foundation. - CDISMPackageManager::Internal_CreatePackageByName(hr:0x800f0805)
2022-04-29 15:44:10, Error                 DISM   DISM Package Manager: PID=6880 TID=4328 Failed to get the underlying cbs package. - CDISMPackageManager::OpenPackageByName(hr:0x800f0805)
2022-04-29 15:44:10, Error                 DISM   DISM Package Manager: PID=6880 TID=4328 The specified package is not valid Windows package. - GetCbsErrorMsg
2022-04-29 15:44:10, Error                 DISM   API: PID=8360 TID=10712 Failed to open package - CGetFeaturesCommandObject::InternalExecute(hr:0x800f0805)
2022-04-29 15:44:10, Error                 DISM   API: PID=8360 TID=10712 InternalExecute failed - CBaseCommandObject::Execute(hr:0x800f0805)
2022-04-29 15:44:10, Error                 DISM   API: PID=8360 TID=9640 CGetFeaturesCommandObject internal execution failed - DismGetFeaturesExInternal(hr:0x800f0805)

x BlueRobot · Apr 29, 2022

Thank you for the logs, there is two possible reasons for that error: the package itself is missing from your packages folder or the package subkey is missing from your CBS hive. Could you please provide the latest version of CBS hive as you did before? I'll get the replacement package files for you too.

Export CBS hive

Click on the Start button and in the search box, 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.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
Once selected, click File > Export....
Change the Save as type: to Registry Hive Files (.).
Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
Attach the .ZIP file to your next post.
If the file is too large to upload here, upload to Dropbox or OneDrive or SendSpace and just provide the link here.

kogermd · Apr 30, 2022

Sure thing, here's a link to the latest CBS hive: ComponentBasedServicing.zip

x BlueRobot · May 3, 2022

Could you please run the following SFCFix? It'll will replace the associated packages under %systemroot%\servicing\packages.

kogermd · May 3, 2022

I ran SFCFix with the provided script. Below is the result from running the script. Afterwards, I tried running DISM with the same result. I am still seeing this in the CBS log "Not able to find an installed package package from moniker: @Foundation [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]".

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-05-03 04:51:01.951
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .zip script file at D:\SFCFix.zip []




PowerCopy::
Successfully took permissions for file or folder C:\Windows\servicing\Packages\Microsoft-Windows-Common-Foundation-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cat
Successfully took permissions for file or folder C:\Windows\servicing\Packages\Microsoft-Windows-Common-Foundation-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.mum
Successfully took permissions for file or folder C:\Windows\servicing\Packages\Microsoft-Windows-CommonFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cat
Successfully took permissions for file or folder C:\Windows\servicing\Packages\Microsoft-Windows-CommonFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.mum

Successfully copied file C:\Users\TEMP.DC3N.001\AppData\Local\niemiro\Archive\Packages\Microsoft-Windows-Common-Foundation-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cat to C:\Windows\servicing\Packages\Microsoft-Windows-Common-Foundation-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cat.
Successfully copied file C:\Users\TEMP.DC3N.001\AppData\Local\niemiro\Archive\Packages\Microsoft-Windows-Common-Foundation-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.mum to C:\Windows\servicing\Packages\Microsoft-Windows-Common-Foundation-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.mum.
Successfully copied file C:\Users\TEMP.DC3N.001\AppData\Local\niemiro\Archive\Packages\Microsoft-Windows-CommonFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cat to C:\Windows\servicing\Packages\Microsoft-Windows-CommonFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cat.
Successfully copied file C:\Users\TEMP.DC3N.001\AppData\Local\niemiro\Archive\Packages\Microsoft-Windows-CommonFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.mum to C:\Windows\servicing\Packages\Microsoft-Windows-CommonFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.mum.

Successfully restored ownership for C:\Windows\servicing\Packages\Microsoft-Windows-Common-Foundation-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cat
Successfully restored permissions on C:\Windows\servicing\Packages\Microsoft-Windows-Common-Foundation-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cat
Successfully restored ownership for C:\Windows\servicing\Packages\Microsoft-Windows-Common-Foundation-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.mum
Successfully restored permissions on C:\Windows\servicing\Packages\Microsoft-Windows-Common-Foundation-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.mum
Successfully restored ownership for C:\Windows\servicing\Packages\Microsoft-Windows-CommonFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cat
Successfully restored permissions on C:\Windows\servicing\Packages\Microsoft-Windows-CommonFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cat
Successfully restored ownership for C:\Windows\servicing\Packages\Microsoft-Windows-CommonFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.mum
Successfully restored permissions on C:\Windows\servicing\Packages\Microsoft-Windows-CommonFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.mum
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2022-05-03 04:51:07.782
----------------------EOF-----------------------

x BlueRobot · May 4, 2022

Could you please try the following SFCFixScript?

SFCFixScript.txt
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a log should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.[/list]

kogermd · May 4, 2022

Looks like we're in business now! After running the script and running DISM, I noticed that the "Not able to find an installed package package from moniker: @Foundation [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]" error message went away. I still wasn't seeing any new updates, but I tried installing the next available update (KB5003681) using DISM and it was successful this time. I then did a new check for updates and I'm seeing 27 important updates now. KB5003681 requires a reboot so I'll have to wait until tomorrow's maintenance window to confirm, but it looks like that may have finally fixed it.

x BlueRobot · May 4, 2022

Excellent news! Hopefully those updates install successfully

kogermd · May 5, 2022

Well, mostly good news... all available updates (including the April 2022 security updates) installed successfully, with the exception of one update: KB4339284. That one fails to install with an error code of 800F0831. I'm not sure why that update is trying to install anyways as it's from August 2018.

x BlueRobot · May 6, 2022

Excellent! Could you please provide the latest CBS log and I'll have a look?

kogermd · May 6, 2022

x BlueRobot said:
Excellent! Could you please provide the latest CBS log and I'll have a look?

Yes, I'm feeling much better about this now! Thanks for everything! See attached for the CBS log from last night.

[SOLVED] Windows Server 2012R2 not updating

Administrator

Attachments

Well-known member

Attachments

Well-known member

Administrator

Attachments

Well-known member

Attachments

Administrator

Well-known member

Attachments

Administrator

Administrator

Attachments

Well-known member

Attachments

Administrator

Well-known member

Administrator

Attachments

Well-known member

Administrator

Attachments

Well-known member

Administrator

Well-known member

Administrator

Well-known member

Attachments