[SOLVED] Trying to update from Windows 10 Pro Version 22H2 19045.4291 (X64) to 19045.4717 and I'm having problems
- Thread starter Rin
- Start date
Rich (BB code):
RegistryScript::
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS with error code ERROR_ACCESS_DENIED.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS with error code ERROR_ACCESS_DENIED.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS with error code ERROR_ACCESS_DENIED.
Rich (BB code):
2024-08-15 14:39:24, Error CSI 0000001a@2024/8/15:11:39:24.676 (F) Attempting to mark store corrupt with category [l:28 ml:29]'CorruptMajorComponentsBranch'[gle=0x80004005]
2024-08-15 14:39:24, Error CSI 0000001b@2024/8/15:11:39:24.677 (F) onecore\base\wcp\componentstore\storelayout.cpp(4966): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function ComponentStore::CRawStoreLayout::OpenCanonicalDataKey expression: (null)
[gle=0x80004005]Unfortunately, the fix failed. Please do the following.
Step 1. Download
- Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
- Follow the on-screen instructions.
- Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
- Post the logfile ComponentsScanner.txt as attachment into your next reply.
Step 2. Upload your COMPONENTS hive.
- Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
- 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.
- 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.
- If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
Your previous thread at MB-Forums: windows 10 security deleted after installing cracked game
I don't know what happened, but your COMPONENTS hive is badly damaged! So please do the following, to restore the current hive with an older version you've provided earlier includuing the last fix.
Step 1. Replace Components Hive Manually
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.
Step 2. Reboot the system and download
ComponentsScanner and save it to your desktop.
I don't know what happened, but your COMPONENTS hive is badly damaged! So please do the following, to restore the current hive with an older version you've provided earlier includuing the last fix.
Step 1. Replace Components Hive Manually
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 COMPONENTS.ZIP and save to your desktop.
- Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
- Now we have the COMPONENTS file that we will be using to replace your current one.
- Navigate to C:\Windows\System32\config
- Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad.
Note: If you get an error that the file is in use, reboot your computer and then try again. - Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config
Step 2. Reboot the system and download
- Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
- Follow the on-screen instructions.
- Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
- Post the logfile ComponentsScanner.txt as attachment into your next reply.
Hi,
Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Step 2. Reboot the system and download
ComponentsScanner and save it to your desktop.
Step 1.
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.
Step 2. Reboot the system and download
- Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
- Follow the on-screen instructions.
- Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
- Post the logfile ComponentsScanner.txt as attachment into your next reply.
Great, please attempt to update again. 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 again. 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 again. If it fails attach a new copy of the CBS logs.
Here's the next fix for the following Defender component which is missing.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Afterwards attempt to update again. 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 again. 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 again. 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 again. 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 again. 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 again. 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 again. 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 SFCFixScript.txt and save it to your desktop.
- Drag the SFCFixScript.txt 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 again. 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 again. 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 again. 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!