[SOLVED] any cumulative update error on server 2022 error 0x80070002
- Thread starter bagmf
- Start date
Unfortunately, the CBS log shows no useful information. So please attempt to update again with Process Monitor running.
Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below.
4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
6. Attach also a new copy of the CBS log for the time stamps.
Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below.
4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
6. Attach also a new copy of the CBS log for the time stamps.
It seems the SBS key under the SOFTWARE hive is missing a number of keys as well.
Export SBS (SideBySide) hive
Export SBS (SideBySide) hive
- Click on the Start button and 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.
Code:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide - Once selected, click File > Export....
- Change the Save as type: to Registry Hive Files (*.*).
- Name this file SideBySide (with no file extension) and save it to your Desktop.
- Right-click on the saved file and choose Send > Compressed (zipped) Folder.
- Attach the .ZIP file to your next post.
- If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
Please export the key as HIVE (hiv) file, not as *.REG.
Here's the next fix.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Afterwards reboot the server and 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 reboot the server and 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.
Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
- 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.
Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealthStep 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
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. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealthSo if I understand correctly, you are going to try to replace all the missing VersionIndex keys yourself?
Which source you have used, another server?
The same server, I ran the restorehealth, after the error I opened the cbs.log and verified that the last error was this "
Did I do it wrong?
Rich (BB code):
\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.2305 (WinBuild.160101.0800)\ComponentFamilies\x86_microsoft-windows-l..rstandard.resources_31bf3856ad364e35_en-us_34a1bf53d0bb857c\v!10.0.20348.1'; a:(OBJ_CASE_INSENSITI[gle=0xd0000034]
"
and I took the key and modified the SFCScript script that previously passed by vc but only modifying the path And then SFCscript looked like this:
::
[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.2305 (WinBuild.160101.0800)\ComponentFamilies\x86_microsoft-windows-l..rstandard.resources_31bf3856ad364e35_en-us_34a1bf53d0bb857c]
"SomeUnparsedVersionsExist"=hex:00
[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.2305 (WinBuild.160101.0800)\ComponentFamilies\x86_microsoft-windows-l..rstandard.resources_31bf3856ad364e35_en-us_34a1bf53d0bb857c\v!10.0.20348.1]
@=dword:00002056Did I do it wrong?
Please post a new copy of the COMPONENTS hive to look at.
Upload your COMPONENTS hive.
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.
Please do the following first.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
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. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealthHas Sysnative Forums helped you? Please consider donating to help us support the site!