[SOLVED] Windows update won't update, shows error

T

tsomega9406

Member
Joined
Mar 6, 2023
Posts
12
Hello, I have a windows 10 laptop running version 22H2, and when I tried to download and install windows updates, it says, there were some problems installing updates, but we'll try again later. Show error code (0x800706be), (0x80070490). Errors shown when installing the updates below. I also ran the SFC/scannow command using admin. privelages in cmd, but it says 'there is a system repair pending that requires reboot. Perform reboot and run sfc/scannow again.' After rebooting and re-running the command, it still shows the same thing. Any help would be appreciated. Thank you

A. 2023-02 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 22H2 for x64 based systems (KB5022729) - Error 0x800706be
B. 2023-02 Update for Windows 10 Version 22H2 for x64 based systems (KB4023057)- Error 0x800706be
C. 2023-02 Cumulative Update for Windows 10 Version 22H2 for x64- based Systems (KB5022834)- Error 0x800706ba
 

Attachments

Hi I'm Gary R,


I'm a Security Analyst, and a Windows Update Trainee, and I'd like to help you with your problems.


As a trainee there may be times when my instructions must first be checked by a qualified update expert, before I post them. This will by necessity introduce some delay when/if that occurs, so please be patient.

Please can you do the following .....

  • 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.
  • The file will likely be too large to upload here, if so please upload to a file sharing service.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Please post me the link to the file
 
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

  • Download SFCFix.exe and save it to your desktop.
  • Download the attachment SFCFix.zip and also save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
1p8eDnI.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt
  • Open the file, then copy and paste its content in your next reply.

Next ...

  • Click Search button and type Command Prompt
  • From the results, right click on the Command Prompt icon, and select Run as administrator
  • A Command Window will open.
  • Copy paste the command below into it, then press Enter
  • Dism /Online /Cleanup-Image /RestoreHealth
  • Once DISM has finished running ...
    • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
  • If the file is too large, upload it to a file sharing service, and post me the link.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 

Attachments

When I dragged SFCfix.zip over SFCFix.exe, cmd appeared and it asked if I wanted to communicate with sysnative servers or something, I closed the window and when I re-dragged, it produced the log. Here are the contents from SFCFix.txt below. Also attached is the CBS.log

SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-03-07 07:58:28.971
Microsoft Windows 10 Build 19045 - amd64
Using .zip script file at C:\Users\M\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\Package_1_for_KB5022502~31bf3856ad364e35~amd64~~10.0.4614.6.cat
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\Package_1_for_KB5022502~31bf3856ad364e35~amd64~~10.0.4614.6.mum
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\Package_5_for_KB5020872~31bf3856ad364e35~amd64~~10.0.4590.4.cat
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\Package_5_for_KB5020872~31bf3856ad364e35~amd64~~10.0.4590.4.mum
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4590.4.cat
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4590.4.mum
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4605.1.cat
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4605.1.mum
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4614.6.cat
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4614.6.mum

Successfully copied file C:\Users\M\AppData\Local\niemiro\Archive\Packages\Package_1_for_KB5022502~31bf3856ad364e35~amd64~~10.0.4614.6.cat to C:\Windows\Servicing\Packages\Package_1_for_KB5022502~31bf3856ad364e35~amd64~~10.0.4614.6.cat.
Successfully copied file C:\Users\M\AppData\Local\niemiro\Archive\Packages\Package_1_for_KB5022502~31bf3856ad364e35~amd64~~10.0.4614.6.mum to C:\Windows\Servicing\Packages\Package_1_for_KB5022502~31bf3856ad364e35~amd64~~10.0.4614.6.mum.
Successfully copied file C:\Users\M\AppData\Local\niemiro\Archive\Packages\Package_5_for_KB5020872~31bf3856ad364e35~amd64~~10.0.4590.4.cat to C:\Windows\Servicing\Packages\Package_5_for_KB5020872~31bf3856ad364e35~amd64~~10.0.4590.4.cat.
Successfully copied file C:\Users\M\AppData\Local\niemiro\Archive\Packages\Package_5_for_KB5020872~31bf3856ad364e35~amd64~~10.0.4590.4.mum to C:\Windows\Servicing\Packages\Package_5_for_KB5020872~31bf3856ad364e35~amd64~~10.0.4590.4.mum.
Successfully copied file C:\Users\M\AppData\Local\niemiro\Archive\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4590.4.cat to C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4590.4.cat.
Successfully copied file C:\Users\M\AppData\Local\niemiro\Archive\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4590.4.mum to C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4590.4.mum.
Successfully copied file C:\Users\M\AppData\Local\niemiro\Archive\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4605.1.cat to C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4605.1.cat.
Successfully copied file C:\Users\M\AppData\Local\niemiro\Archive\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4605.1.mum to C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4605.1.mum.
Successfully copied file C:\Users\M\AppData\Local\niemiro\Archive\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4614.6.cat to C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4614.6.cat.
Successfully copied file C:\Users\M\AppData\Local\niemiro\Archive\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4614.6.mum to C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4614.6.mum.

Successfully restored ownership for C:\Windows\Servicing\Packages\Package_1_for_KB5022502~31bf3856ad364e35~amd64~~10.0.4614.6.cat
Successfully restored permissions on C:\Windows\Servicing\Packages\Package_1_for_KB5022502~31bf3856ad364e35~amd64~~10.0.4614.6.cat
Successfully restored ownership for C:\Windows\Servicing\Packages\Package_1_for_KB5022502~31bf3856ad364e35~amd64~~10.0.4614.6.mum
Successfully restored permissions on C:\Windows\Servicing\Packages\Package_1_for_KB5022502~31bf3856ad364e35~amd64~~10.0.4614.6.mum
Successfully restored ownership for C:\Windows\Servicing\Packages\Package_5_for_KB5020872~31bf3856ad364e35~amd64~~10.0.4590.4.cat
Successfully restored permissions on C:\Windows\Servicing\Packages\Package_5_for_KB5020872~31bf3856ad364e35~amd64~~10.0.4590.4.cat
Successfully restored ownership for C:\Windows\Servicing\Packages\Package_5_for_KB5020872~31bf3856ad364e35~amd64~~10.0.4590.4.mum
Successfully restored permissions on C:\Windows\Servicing\Packages\Package_5_for_KB5020872~31bf3856ad364e35~amd64~~10.0.4590.4.mum
Successfully restored ownership for C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4590.4.cat
Successfully restored permissions on C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4590.4.cat
Successfully restored ownership for C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4590.4.mum
Successfully restored permissions on C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4590.4.mum
Successfully restored ownership for C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4605.1.cat
Successfully restored permissions on C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4605.1.cat
Successfully restored ownership for C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4605.1.mum
Successfully restored permissions on C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4605.1.mum
Successfully restored ownership for C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4614.6.cat
Successfully restored permissions on C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4614.6.cat
Successfully restored ownership for C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4614.6.mum
Successfully restored permissions on C:\Windows\Servicing\Packages\Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4614.6.mum
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 10 datablocks.
Finish time: 2023-03-07 07:58:29.910
Script hash: b6aZyxBhUoair51lPocJwnMvMflhN3EUt8aQixLir+I=
----------------------EOF-----------------------
 

Attachments

Looking over your latest logs, may take a while. Back ASAP.
 
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
1p8eDnI.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt
  • Open the file, then copy and paste its content in your next reply.

Next ...

  • Click Search button and type Command Prompt
  • From the results, right click on the Command Prompt icon, and select Run as administrator
  • A Command Window will open.
  • Copy paste the command below into it, then press Enter
  • Dism /Online /Cleanup-Image /RestoreHealth
  • Once DISM has finished running ...
    • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
  • If the file is too large, upload it to a file sharing service, and post me the link.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 

Attachments

Unless you've deleted the copy you've already used for the fix I posted in post #4, you should still have a copy of SFCFix.exe on your Desktop.

If you have deleted it (and I certainly did not ask you to do so), then by all means download a new copy.
 
Here's is the SFCFix log and attached CBS.log

SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-03-07 13:41:32.990
Microsoft Windows 10 Build 19045 - amd64
Using .zip script file at C:\Users\M\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\HyperV-HypervisorPlatform-Package~31bf3856ad364e35~amd64~~10.0.19041.2311.cat
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\HyperV-HypervisorPlatform-Package~31bf3856ad364e35~amd64~~10.0.19041.2311.mum
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\Microsoft-Hyper-V-Hypervisor-Package~31bf3856ad364e35~amd64~~10.0.19041.2364.cat
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\Microsoft-Hyper-V-Hypervisor-Package~31bf3856ad364e35~amd64~~10.0.19041.2364.mum
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.19041.2364.cat
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.19041.2364.mum

Successfully copied file C:\Users\M\AppData\Local\niemiro\Archive\Packages\HyperV-HypervisorPlatform-Package~31bf3856ad364e35~amd64~~10.0.19041.2311.cat to C:\Windows\Servicing\Packages\HyperV-HypervisorPlatform-Package~31bf3856ad364e35~amd64~~10.0.19041.2311.cat.
Successfully copied file C:\Users\M\AppData\Local\niemiro\Archive\Packages\HyperV-HypervisorPlatform-Package~31bf3856ad364e35~amd64~~10.0.19041.2311.mum to C:\Windows\Servicing\Packages\HyperV-HypervisorPlatform-Package~31bf3856ad364e35~amd64~~10.0.19041.2311.mum.
Successfully copied file C:\Users\M\AppData\Local\niemiro\Archive\Packages\Microsoft-Hyper-V-Hypervisor-Package~31bf3856ad364e35~amd64~~10.0.19041.2364.cat to C:\Windows\Servicing\Packages\Microsoft-Hyper-V-Hypervisor-Package~31bf3856ad364e35~amd64~~10.0.19041.2364.cat.
Successfully copied file C:\Users\M\AppData\Local\niemiro\Archive\Packages\Microsoft-Hyper-V-Hypervisor-Package~31bf3856ad364e35~amd64~~10.0.19041.2364.mum to C:\Windows\Servicing\Packages\Microsoft-Hyper-V-Hypervisor-Package~31bf3856ad364e35~amd64~~10.0.19041.2364.mum.
Successfully copied file C:\Users\M\AppData\Local\niemiro\Archive\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.19041.2364.cat to C:\Windows\Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.19041.2364.cat.
Successfully copied file C:\Users\M\AppData\Local\niemiro\Archive\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.19041.2364.mum to C:\Windows\Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.19041.2364.mum.

Successfully restored ownership for C:\Windows\Servicing\Packages\HyperV-HypervisorPlatform-Package~31bf3856ad364e35~amd64~~10.0.19041.2311.cat
Successfully restored permissions on C:\Windows\Servicing\Packages\HyperV-HypervisorPlatform-Package~31bf3856ad364e35~amd64~~10.0.19041.2311.cat
Successfully restored ownership for C:\Windows\Servicing\Packages\HyperV-HypervisorPlatform-Package~31bf3856ad364e35~amd64~~10.0.19041.2311.mum
Successfully restored permissions on C:\Windows\Servicing\Packages\HyperV-HypervisorPlatform-Package~31bf3856ad364e35~amd64~~10.0.19041.2311.mum
Successfully restored ownership for C:\Windows\Servicing\Packages\Microsoft-Hyper-V-Hypervisor-Package~31bf3856ad364e35~amd64~~10.0.19041.2364.cat
Successfully restored permissions on C:\Windows\Servicing\Packages\Microsoft-Hyper-V-Hypervisor-Package~31bf3856ad364e35~amd64~~10.0.19041.2364.cat
Successfully restored ownership for C:\Windows\Servicing\Packages\Microsoft-Hyper-V-Hypervisor-Package~31bf3856ad364e35~amd64~~10.0.19041.2364.mum
Successfully restored permissions on C:\Windows\Servicing\Packages\Microsoft-Hyper-V-Hypervisor-Package~31bf3856ad364e35~amd64~~10.0.19041.2364.mum
Successfully restored ownership for C:\Windows\Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.19041.2364.cat
Successfully restored permissions on C:\Windows\Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.19041.2364.cat
Successfully restored ownership for C:\Windows\Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.19041.2364.mum
Successfully restored permissions on C:\Windows\Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.19041.2364.mum
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 16 datablocks.
Finish time: 2023-03-07 13:41:33.606
Script hash: G8Upf+SMOiSdW0idqXoaSC+8nbPrPr7mrJLqTXLSVXk=
----------------------EOF-----------------------
 

Attachments

Going to have to consult on what I'm finding in your log, could take a while, I'll get back to you as soon as I can, but it may not be today.


In the meantime can you please do the following ...

  • Restart the computer.
  • Run the command SFC /SCANNOW in an elevated command prompt and let me know if it completes.
  • If it fails, attach your latest C:\Windows\Logs\CBS\CBS.log to your next reply.
 
Last edited:
Hopefully, my windows updates will start working and installing updates again. Any idea what the issue is on why windows updates isn't working?

I ran the SFC /SCANNOW and it said 'There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again.' After restarting and re-running the command, it said the same thing. Here is the attached CBS.log, thank you for helping.
 

Attachments

I'd like to take a look at one of your Registry Keys ...

Please Download FRST64 to your Desktop.

  • Start FRST.
  • Hit your Windows Key + R to open a Run window
  • Type Notepad then click OK
  • This will open an empty Notepad document
  • Copy/Paste the following into it (Don't include Code: ) .....
Code: 
ExportKey:HKLM\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\DriverOperations
  • Save it as fixlist.txt to the same location as FRST (must be in this location)
  • Now press the Fix button once and wait.
  • FRST will process fixlist.txt
  • When finished, it will produce a log fixlog.txt in the same folder/directory as FRST64.exe
  • Please post me the log
 
Last edited:
Question, after I downloaded and run FRST64, the default items that are 'checked' are 'Registry', 'Processes', 'Services', 'Internet', 'Drivers', 'One month' and under optional scan, the 'addition.txt' is checked. I already ran the program with those default items selected, by clicking the 'scan' button or did you want me to scan using the 'search registry button'? But I haven't fixed anything yet, because I was a little confused. Because you said you wanted to look at one of the registry keys. Would you like the FRST.log and Addition.log?
 
Last edited:
If you run FRST the way you did (which will not harm your machine), it will just produce two logs .... FRST.txt ... and ... Addition.txt ... I don't need to see either of those.

If you create the ... fixlist.txt ... that I asked you to create, and then click on the ... Fix ... button (on FRST's interface), then it will process that file, and produce a log called ... fixlog.txt

That is the log I need to see.
 
No problem.

Looking at your fixlog, there's a lot for me to go through, so it's probably better if I can look at things directly.

To do that, I need you to post me a copy of your 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, please upload to a file sharing service.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 
Thanks.

May take me a while, back ASAP.
 
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

  • Download the attachment SFCFixScript.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFixScript.zip file over the SFCFix.exe executable and release it.
1p8eDnI.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt
  • Open the file, then copy and paste its content in your next reply.

Next ...

  • Click Search button and type Command Prompt
  • From the results, right click on the Command Prompt icon, and select Run as administrator
  • A Command Window will open.
  • Copy paste the command below into it, then press Enter
  • Dism /Online /Cleanup-Image /RestoreHealth
  • Once DISM has finished running ...
    • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
  • If the file is too large, upload it to a file sharing service, and post me the link.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 

Attachments

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