[SOLVED] 2021-08 Servicing Stack Update for Windows Server 2019 for x64-based Systems (KB5005112) - Error 0x800703f1

S

slombards1

Active member
Joined
Aug 12, 2022
Posts
28
Hi,

I have tried numerous fixes found online, such as sfc /scannow methods & have now tried your SFCFix.exe tool.
I receive error : 1009 and informed that "the configuration registry db is corrupt"
The DISM log file can be found .... & then console does nothing else.

I have attached the log file.

Your assistance will be greatly appreciated.

Many Thx
Sean
 

Attachments

Rich (BB code): 
2022-08-10 10:53:50, Info                  CBS    Plan: FOD installation from expanded folder, do not move file: Microsoft-Windows-LanguageFeatures-OCR-en-us-Package~31bf3856ad364e35~amd64~~10.0.17763.1
2022-08-10 10:53:50, Info                  CBS    Plan: Force applicability state to absent due to absent limit state on package: Microsoft-Windows-LanguageFeatures-OCR-en-us-Package~31bf3856ad364e35~amd64~~10.0.17763.1
2022-08-10 10:53:50, Info                  CBS    Plan: Package: Microsoft-Windows-LanguageFeatures-OCR-en-us-Package~31bf3856ad364e35~amd64~~10.0.17763.1, current: Installed, pending: Default, start: Installed, applicable: Absent, targeted: Absent, limit: Absent
2022-08-10 10:53:50, Info                  CBS    Plan: Force package:Microsoft-Windows-LanguageFeatures-OCR-en-us-Package~31bf3856ad364e35~amd64~~10.0.17763.1, update: 820a90c0a96c46216b8530b1db2bf24e into absent state since package state is absent
2022-08-10 10:53:50, Info                  CBS    Plan: Package: Microsoft-Windows-LanguageFeatures-OCR-en-us-Package~31bf3856ad364e35~amd64~~10.0.17763.1, Update: 820a90c0a96c46216b8530b1db2bf24e, current: Installed, pending: Default, start: Installed, applicable: Absent, targeted: Absent, limit: Absent, selected: Default
2022-08-10 10:53:50, Info                  CBS    Plan: Start to process package watchlist.
2022-08-10 10:53:50, Info                  CBS    Plan: Package Microsoft-Windows-LanguageFeatures-Basic-en-us-Package~31bf3856ad364e35~amd64~~10.0.17763.1 declares capability Language.Basic~~~en-US~0.0.1.0 and it is still required by package: Microsoft-Windows-LanguageFeatures-Handwriting-en-us-Package~31bf3856ad364e35~amd64~~10.0.17763.1, cannot remove. [HRESULT = 0x800f0825 - CBS_E_CANNOT_UNINSTALL]
2022-08-10 10:53:50, Info                  CBS    Failed to validate capability removal [HRESULT = 0x800f0825 - CBS_E_CANNOT_UNINSTALL]
2022-08-10 10:53:50, Info                  CBS    Failed to validate the plan. [HRESULT = 0x800f0825 - CBS_E_CANNOT_UNINSTALL]
2022-08-10 10:53:50, Info                  CBS    Failed to plan execution. [HRESULT = 0x800f0825 - CBS_E_CANNOT_UNINSTALL]

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.
 
Hi,

Thanks for your response.

I have loaded Regedit (with admin priv).
When I click on Component Based Servicing, then File, Export (as above).... I am unable to save file to desktop "Cannot export c:\users\slombard\desktop\s:Insufficient Privileges

I am able to save as .reg file just not the hive dump above.

Ideas Please ?


Many Thx
 
Hmm, you shouldn't have any issues with exporting that subkey as a registry hive. Let's try exporting using FRST, please find the instructions below:

FRST Fix
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

A zip file should be produced on your desktop with the date and time of when you ran the script. Please attach the .zip file in your post if it is successfully produced.
 

Attachments

Hi,

I have tried to run with 3 different domain admin accounts, with the same result :

Fix result of Farbar Recovery Scan Tool (x64) Version: 15-08-2022
Ran by adminsean (26-08-2022 14:45:52) Run:2
Running from C:\Users\adminsean\Desktop
Loaded Profiles: adminsean & Sean & konrad
Boot Mode: Normal
==============================================

fixlist content:
*****************
reg: reg save "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing" "%userprofile%\Desktop\CBS.hiv"
zip: %userprofile%\Desktop\CBS.hiv
*****************


========= reg save "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing" "%userprofile%\Desktop\CBS.hiv" =========

ERROR: A required privilege is not held by the client.



========= End of Reg: =========

================== Zip: ===================
"%userprofile%\Desktop\CBS.hiv" => not found
=========== Zip: End ===========

==== End of Fixlog 14:45:52 ====

Zip file is empty

Thx for your trouble & efforts.

Possibly infected ? Although Kaspersky finds nothing.
 
No this isn't anything to do with any infection, it's how your permissions have been set up on the server. The only thing I can suggest is to take ownership of the subkey and then export that way.
 
Taken Ownership of key & all sub-keys, no change - same result as before
 

Attachments

  • Screenshot 2022-08-31 060343.png
    Screenshot 2022-08-31 060343.png
    29.5 KB · Views: 0
  • Screenshot 2022-08-31 060606.png
    Screenshot 2022-08-31 060606.png
    40.6 KB · Views: 0
On a side note, this server is running in a Hyper-V environment.
Before running the last attempted fix, I did restart the virtual host (the Server in question).
 
Let's just query it manually using command prompt for now. Could you please enter the following commands and then post their output in your next post:

Rich (BB code): 
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Features on Demand\Removed FOD Markers" /s
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-LanguageFeatures-Basic-en-us-Package~31bf3856ad364e35~amd64~~10.0.17763.1" /s
 
Hi,

First of all, thanks for all your trouble & efforts, trying to resolve this issue.

Regards
Sean


Results below :
C:\Windows\system32>reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Features on Demand\Removed FOD Markers" /s

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Features on Demand\Removed FOD Markers
Language.Basic~~~en-US~0.0.1.0 REG_DWORD 0x1
Language.Speech~~~en-US~0.0.1.0 REG_DWORD 0x1
Language.TextToSpeech~~~en-US~0.0.1.0 REG_DWORD 0x1
Language.OCR~~~en-US~0.0.1.0 REG_DWORD 0x1


C:\Windows\system32>reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-LanguageFeatures-Basic-en-us-Package~31bf3856ad364e35~amd64~~10.0.17763.1" /s

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-LanguageFeatures-Basic-en-us-Package~31bf3856ad364e35~amd64~~10.0.17763.1
InstallClient REG_SZ DISM Package Manager Provider
InstallName REG_SZ Microsoft-Windows-LanguageFeatures-Basic-en-us-Package~31bf3856ad364e35~amd64~~10.0.17763.1.mum
InstallLocation REG_SZ \\?\D:\wd\in\BuildChunkArtifact\80154b57-1148-3590-c1b9-d2ce93ee1fac\amd64fre\NEUTRAL_FEATURES_ON_DEMAND\cabs\Microsoft-Windows-LanguageFeatures-Basic-en-us-Package~31bf3856ad364e35~amd64~~.cab
CurrentState REG_DWORD 0x70
SelfUpdate REG_DWORD 0x0
Visibility REG_DWORD 0x1
InstallTimeHigh REG_DWORD 0x1d44cd3
InstallTimeLow REG_DWORD 0xb3b6f6b9
InstallUser REG_SZ S-1-5-21-1908608623-3820984453-2552962715-1017
LastProgressState REG_DWORD 0x70
LastError REG_DWORD 0x800f0825

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-LanguageFeatures-Basic-en-us-Package~31bf3856ad364e35~amd64~~10.0.17763.1\Owners
Microsoft-Windows-LanguageFeatures-Basic-en-us-Package~31bf3856ad364e35~amd64~~10.0.17763.1 REG_DWORD 0x20070


C:\Windows\system32>
 
Did you intentionally intend to remove the en-us language pack from the system?
 
Hi,

No I did not.

I started at this company 3 months ago & am trying to resolve numerous issues.
I suppose this server is just another example.

Regards
Sean
 
I would attempt to install the en-us language pack again from the features wizard. Let me know how it goes. The reason you're getting that error in your CBS log is because the servicing stack is attempting to remove a package which still has an active dependency.
 
If I try to install feature (Language Pack) through Server Manager, i get the attached error.
 

Attachments

  • Feature Error.png
    Feature Error.png
    301.8 KB · Views: 1
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.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. 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.

Afterwards, please open a command prompt window and enter the following command:

Rich (BB code): 
DISM /Online /Get-Features
 

Attachments

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-09-05 17:28:09.743
Microsoft Windows Server 10 Build 17763 - amd64
Using .txt script file at C:\Users\adminsean\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.17763.1.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.17763.1\Owners.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\System.

WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.17763.1.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.17763.1.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.17763.1\Owners.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.17763.1\Owners.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\System.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\System.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.17763.1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.17763.1\Owners.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\System.
RegistryScript:: directive completed successfully.




Successfully processed all directives.



Failed to process registry database in location 1.
Failed to load registry hive C:\Windows\System32\config\COMPONENTS into key HKEY_LOCAL_MACHINE\COMPONENTS with error code ERROR_BADDB.

Failed to process registry database in location 2 with error code ERROR_FILE_NOT_FOUND.
WARNING: Failed to process registry database in location 3 with error code ERROR_INVALID_HANDLE.
Failed to process registry database in location 4 with error code ERROR_INVALID_HANDLE.
Failed to process registry database in location 4 with error code ERROR_FILE_NOT_FOUND.
Failed to process registry database in location 4 with error code ERROR_FILE_NOT_FOUND.
Failed to process registry database in location 4 with error code ERROR_FILE_NOT_FOUND.


SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2022-09-05 17:28:23.915
Script hash: WY8WuFVfTZOX11C9zQfdFSXWLIVXXkv9NwJpkFpHq7Q=
----------------------EOF-----------------------
 
It seems there is going to be some possible issues with your COMPONENTS hive as well, could you please scan it by following this tutorial.

What was the result of the DISM command?

Rich (BB code): 
DISM /Online /Get-Features
 
Sorry for not posting these results from DISM :

C:\Windows\system32>DISM /Online /Get-Features

Deployment Image Servicing and Management tool
Version: 10.0.17763.1697

Image Version: 10.0.17763.1817

Features listing for package : Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.17763.1

Feature Name : Server-Core
State : Enabled

Feature Name : NetFx4ServerFeatures
State : Enabled


Error: 1009

The configuration registry database is corrupt.

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

C:\Windows\system32>
 
You must log in or register to reply here.

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

Back
Top