[SOLVED] Windows 7 Ultimate x64 Error 80073701 with the update KB4503292

[Alex M.]

Hello,


I get this error 80073701 when I try to apply the update (KB4503292).


Unfortunately I might know why I'm encountering this problem:


I've never had any problems with Windows Update before until a few days ago I was doing the usual "disk cleanup" routine on the driver where the OS is installed (right-click driver, properties, "disk cleanup"), I wasn't happy with the low mb that got cleaned up so I decided to give it another try and at that point the cleanup disk feature found 15 Gigabytes of Windows Update files and asked me if I wanted to delete them. In my ingenuity, I thought it was happening the same thing that happens with NVIDIA drivers, meaning I was storing the old drivers in the computer. So I deleted them all. Next the computer wanted a reboot, and when it was rebooting it tried to apply an update, which it failed. Eventually after an hour of attempting to bypass the "update process" I was able to log back in and it was like nothing happened.

Until I got notified with the update mentioned above and got the error.

Note: when I deleted Windows Update files with the "disk cleanup" the space of the driver barely changed even if it stated it found 15 GB, I had like 23 gb before the cleanup and 21 gb of free space now.



Running the command "sfc /scannow" in the Command Prompt it displays the following sentence "Windows Resource Protection did not find any integrity violations".


SURT returned that a number of packages are missing (1400+) (CBS log and SURT log are attached in a zip below).


I was trying to manually download all of the missing packages but it was taking ages, and I don't even know if I have enough space to store them all.




Is there a way to fix this problem or it's better to do a clean reinstall of the OS?


Thanks a lot!


Alex.

 

[Sysnative Windows Update]

Hello and welcome!

Due to the precise nature of your corruption, you will receive help from a user named writhziden. He's one of our senior trainees here who's in his final phase of his studies and needs to gain some real world experience in specific areas of Windows Update. This means that he'll be assisting you, but that I will first need to double check and approve his fixes before he posts them to you. If anything this is a good thing for you because it means that you've got at least two of us watching over your thread, but it will unfortunately add a slight delay between each reply. I hope that you understand and can accept the need for us to train up new members in this way in order to carry on doing what we do here, however, if for any reason you object to this setup, I will happily take on your thread myself.

Thank you very much for your understanding. We'll be with you very shortly.

 

[writhziden]

Hello, and welcome to Sysnative Forums. Thank you for being patient while we analyzed your files and created an initial fix. Below are the recommended steps to begin the process for fixing your update error.

Step 1
Run SFCFix with the included SFCFix.zip archive

WARNING! The following fix is specific to the user's system in this thread only and may be harmful to apply to another system. If you came across this thread and have a similar issue, start your own thread by following the Windows Update Forum Posting Instructions

• Download using the link to SFCFix.zip (see the next step for the link) and save it on your desktop.
• LINK -----> SFCFix.zip (also attached at the bottom of this post)
• Save any work you have open, and close all programs.
• 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.
• Open the file, then copy and paste its content in your next reply.

Step 2
System Update Readiness Tool (SUR) Windows 7 - 64-Bit

1. Download and run the following file.
2. When it asks you if you wish to install, please answer Yes. Note: It could take several hours to run. Please don't cancel it.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
5. Please do not install any other updates until we analyze the CheckSUR log and recommend you do so.

Please Note:: if the file is too big to upload to your next post, please upload via Sendspace and just provide the link here.

 

[Alex M.]

Hello to you both!

Thank you for the quick response, I'm glad I can contribute in some sort.

I cannot copy-paste the text from the SFCFix.txt because it's too long.

I will attach it in the zip file with the CheckSUR log.


Waiting for futher instructions :)

 

[writhziden]

CheckSUR shows quite a few items were fixed, but there are still several items CheckSUR reports as having errors. Follow the same procedure as you did previously but with the new SFCFix archive.

Step 1
Run SFCFix with the included SFCFix.zip archive

WARNING! The following fix is specific to the user's system in this thread only and may be harmful to apply to another system. If you came across this thread and have a similar issue, start your own thread by following the Windows Update Forum Posting Instructions

• Download using the link to SFCFix.zip (see the next step for the link) and save it on your desktop.
• LINK -----> SFCFix.zip
• Save any work you have open, and close all programs.
• 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.
• Open the file, then copy and paste its content in your next reply.

Step 2
System Update Readiness Tool (SUR) Windows 7 - 64-Bit

1. As before, run Windows6.1-KB947821-v34-x64 (SUR).
2. When it asks you if you wish to install, please answer Yes. Note: It could take several hours to run. Please don't cancel it.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
5. Please do not install any other updates until we analyze the CheckSUR log and recommend you do so.

Please Note:: if the file is too big to upload to your next post, please upload via Sendspace and just provide the link here.

 

[Alex M.]

Hello,

As before the text in the file SFCFix.txt is too long and it won't let me post it in this reply.

I have attached it with the CheckSUR.log.

Thank you for your time.

Regards,

Alex.

 

[writhziden]

Summary:
Seconds executed: 4285
Found 946 errors
Fixed 500 errors
CBS MUM Missing Total count: 946
Fixed: CBS MUM Missing. Total count: 500
Fixed: CBS Paired File. Total count: 500

CheckSUR is showing that we're getting closer to fixing the primary set of missing update files. Proceed with the steps below using the new SFCFix archive.

Step 1
Run SFCFix with the included SFCFix.zip archive

WARNING! The following fix is specific to the user's system in this thread only and may be harmful to apply to another system. If you came across this thread and have a similar issue, start your own thread by following the Windows Update Forum Posting Instructions

• Download using the link to SFCFix.zip (see the next step for the link) and save it on your desktop.
• LINK -----> SFCFix.zip
• Save any work you have open, and close all programs.
• 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.
• Open the file, then copy and paste its content in your next reply. If the content is too long to post, attach it with your CheckSUR log file from Step 2.

Step 2
System Update Readiness Tool (SUR) Windows 7 - 64-Bit

1. As before, run Windows6.1-KB947821-v34-x64 (SUR).
2. When it asks you if you wish to install, please answer Yes. Note: It could take several hours to run. Please don't cancel it.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
5. Please do not install any other updates until we analyze the CheckSUR log and recommend you do so.

Please Note:: if the file is too big to upload to your next post, please upload via Sendspace and just provide the link here.

 

[Alex M.]

Hello!

I have attached the files SFCFix.text and CheckSUR.log.

This time the installation from the System Update Readiness Tool didn't last hours but only a couple of minutes :)

Again thank you for your time.

Waiting for further instructions.

 

[writhziden]

All looks good with your logs. Go ahead and see how things go with updating.

If updating fails, please provide your CBS log Text Document file:

Export/Upload your CBS log file

Read More:

1. On Windows 8 and Windows 10, press the Windows key, type This PC, and press Enter.
   On Windows Vista and Windows 7, click the Start button then click Computer.
2. Double-click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder.
3. Find and double click on the Logs folder.
4. Find and double click on the CBS folder.
5. Right-click on the CBS Text Document file, and select Copy.
6. Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS Text Document file appear on your Desktop called CBS.
7. Right-click on this new Text Document file, and navigate through Send to, and select Compressed (zipped) folder.
8. A new file, also called CBS (CBS.zip), but this time with a different icon, will be created on your desktop.
9. Attach the CBS.zip file.
   Note: If your CBS.zip is larger than about 7MB then you will need to upload your file to a hosting service and provide a link instead. See “What to do if your CBS log file is too large to upload” below.

What to do if your CBS log file is too large to upload

Read More:

In some instances you will be unable to upload your CBS log file to our forum because it is too large.
To work around this problem you need to use a file sharing service to upload your attachment and then provide the link that is generated by the hosting service in your post.
Several file sharing options are listed below (they are clickable links), however you are not limited to these:

Microsoft OneDrive
Google Drive
Dropbox
ExpireBox
SendSpace
WeTransfer

 

[Alex M.]

I still got the error 80073701 when trying to do the update.

Is it normal that the CBS file is big and its getting bigger every minute?

I have uploaded here:

CBS.log

 

[writhziden]

Yes, the CBS log tends to grow each time updates are installed and/or a CBS verification scan is performed. Windows will manage the size to some extent by creating CBS persist files that contain older log entries as CBS.log gets too big.

It is also not unexpected that you still ran into error 80073701. The fixes applied so far were done to reconstruct the update files for various updates that hopefully installed correctly. SFCFix and the System Update Readiness Tool have fixed the majority of the issues, but at least one still remains as seen in the CBS log.

2019-06-23 21:45:43, Info CBS Failed to pin deployment while resolving Update: 4493472-18_neutral_LDR from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

KB4493472 is not installed properly on your system, and we will need to remove the problematic pieces of the update. To do so, I will need a registry search output from you:

FRST Registry Search

1. Click your Start button and type in cmd. Press Enter.
2. Copy paste the following into the Command Prompt:
   
   reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
3. Please download Farbar Recovery Scan Tool and save it to your Desktop.
   Note: You need to run the 64-bit Version so please ensure you download that one.
4. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
5. Copy and paste KB4493472 into the Search box and click the Search Registry button.
6. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.

 

[Alex M.]

I understand, thank you for clarifying how the CBS log works.

Attached the SearchReg.txt as requested. :)

 

[writhziden]

Happy to answer any questions you might have.

Below is the fix for update KB4493472.

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system

1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
   Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
   Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Try to install updates again, and if any fail, attach the CBS.log.

 

[Alex M.]

Hello!

The installation was a success after performing the fix and it looks like everything is back to normal!

I don't think you need the Fixlog.txt anymore but I have attached it anyway.

Is it safe to delete the FRST64.exe, SFCFix.exe now that the issue is resolved? Are there any other files I could delete (I saw new folders in the C:\Windows folder like CheckSUR)? I noticed the OS driver has increased in size by almost 2 GB.

 

[writhziden]

It is safe to remove SFCFix.exe, but there is a special procedure for FRST64.exe removal.

1. Rename FRST64.exe to uninstall.exe
2. Run uninstall.exe to remove FRST64 files and folders with the tool
3. Reboot your computer to complete the process

You can also remove CBSPersist logs and CheckSUR.Persist logs from C:\Windows\Logs\CBS. Make sure to leave CBS.log intact, and only clean up the logs that are currently there. Future logs should be kept in place in case you run into other update errors and the logs need analysis to provide fixes.

 

[Alex M.]

Alright I have successfully removed it.

I'd like to thank you once again for your awesome support and time. This forum is great!

 

[writhziden]

Very happy we were able to help you resolve your update troubles. Take care!