[SOLVED] Server 2019 Software Protection Fails

GFink

New member
Joined
Apr 19, 2023
Posts
3
Probably not the correct forum for this post as Windows Update is only part of the overall issue. I have a Windows server 2019 with Remote Desktop Services installed. Windows will no longer active, not will RD licensing recognize the installed license CALs. The Software Protection service will not start. Googling suggests running "DISM /Online /Cleanup-Image /RestoreHealth /SourceD:\sources\install.wim", where the source is the mounted Server 2019 ISO. This fails:

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.3469


[== 4.5% ]

Error: 14098

The component store has been corrupted.

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

The errors in the DISM log are:

DISM Package Manager: Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80073712)
DISM Package Manager: Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x80073712)
DISM Package Manager: Failed to restore the image health. - CPackageManagerCLIHandler:: ProcessCmdLine_CleanupImage(hr:0x80073712)
DISM Package Manager: Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80073712)
DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80073712

Looking at the C:\Windows\System32\Tasks\Microsoft\Windows folder, there are many missing folders, including the SoftwareProtectionPlatform folder for the Software Protection service. This is what lead me to use DISM to repair the installation.

I have downloaded and run the SFCFix.exe tool. Below are the results:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-04-19 12:27:49.963
Microsoft Windows Server 10 Build 17763 - amd64
Not using a script file.




AutoAnalysis::
WARNING: Failed to check store directories with return code 1 and error code ERROR_FILE_NOT_FOUND. COMPONENTS hive may be corrupt.


WARNING: Components hive failed size test and may be corrupt.





SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.



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 0 datablocks.
Finish time: 2023-04-19 12:48:07.538
----------------------EOF-----------------------

System Restore Points are not available, and I hesitate to attempt a system restore using the install media because I cannot export the RD license CALs.
 
Here are the results from the ComponentScanner:

ComponentsScanner Version 1.5.1.0 by sysnative.com
Windows Version: Windows Server 2019 Standard x64 (10.0.17763.3469)
Start time: 2023-04-19T15:29:00
Hive scanned: %windir%\System32\config\COMPONENTS
Number of keys: 2
Number of values: 0

==== Critical Errors ====
COMPONENTS hive is very small (<6MB). This could indicate major corruption & large missing sections of data
COMPONENTS hive contains no parsable registry values
Critical registry key "COMPONENTS\CanonicalData\Catalogs" does not exist or could not be loaded
Critical registry key "COMPONENTS\CanonicalData\Deployments" does not exist or could not be loaded
Critical registry key "COMPONENTS\DerivedData\Components" does not exist or could not be loaded
Critical registry key "COMPONENTS\DerivedData\VersionedIndex" does not exist or could not be loaded
Critical registry key "COMPONENTS\ServicingStackVersions" does not exist or could not be loaded
Critical registry key "COMPONENTS\Installers" does not exist or could not be loaded

==== Corrupt Key Names ====
None

==== Corrupt Value Names ====
None

==== Corrupt Value Data Type ====
None

==== Corrupt Value Data ====
None

==== Repair Log ====
No possible repairs

==== Warnings ====
None


Storing 0KB in C:\Users\colgdf\AppData\Local\Sysnative\ComponentsScanner

Finish Time: 2023-04-19T15:29:11. Corruption scan time: 0.5606418s
===========================EOF===========================
 
Unfortunately, it seems that your entire COMPONENTS hive has been corrupted beyond repair. The only two options are to attempt to restore an older COMPONENTS hive from a backup, although, this can cause additional problems in itself; or alternatively, you will need to a complete clean install.
 
Thank you for taking the time to look at my issue. Have a wonderful day.
 

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

Back
Top