[SOLVED] Server 2008 R2 Cant update IE 10

We can try deleting (or at least renaming) the pending.xml file to see if that fixes it but I'm not a big fan of doing that as all of those pending updates will never get applied. It sometimes does fix issues but should be considered a last resort.

Let's get some more logs to review.

Step#1 - FRST Scan
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. Right click to run as administrator. When the tool opens click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please copy and paste log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also paste that along with the FRST.txt into your reply.
 
Here are the FRST logs:

View attachment Addition.txt
View attachment FRST.txt

BrianDrab said:
We can try deleting (or at least renaming) the pending.xml file to see if that fixes it but I'm not a big fan of doing that as all of those pending updates will never get applied. It sometimes does fix issues but should be considered a last resort.

Let's get some more logs to review.

Step#1 - FRST Scan
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. Right click to run as administrator. When the tool opens click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please copy and paste log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also paste that along with the FRST.txt into your reply.
Click to expand...
 
The following is in your application event log.
Code: 
Error: (06/19/2015 00:08:24 PM) (Source: Application Popup) (EventID: 1060) (User: )
Description: \??\C:\Windows\TEMP\mst.sys has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.
Apparently one of the ways this can happen is if you install the 32-bit version of the Dell Open Manage Server Administrator on a 64-bit server. Not sure if this fits your situation but wanted to point it out.

Also wanted to make you aware of the following.

Code: 
Error: (06/21/2015 01:03:39 AM) (Source: VSS) (EventID: 12292) (User: )
Description: Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {e4eb5095-f587-4159-a1d8-2710692fd243} [0x80070422, The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
].

Operation:
   Obtain a callable interface for this provider
   List interfaces for all providers supporting this context
   Delete Shadow Copies
Context:
   Provider ID: {24602736-bed9-4619-91b0-243447c6409c}
   Class ID: {e4eb5095-f587-4159-a1d8-2710692fd243}
   Snapshot Context: 16
   Snapshot Context: 16
   Execution Context: Coordinator


Please zip/attach the following log.
C:\Windows\IE11_main.log
 
Good catch on the Open Manage. I uninstalled the 32-bit version.
Here is the log you requested:

BrianDrab said:
The following is in your application event log.
Code: 
Error: (06/19/2015 00:08:24 PM) (Source: Application Popup) (EventID: 1060) (User: )
Description: \??\C:\Windows\TEMP\mst.sys has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.
Apparently one of the ways this can happen is if you install the 32-bit version of the Dell Open Manage Server Administrator on a 64-bit server. Not sure if this fits your situation but wanted to point it out.

Also wanted to make you aware of the following.

Code: 
Error: (06/21/2015 01:03:39 AM) (Source: VSS) (EventID: 12292) (User: )
Description: Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {e4eb5095-f587-4159-a1d8-2710692fd243} [0x80070422, The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
].

Operation:
   Obtain a callable interface for this provider
   List interfaces for all providers supporting this context
   Delete Shadow Copies
Context:
   Provider ID: {24602736-bed9-4619-91b0-243447c6409c}
   Class ID: {e4eb5095-f587-4159-a1d8-2710692fd243}
   Snapshot Context: 16
   Snapshot Context: 16
   Execution Context: Coordinator


Please zip/attach the following log.
C:\Windows\IE11_main.log
Click to expand...
 
I see the following in the log. Since your machine is a server, does it happen to be connected to a corporate WSUS update server to get its updates?

Code: 
00:16.302: INFO:    Process 'C:\Windows\SysNative\dism.exe /online /add-package /packagepath:C:\Windows\TEMP\IE133DD.tmp\IE11-neutral.Downloaded.cab /quiet /norestart' exited with exit code 0x800F081E (-2146498530)
00:16.302: ERROR:   Neutral package installation failed (exit code = 0x800f081e (2148468766)).
 
Thanks. We're going to rename the Pending.xml and see what happens. Please do the following. Note: The computer will reboot after the fix.

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. Download attached file 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).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. 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.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Ok fix ran and rebooted the server. Here is the Fixlog.txt file:


BrianDrab said:
Thanks. We're going to rename the Pending.xml and see what happens. Please do the following. Note: The computer will reboot after the fix.

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. Download attached file 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).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. 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.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
Click to expand...
 
Windows update history.pngNo get a Windows Update Error 0x80073712 immediately after hitting the Install Updates. However in the Update History it lists installing the same update KB2882822 more than 50+ times
 
Thanks. Your Store has been marked Dirty.
Code: 
2015-06-21 18:51:05, Info                  CSI    00000016 Component store has dirty flag; cannot create transactions against it at this time.
2015-06-21 18:51:05, Error                 CSI    00000017@2015/6/21:23:51:05.577 (F) d:\win7sp1_gdr\base\wcp\componentstore\csd_transact.cpp(3070): Store corruption detected in function CCSDirect::CreateTransaction expression: 0
  RegistryCorruption on resource [40]"\Registry\Machine\COMPONENTS\\StoreDirty"[gle=0x80004005]

Please do the following.

Step#1 - Remove Dirty Flag
1. Click on the Start button and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator
3. When command prompt opens, copy and paste the following commands into it, press enter after each

REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
REG DELETE /v HKLM\COMPONENTS\StoreDirty

Step#2 - SFC Scan

  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish or error out before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please zip/attach this to your next post.


Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
The Registry Delete Failed, "invalid key". I manually looked though the registry and the Components Hive was there but did not see this key. I did try the SFC but it failed with "Windows Software Protection could not perform the requested operation".

Does your REG command need an Unload of the Hive? Also I noticed on the Error message in the CSC that there are two backslashes between Components and StoreDirty. Not sure if this is significant?

Reg delete.png
 
No Unload command is needed. I noticed that you had a space before the following REG command. Maybe that's what caused the error?

Capture.JPG
 
andywt said:
I tried niemiro's suggestion. Got a further but it still failed.
View attachment 13501
Click to expand...

That's a reasonably good outcome. The store is designed to self repair over a reboot - that's why the dirty flag exists. Usually this happens well, very occasionally it goes wrong. Since the repair does seem to have succeeded, can you please re-try Windows Update and re-upload a new CBS.log. Hopefully it won't be polluted with store dirty failures this time and we'll be able to make something more of it.
 
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