[SOLVED] Win Update keeps requiring reboot and cannot install Net 4.0 or prereq (80070bc9)

[alanlance]

My son's computer (i7-2600 running Windows 7 SP1 x64) would would not update (Please reboot every time a check for updates was done) about a year ago. This was before .Net 4.0 was installed, and he needed it for several programs. I tried everything I could find and, at some point (I am still not sure what made it work) it finally installed Net 4.0. The update loop didn't stop, but we ignored it (mistake, I know).

Recently, his hard drive died, so I replaced it and updated to the latest backup I had (before the fix). At this point, there is no Net 4.0, and the prerequisite (KB958488) will not install while the update loop continues. I have tried many things. Scanned and cleaned with two different programs, tried Clean Boot, reset Updates using the Fixit and manually, used the Widows Update Diagnostic Tool, and the Net Fix Tool (no luck). I ran sfc scan (no problems), ran SURT (CheckSUR says no errors, but I don't understand the rest of the file), and even checked the WindowsUpdate.log file. That shows things progressing until it checks for a handler, and then the 8007BC9 error comes up. I am at a loss and hope someone here will be able to assist; I am out of my depth. I also ran the SFCFix with clean results.

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-08-04 21:51:36.390
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.








AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-08-04 21:53:28.694
----------------------EOF-----------------------


I have attached the CBS folder and the WindowsUpdate.log in the hopes that someone can make more sense of them than I can. My thanks to you all!

 

[BrianDrab]

Hello and welcome

Due to the precise nature of your corruption, you will receive help from a user named LiquidTension. He's one of our senior trainees here who's in his final phrase 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.

 

[alanlance]

Although my son is in a hurry to get his computer back, I am happy to get answers at any pace they are available, so I will be happy to hear from LiquidTension. I have, to my knowledge, tried all of the general methods of correcting this kind of error (though I may have missed one or there may be a combination in a particular order that works), but I imagine, at this stage, that I will need something specific to my situation. I will wait to hear your suggestions, and many thanks,

Alan

 

[LiquidTension]

Hello Alan,

Please do the following:

Clear Transactional Logfiles

Warning: This fix is intended for use on this particular machine. Do not use this fix on any other machine; doing so may cause damage to your Operating System. If you are not the original poster and require assistance, please start your own topic.

• Click the Windows Start
  
  button. Type CMD in the search bar, right-click CMD and click
  
  Run as administrator.
• Copy and paste (right-click the Window + Paste) each bold line below one at a time into the Command Prompt. Press Enter on your keyboard after each line.
• Type Y and press Enter on your keyboard if prompted, "Are you sure?".
• Note: Ignore any failure messages.
  
  fsutil resource setautoreset true %SystemDrive%\
  
  attrib -r -s -h %SystemRoot%\System32\Config\TxR\*
  del %SystemRoot%\System32\Config\TxR\*
  
  attrib -r -s -h %SystemRoot%\System32\SMI\Store\Machine\*
  del %SystemRoot%\System32\SMI\Store\Machine\*.tm*
  del %SystemRoot%\System32\SMI\Store\Machine\*.blf
  del %SystemRoot%\System32\SMI\Store\Machine\*.regtrans-ms

 

[alanlance]

I am so sorry, but, last night, I finally realized I was being stubborn. Since the backup was from a year ago, I was not saving any truly necessary settings, and all the file were accessible. I saved the files to an external disk and did a full reset to factory spec. Now everything works. I really appreciate your willingness to help (folks like you will be the only hope for a large chunk of the current generation of users who feel you should just keep hitting buttons until the warning screen goes away). Thanks so much,

Alan

 

[LiquidTension]

That's quite alright, Alan. I'm pleased you were able to resolve the issues.

Take care.