Solved IE 11 x64 update failing Error 9c48

[techke10]

Hi and thank you in advance for your help.

I work for a school and am having an issue with IE 11 on many machines I just imaged. IE will not go to internal intranet links and is many times not loading or slowly loading pages. I read in another forum to uninstall the IE 11 update. I did this on one computer, rebooted, then tried to manually install IE 11. However, that didn't work. So, I let it do updates. It pulled down IE 9, IE 10, and IE 11 in windows updater. I performed the updates 3 times, each time with one failing until I am at the final update which is IE 11 and it fails. I performed a registry fix using CCleaner, but no dice. I have seen on some other threads here that after running the CheckSUR tool, there has been a fix given. I was wondering if this is something I need to do for every machine (about 18) or if there is a way I can fix it myself. Thanks for any help!


Machine Specs

HP Compaq DC7800 CMT
Win 7 pro x64
3 gb RAM
500 gb Seagate HD
NVIDIA GeForce Graphics Card
Intel Core 2 Duo
Microsoft Forefront Endpoint

 

[NoelDP]

Please follow the Windows Update Posting Instructions and post the requested data
If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

 

[techke10]

Ok, sorry about not posting correctly. I have run the CheckSUR tool and then ran the SFC check. I have attached both the sfcdetails log as well as the CBS log file(s). I will have to do two more posts below with CBS Log files split because of the size. There is one that I cannot compress lower than 15mb. I may not be able to upload that cab file. I could share it via Google Drive if that would work. Please help me know if there is anything else I need to do. Thanks!

 

[techke10]

Here is the next part of the CBS log file. I couldn't get the one to upload that was 15 mb.

 

[techke10]

Last one.

 

[NoelDP]

No problem

Here's the errors from the SFC scan...

 Line 3587: 2014-09-09 08:18:36, Info                  CSI    00000347 [SR] Repairing 2 components
 Line 3588: 2014-09-09 08:18:36, Info                  CSI    00000348 [SR] Beginning Verify and Repair transaction
 Line 3591: 2014-09-09 08:18:36, Info                  CSI    0000034a [SR] Cannot repair member file [l:22{11}]"winload.exe" of Microsoft-Windows-BootEnvironment-OS-Loader, Version = 6.1.7601.17556, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3594: 2014-09-09 08:18:36, Info                  CSI    0000034c [SR] Cannot repair member file [l:26{13}]"winresume.exe" of Microsoft-Windows-BootEnvironment-OS-Loader, Version = 6.1.7601.17556, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3597: 2014-09-09 08:18:36, Info                  CSI    0000034e [SR] Cannot repair member file [l:30{15}]"winload.exe.mui" of Microsoft-Windows-BootEnvironment-OS-Loader.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

the CheckSUR scan was clear.

I'll post a fix protocol for these errors later.

 

[NoelDP]

I've uploaded a file - t10aa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\t10aa
hit the enter key - if you get a 'Not Found' error try
DIR D:\t10aa
or
DIR E:\t10aa



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY <drive>:\t10aa <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

 

[techke10]

Ok. Followed the above. Again, I have many files so am putting them as separate attachments. There is one Cabinet File that is 15 mb and won't compress to a size that can be uploaded. Let me know if you would like me to share the whole file via Google Drive or OneDrive. Thanks!
#1

 

[techke10]

Here is #2

 

[techke10]

Here is #3

 

[techke10]

And lastly, #4

 

[NoelDP]

SFCdetails is clear - which means that the posted files achieved their desired result.

The oversized CAB file is almost irrelevant, I believe.

When I ask for the CBS.log file - I really do mean only that file, so that's the only one I need uploaded.

The important errors from that this time are these...

 Line 3686: 2014-09-10 07:41:23, Error                 CBS    Failed to create CSI transaction with id: TI5.30395628_631997735:1/. A pending repair transaction already exists, reboot is required [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
 Line 3698: 2014-09-10 07:41:23, Error                 CBS    Failed to call external evaluate applicability on package: WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320, Update: ActiveX-64and32 [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]

Looking at the background data...
There is no data whatever between these two points..

2014-09-09 16:16:36, Error                 CBS    Failed to call external evaluate applicability on package: WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320, Update: ActiveX-64and32 [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
2014-09-10 07:41:23, Info                  CBS    Session: 30395628_631997735 initialized by client WindowsUpdateAgent.

Please upload the C:\Windows\windowsupdate.log file - it may show some details missing from what we've seen so far.

 

[techke10]

Ok. Sorry for the delay. I have attached the WindowsUpdate.log file below. I replied to my other post as well as far as Registry changing programs. We use FOG as an imaging server and I have installed CCleaner as a C drive cleaner but also has a registry fix program. Thanks for all of your help and time.

 

[NoelDP]

Looking at that result, we've cleared a few thing but many are left unresolved.
We need to go back to basics...

Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.
At the Command prompt, type
CHKDSK C: /R
and hit the Enter key.
You will be told that the drive is locked, and the CHKDSK will run at the next boot - hit the Y key, and then reboot.
The CHKDSK will take a few hours depending on the size of the drive, so be patient!
After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot) - then run the SFC again, and post the new CBS.log file.

 

[techke10]

Thanks again for your help! I ran chkdsk c: /r and then ran sfc scan. The CBS.log file is below.

 

[NoelDP]

What happens with updates now? what error code if you just attempt to install the oldest found update?

Please post the C:\Windows\windowsupdate.log

 

[techke10]

Wow! I did the update this morning, and it worked! Thank you so much for your help. I am assuming this means the issue is resolved and will mark solved as long as you think it is. I have attached the WindowsUpdate.log file in case that is something you wanted to see anyway. Thanks again NoelDP for your help! I appreciate it.