[SOLVED] Restoring license.rtf files to allow the DISM RestoreHealth command to finish

C

CoolieCoolster

Member
Joined
Feb 17, 2022
Posts
6
After accidentally deleting several "license.rtf" files, I noticed that the DISM RestoreHealth command would not successfully progress past 62.3%. As I thought this issue could affect other Windows processes, I tried to restore the files using various tools with no avail, such as SFCFix also staying at 62.3% before stating that the source files could not be found. As the issue still persists after a reinstallation of Windows, based on the attached DISM and CBS logs, would a "SFCFix.zip" file used in conjunction with the SFCFix application be able to fix the problem?

Thanks!
 

Attachments

Rich (BB code): 
2022-02-17 05:44:49, Info                  CBS    (p)    CSI Payload Corrupt    (n)            x86_microsoft-windows-l..-oem-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_0ee5283d61e9682c\r\license.rtf
2022-02-17 05:44:49, Info                  CBS    Repair failed: Missing replacement payload.
2022-02-17 05:44:49, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-l..-oem-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_6b03c3c11a46d962\r\license.rtf
2022-02-17 05:44:49, Info                  CBS    Repair failed: Missing replacement payload.
2022-02-17 05:44:49, Info                  CBS    (p)    CSI Payload Corrupt    (n)            x86_microsoft-windows-l..ault-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_6d4c1d6c2f0270ec\r\license.rtf
2022-02-17 05:44:49, Info                  CBS    Repair failed: Missing replacement payload.
2022-02-17 05:44:49, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-l..ault-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_c96ab8efe75fe222\r\license.rtf
2022-02-17 05:44:49, Info                  CBS    Repair failed: Missing replacement payload.
2022-02-17 05:44:49, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_14161e648abddd30\r\license.rtf
2022-02-17 05:44:49, Info                  CBS    Repair failed: Missing replacement payload.
2022-02-17 05:44:49, Info                  CBS    (p)    CSI Payload Corrupt    (n)            x86_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_b7f782e0d2606bfa\r\license.rtf
2022-02-17 05:44:49, Info                  CBS    Repair failed: Missing replacement payload.
2022-02-17 05:44:49, Info                  CBS    (p)    CSI Payload Corrupt    (n)            x86_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_0ccc38a0b2bfc33a\r\license.rtf
2022-02-17 05:44:49, Info                  CBS    Repair failed: Missing replacement payload.
2022-02-17 05:44:49, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_68ead4246b1d3470\r\license.rtf
2022-02-17 05:44:49, Info                  CBS    Repair failed: Missing replacement payload.

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. 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.
3. 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.
4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.
 
The zipped components file is only 8MB, so maybe that's part of the problem? Since it's smaller than one of the log files from before I'll just attach it here for now.
 

Attachments

Thanks and no the size of the COMPONENTS hive appears to be normal. The issue is because those files are missing and unfortunately they appear to have been part of an OOBE update which is no longer available. Do you have any backups or restore points which you can use?
 
SFCFix Script
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 file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - 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 SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

Thanks to @Maxstar for finding the update package!
 

Attachments

x BlueRobot said:
Thanks and no the size of the COMPONENTS hive appears to be normal. The issue is because those files are missing and unfortunately they appear to have been part of an OOBE update which is no longer available. Do you have any backups or restore points which you can use?
Click to expand...
I tried using a restore point before resetting, but unfortunately it didn't seem to fix the issue from what I could tell. Here's the text from the text file:
Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-02-18 09:20:34.306
Microsoft Windows 10 Build 19044 - amd64
Using .zip script file at C:\Users\cooli\Downloads\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\x86_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_b7f782e0d2606bfa\r
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\x86_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_0ccc38a0b2bfc33a\r
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\x86_microsoft-windows-l..ault-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_6d4c1d6c2f0270ec\r
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\x86_microsoft-windows-l..-oem-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_0ee5283d61e9682c\r
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_68ead4246b1d3470\r
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_14161e648abddd30\r
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-l..ault-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_c96ab8efe75fe222\r
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-l..-oem-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_6b03c3c11a46d962\r

Successfully copied file C:\Users\cooli\AppData\Local\niemiro\Archive\x86_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_b7f782e0d2606bfa\r\license.rtf to C:\WINDOWS\WinSxS\x86_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_b7f782e0d2606bfa\r\license.rtf.
Successfully copied file C:\Users\cooli\AppData\Local\niemiro\Archive\x86_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_0ccc38a0b2bfc33a\r\license.rtf to C:\WINDOWS\WinSxS\x86_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_0ccc38a0b2bfc33a\r\license.rtf.
Successfully copied file C:\Users\cooli\AppData\Local\niemiro\Archive\x86_microsoft-windows-l..ault-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_6d4c1d6c2f0270ec\r\license.rtf to C:\WINDOWS\WinSxS\x86_microsoft-windows-l..ault-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_6d4c1d6c2f0270ec\r\license.rtf.
Successfully copied file C:\Users\cooli\AppData\Local\niemiro\Archive\x86_microsoft-windows-l..-oem-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_0ee5283d61e9682c\r\license.rtf to C:\WINDOWS\WinSxS\x86_microsoft-windows-l..-oem-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_0ee5283d61e9682c\r\license.rtf.
Successfully copied file C:\Users\cooli\AppData\Local\niemiro\Archive\amd64_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_68ead4246b1d3470\r\license.rtf to C:\WINDOWS\WinSxS\amd64_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_68ead4246b1d3470\r\license.rtf.
Successfully copied file C:\Users\cooli\AppData\Local\niemiro\Archive\amd64_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_14161e648abddd30\r\license.rtf to C:\WINDOWS\WinSxS\amd64_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_14161e648abddd30\r\license.rtf.
Successfully copied file C:\Users\cooli\AppData\Local\niemiro\Archive\amd64_microsoft-windows-l..ault-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_c96ab8efe75fe222\r\license.rtf to C:\WINDOWS\WinSxS\amd64_microsoft-windows-l..ault-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_c96ab8efe75fe222\r\license.rtf.
Successfully copied file C:\Users\cooli\AppData\Local\niemiro\Archive\amd64_microsoft-windows-l..-oem-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_6b03c3c11a46d962\r\license.rtf to C:\WINDOWS\WinSxS\amd64_microsoft-windows-l..-oem-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_6b03c3c11a46d962\r\license.rtf.

Successfully restored ownership for C:\WINDOWS\WinSxS\x86_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_b7f782e0d2606bfa\r
Successfully restored permissions on C:\WINDOWS\WinSxS\x86_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_b7f782e0d2606bfa\r
Successfully restored ownership for C:\WINDOWS\WinSxS\x86_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_0ccc38a0b2bfc33a\r
Successfully restored permissions on C:\WINDOWS\WinSxS\x86_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_0ccc38a0b2bfc33a\r
Successfully restored ownership for C:\WINDOWS\WinSxS\x86_microsoft-windows-l..ault-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_6d4c1d6c2f0270ec\r
Successfully restored permissions on C:\WINDOWS\WinSxS\x86_microsoft-windows-l..ault-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_6d4c1d6c2f0270ec\r
Successfully restored ownership for C:\WINDOWS\WinSxS\x86_microsoft-windows-l..-oem-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_0ee5283d61e9682c\r
Successfully restored permissions on C:\WINDOWS\WinSxS\x86_microsoft-windows-l..-oem-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_0ee5283d61e9682c\r
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_68ead4246b1d3470\r
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_68ead4246b1d3470\r
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_14161e648abddd30\r
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-l..fessional.resources_31bf3856ad364e35_10.0.19041.1265_en-us_14161e648abddd30\r
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-l..ault-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_c96ab8efe75fe222\r
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-l..ault-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_c96ab8efe75fe222\r
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-l..-oem-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_6b03c3c11a46d962\r
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-l..-oem-core.resources_31bf3856ad364e35_10.0.19041.1265_en-us_6b03c3c11a46d962\r
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 9 datablocks.
Finish time: 2022-02-18 09:20:35.495
Script hash: tXkuxkakaJvBUuZFAg82097A0b8gIZEYowwD1/I9Cnc=
----------------------EOF-----------------------

Once I have everything working as it should I'll see if I can regularly automatically backup all of the system files to the D drive, as it often seems that the ~1.5GB restore points lack the missing data needed to avoid a system reset...
 
Last edited:
Could you please run SFC again and then attach the CBS log if it fails.

CoolieCoolster said:
Once I have everything working as it should I'll see if I can regularly automatically backup all of the system files to the D drive
Click to expand...
That would be a good idea, you can't really rely on system restore being reliable.
 
The SFC scan successfully finished without detecting issues, as well as finally the RestoreHealth function, so thanks a bunch! What would be the best way to back up the system files to my computer's secondary drive? There's plenty of storage to keep multiple backups to ensure there's always at least one that works, so is there a tool I could use to schedule weekly backups of those files to a folder on the D drive, replacing the oldest one if there's already four backups?
 
Alrighty; thanks for the suggestion! Lastly, in seeing what was restored, I noticed that the C:\Windows\WinSxS\Temp\InFlight folder now has 63,000 files and 43,000 folders. As they seem to stay after using the disk cleanup utility, is it normal for that folder to have that many files and folders?
 
Yes, please don't delete them otherwise you'll create yourself a very big headache. Windows will eventually clean up them in due course with an automated scavenger task which runs in the background.
 
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