[SOLVED] Win Server 2008 R2 SP1 - Windows Update fails/IE doesn't work/IE can't be installed

ignorantbliss

Active member
Joined
Oct 2, 2014
Posts
34
Having issues with a server that had been failing to install IE9 updates via Windows Update and additionally failing to install IE10 or IE11.

IE is at a hard fail at this point, and I truly do not know how it got to the point it's in. I came in on the back end after the problems were reported to me. I've tried everything I know, and even opened a call and have engaged Microsoft Support who has been unable to make any headway after being passed around to four different techs now.

I'm coming here hoping that the brilliant minds that have helped me in the past could possibly do it again with something stumping everyone I've worked with on it so far.

IE9 is installed, and does not function. I don't know what brought it to the state it's in, but I know it's been in that state for over a month now. If you open IE, it opens fine - but when you load a page, ANY page, it just closes IE and tries to download the file. Like, if you go to bing.com it tries to download bing_com.htm

You cannot click on "About Internet Explorer" it does nothing. You cannot bring up Internet Options, either from IE, Control Panel, or run/command line.

You cannot install IE10, it fails. You cannot install IE11, it fails. You cannot uninstall IE9.

Other browsers, such as Chrome or Firefox work fine. But anything that is reliant on iexplore.exe or it's subsequent registered DLL's fail.


CheckSUR log below, as well the CBS.zip and SFCFix.txt files can be found on the link below.

https://www.dropbox.com/sh/7jz7yh906dcqx1g/AABGSwYr-JA1uhgA1lkm-adIa?dl=0



Code:
[/COLOR]

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-10-07 14:11


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist
(f)	CBS Registry Error	0x00000002	x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_0.0.0.0_pt	Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect	Failed to open store sub key


Checking Packages
(f)	CBS Registry Error	0x80070103	Package_168_for_KB2570791~31bf3856ad364e35~amd64~~6.1.1.1		failed to get owner for package.


Checking Component Store
(f)	CSI Missing Identity	0x00000000	appid	62530574173..024f01c7b6d_31bf3856ad364e35_9.4.8112.16450_957362e7ecd0b397	
(f)	CSI Manifest Missing	0x00000002	amd64_microsoft-windows-i..explorer-deployment_31bf3856ad364e35_9.4.8112.16421_none_c2658da8ebaeca79.manifest	amd64_microsoft-windows-i..explorer-deployment_31bf3856ad364e35_9.4.8112.16421_none_c2658da8ebaeca79	
(fix)	CSI Manifest Missing	CSI File Replaced	File: amd64_microsoft-windows-i..explorer-deployment_31bf3856ad364e35_9.4.8112.16421_none_c2658da8ebaeca79.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-ie-servicing-x64-7mar14.cab
(f)	CSI Missing Winning Component Key	0x00000000	amd64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_9.4.8112.16506_none_76a1d4ef74621889		
(f)	CSI Missing Winning Component Key	0x00000000	x86_microsoft-windows-ie-ieproxy_31bf3856ad364e35_9.4.8112.16506_none_a8c92a4d64c231d2		
(f)	CSI Missing Winning Component Key	0x00000000	x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_9.4.8112.16506_none_1a83396bbc04a753		
(f)	CSI Missing Winning Component Key	0x00000000	amd64_microsoft-windows-i..etexplorer-optional_31bf3856ad364e35_9.4.8112.16450_none_0d332a8d8082c4fb		
(f)	CSI Missing Winning Component Key	0x00000000	amd64_microsoft-windows-ie-devtools_31bf3856ad364e35_9.4.8112.16506_none_b05dee42126564ca		
(f)	CSI Missing Winning Component Key	0x00000000	x86_microsoft-windows-ie-ieshims_31bf3856ad364e35_9.4.8112.16506_none_602775e3b46a9840		
(f)	CSI Missing Winning Component Key	0x00000000	amd64_microsoft-windows-ie-ieshims_31bf3856ad364e35_9.4.8112.16506_none_bc4611676cc80976		
(f)	CSI Missing Winning Component Key	0x00000000	amd64_microsoft-windows-ie-extcompat_31bf3856ad364e35_9.4.8112.16506_none_b1688d74a9290cbd		
(f)	CSI Missing Winning Component Key	0x00000000	x86_microsoft-windows-ie-extcompat_31bf3856ad364e35_9.4.8112.16506_none_5549f1f0f0cb9b87		
(f)	CSI Missing Winning Component Key	0x00000000	x86_microsoft-windows-ie-devtools_31bf3856ad364e35_9.4.8112.16506_none_543f52be5a07f394		
(f)	CSI Missing Winning Component Key	0x00000000	amd64_microsoft-windows-ie-ieproxy_31bf3856ad364e35_9.4.8112.16506_none_04e7c5d11d1fa308		


Summary:
Seconds executed: 1017
 Found 15 errors
 Fixed 1 errors
  CSI Manifest Missing Total count: 1
  Fixed: CSI Manifest Missing.  Total count: 1
  CSI Missing Identity Total count: 1
  CBS Registry Error Total count: 2
  CSI Missing Winning Component Key Total count: 11
(w)	Unable to get system disk properties	0x0000045D	IOCTL_STORAGE_QUERY_PROPERTY	Disk Cache	
Customer Experience report successfully uploaded.  Thank you for participating.  For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.
 
I'd like to take a look at the COMPONENTS hive.

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. [sfcfixdownload]Download SFCFix[/sfcfixdownload] (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

https://dl.dropboxusercontent.com/u...eric/Collect/COMPONENTS/SFCFixScript.txt?dl=1
 
Ran, here's the output. Thank you again!

Code:
SFCFix version 2.4.5.0 by niemiro.Start time: 2015-10-07 16:11:53.163
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Using .txt script file at C:\Users\mtiadmintim\Desktop\SFCFixScript.txt [0]








Collect:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-10-07 16:12:50.246
----------------------EOF-----------------------
 
SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

View attachment SFCFix.zip

System Update Readiness Tool (SURT)

Run the System Update Readiness Tool.
This tool will take some time to complete - when it has finished, attach C:\Windows\Logs\CBS\CheckSUR.log with your reply.
 
SFCFix Script Output

Code:
SFCFix version 2.4.5.0 by niemiro.Start time: 2015-10-08 14:21:32.470
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Using .zip script file at C:\Users\mtiadmintim\Desktop\SFCFix.zip [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-i..etexplorer-optional_31bf3856ad364e35_9.4.8112.16450_none_0d332a8d8082c4fb.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_9.4.8112.16506_none_1a83396bbc04a753.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ie-ieproxy_31bf3856ad364e35_9.4.8112.16506_none_04e7c5d11d1fa308.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_9.4.8112.16506_none_76a1d4ef74621889.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ie-devtools_31bf3856ad364e35_9.4.8112.16506_none_543f52be5a07f394.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ie-extcompat_31bf3856ad364e35_9.4.8112.16506_none_5549f1f0f0cb9b87.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ie-ieshims_31bf3856ad364e35_9.4.8112.16506_none_602775e3b46a9840.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\62530574173..024f01c7b6d_31bf3856ad364e35_9.4.8112.16450_957362e7ecd0b397.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ie-ieproxy_31bf3856ad364e35_9.4.8112.16506_none_a8c92a4d64c231d2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ie-devtools_31bf3856ad364e35_9.4.8112.16506_none_b05dee42126564ca.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ie-extcompat_31bf3856ad364e35_9.4.8112.16506_none_b1688d74a9290cbd.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ie-ieshims_31bf3856ad364e35_9.4.8112.16506_none_bc4611676cc80976.


Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-i..etexplorer-optional_31bf3856ad364e35_9.4.8112.16450_none_0d332a8d8082c4fb.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_9.4.8112.16506_none_1a83396bbc04a753.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ie-ieproxy_31bf3856ad364e35_9.4.8112.16506_none_04e7c5d11d1fa308.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_9.4.8112.16506_none_76a1d4ef74621889.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ie-devtools_31bf3856ad364e35_9.4.8112.16506_none_543f52be5a07f394.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ie-extcompat_31bf3856ad364e35_9.4.8112.16506_none_5549f1f0f0cb9b87.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ie-ieshims_31bf3856ad364e35_9.4.8112.16506_none_602775e3b46a9840.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\62530574173..024f01c7b6d_31bf3856ad364e35_9.4.8112.16450_957362e7ecd0b397.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ie-ieproxy_31bf3856ad364e35_9.4.8112.16506_none_a8c92a4d64c231d2.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ie-devtools_31bf3856ad364e35_9.4.8112.16506_none_b05dee42126564ca.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ie-extcompat_31bf3856ad364e35_9.4.8112.16506_none_b1688d74a9290cbd.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ie-ieshims_31bf3856ad364e35_9.4.8112.16506_none_bc4611676cc80976.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-i..etexplorer-optional_31bf3856ad364e35_9.4.8112.16450_none_0d332a8d8082c4fb.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_9.4.8112.16506_none_1a83396bbc04a753.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ie-ieproxy_31bf3856ad364e35_9.4.8112.16506_none_04e7c5d11d1fa308.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_9.4.8112.16506_none_76a1d4ef74621889.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ie-devtools_31bf3856ad364e35_9.4.8112.16506_none_543f52be5a07f394.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ie-extcompat_31bf3856ad364e35_9.4.8112.16506_none_5549f1f0f0cb9b87.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ie-ieshims_31bf3856ad364e35_9.4.8112.16506_none_602775e3b46a9840.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\62530574173..024f01c7b6d_31bf3856ad364e35_9.4.8112.16450_957362e7ecd0b397.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ie-ieproxy_31bf3856ad364e35_9.4.8112.16506_none_a8c92a4d64c231d2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ie-devtools_31bf3856ad364e35_9.4.8112.16506_none_b05dee42126564ca.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ie-extcompat_31bf3856ad364e35_9.4.8112.16506_none_b1688d74a9290cbd.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ie-ieshims_31bf3856ad364e35_9.4.8112.16506_none_bc4611676cc80976.
RegistryScript:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 12 datablocks.
Finish time: 2015-10-08 14:21:34.777
Script hash: UJtl146o9s0zUhVGOZsV+JYFttX8FNT6OAQOGZhC8SI=
----------------------EOF-----------------------





And the CheckSUR results....
Code:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-10-08 14:23


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist
(f)	CBS Registry Error	0x00000002	x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_0.0.0.0_pt	Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect	Failed to open store sub key


Checking Packages
(f)	CBS Registry Error	0x80070103	Package_168_for_KB2570791~31bf3856ad364e35~amd64~~6.1.1.1		failed to get owner for package.


Checking Component Store
(f)	CSI Missing Component Key	0x00000000	amd64_62530574173d29e1dd547024f01c7b6d_31bf3856ad364e35_9.4.8112.16450_none_957362e7ecd0b397	HKLM\Components\DerivedData\Components	
(fix)	CSI Missing Component Key	CSI Registry Item Repaired	Key created.  There will be more reports as values are replaced.
(f)	CSI C Mark Deployment Missing	0x00000000	c!ca681cb528c..b79427f0eb0_31bf3856ad364e35_9.4.8112.16506_48833e7d81cf975a	amd64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_9.4.8112.16506_none_76a1d4ef74621889	
(f)	CSI C Mark Deployment Missing	0x00000000	c!bd83c28417c..494540806be_31bf3856ad364e35_9.4.8112.16506_71037af12065aef9	x86_microsoft-windows-ie-ieproxy_31bf3856ad364e35_9.4.8112.16506_none_a8c92a4d64c231d2	
(f)	CSI C Mark Deployment Missing	0x00000000	c!ca681cb528c..b79427f0eb0_31bf3856ad364e35_9.4.8112.16506_48833e7d81cf975a	x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_9.4.8112.16506_none_1a83396bbc04a753	
(f)	CSI C Mark Deployment Missing	0x00000000	c!b7715e8b5db..912fc4ec2ff_31bf3856ad364e35_9.4.8112.16506_5ab64eab369f0d49	amd64_microsoft-windows-ie-devtools_31bf3856ad364e35_9.4.8112.16506_none_b05dee42126564ca	
(f)	CSI C Mark Deployment Missing	0x00000000	c!ffe1f622525..053c48116ba_31bf3856ad364e35_9.4.8112.16506_6fddd4733ed5ce12	x86_microsoft-windows-ie-ieshims_31bf3856ad364e35_9.4.8112.16506_none_602775e3b46a9840	
(f)	CSI C Mark Deployment Missing	0x00000000	c!ffe1f622525..053c48116ba_31bf3856ad364e35_9.4.8112.16506_6fddd4733ed5ce12	amd64_microsoft-windows-ie-ieshims_31bf3856ad364e35_9.4.8112.16506_none_bc4611676cc80976	
(f)	CSI Missing C Mark	0x00000000	c!62530574173..024f01c7b6d_31bf3856ad364e35_9.4.8112.16450_957362e7ecd0b397	amd64_62530574173d29e1dd547024f01c7b6d_31bf3856ad364e35_9.4.8112.16450_none_957362e7ecd0b397	Missing c!
(fix)	CSI Missing C Mark	CSI Registry Item Repaired	c!62530574173..024f01c7b6d_31bf3856ad364e35_9.4.8112.16450_957362e7ecd0b397 successfully added to amd64_62530574173d29e1dd547024f01c7b6d_31bf3856ad364e35_9.4.8112.16450_none_957362e7ecd0b397
(f)	CSI C Mark Deployment Missing	0x00000000	c!866e0ecb11a..13ccc3d122a_31bf3856ad364e35_9.4.8112.16506_733763c6655c1af4	amd64_microsoft-windows-ie-extcompat_31bf3856ad364e35_9.4.8112.16506_none_b1688d74a9290cbd	
(f)	CSI C Mark Deployment Missing	0x00000000	c!866e0ecb11a..13ccc3d122a_31bf3856ad364e35_9.4.8112.16506_733763c6655c1af4	x86_microsoft-windows-ie-extcompat_31bf3856ad364e35_9.4.8112.16506_none_5549f1f0f0cb9b87	
(f)	CSI C Mark Deployment Missing	0x00000000	c!b7715e8b5db..912fc4ec2ff_31bf3856ad364e35_9.4.8112.16506_5ab64eab369f0d49	x86_microsoft-windows-ie-devtools_31bf3856ad364e35_9.4.8112.16506_none_543f52be5a07f394	
(f)	CSI C Mark Deployment Missing	0x00000000	c!bd83c28417c..494540806be_31bf3856ad364e35_9.4.8112.16506_71037af12065aef9	amd64_microsoft-windows-ie-ieproxy_31bf3856ad364e35_9.4.8112.16506_none_04e7c5d11d1fa308	


Summary:
Seconds executed: 1286
 Found 14 errors
 Fixed 2 errors
  CSI Missing Component Key Total count: 1
  Fixed: CSI Missing Component Key.  Total count: 1
  CSI Missing C Mark Total count: 1
  Fixed: CSI Missing C Mark.  Total count: 1
  CSI C Mark Deployment Missing Total count: 10
  CBS Registry Error Total count: 2
(w)	Unable to get system disk properties	0x0000045D	IOCTL_STORAGE_QUERY_PROPERTY	Disk Cache	
Customer Experience report successfully uploaded.  Thank you for participating.  For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.
 
SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

View attachment SFCFix.zip

System Update Readiness Tool (SURT)

Run the System Update Readiness Tool.
This tool will take some time to complete - when it has finished, attach C:\Windows\Logs\CBS\CheckSUR.log with your reply.
 
SFCFix Output...

Code:
SFCFix version 2.4.5.0 by niemiro.Start time: 2015-10-08 16:11:08.564
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Using .zip script file at C:\Users\mtiadmintim\Desktop\SFCFix.zip [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.


Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\b7715e8b5db..912fc4ec2ff_31bf3856ad364e35_9.4.8112.16506_5ab64eab369f0d49.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ffe1f622525..053c48116ba_31bf3856ad364e35_9.4.8112.16506_6fddd4733ed5ce12.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ca681cb528c..b79427f0eb0_31bf3856ad364e35_9.4.8112.16506_48833e7d81cf975a.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\bd83c28417c..494540806be_31bf3856ad364e35_9.4.8112.16506_71037af12065aef9.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\866e0ecb11a..13ccc3d122a_31bf3856ad364e35_9.4.8112.16506_733763c6655c1af4.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\b7715e8b5db..912fc4ec2ff_31bf3856ad364e35_9.4.8112.16506_5ab64eab369f0d49.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ffe1f622525..053c48116ba_31bf3856ad364e35_9.4.8112.16506_6fddd4733ed5ce12.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ca681cb528c..b79427f0eb0_31bf3856ad364e35_9.4.8112.16506_48833e7d81cf975a.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\bd83c28417c..494540806be_31bf3856ad364e35_9.4.8112.16506_71037af12065aef9.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\866e0ecb11a..13ccc3d122a_31bf3856ad364e35_9.4.8112.16506_733763c6655c1af4.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
RegistryScript:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 18 datablocks.
Finish time: 2015-10-08 16:11:09.530
Script hash: YLk/nuWCx8if+NJ4TWqEIyTAowilfA8db3HMUvgDm8c=
----------------------EOF-----------------------




CheckSUR output... ALMOST-THERE - have I told you that you're amazing? Because you are.

Code:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-10-08 16:13


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist
(f)	CBS Registry Error	0x00000002	x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_0.0.0.0_pt	Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect	Failed to open store sub key


Checking Packages
(f)	CBS Registry Error	0x80070103	Package_168_for_KB2570791~31bf3856ad364e35~amd64~~6.1.1.1		failed to get owner for package.


Checking Component Store


Summary:
Seconds executed: 912
 Found 2 errors
  CBS Registry Error Total count: 2
(w)	Unable to get system disk properties	0x0000045D	IOCTL_STORAGE_QUERY_PROPERTY	Disk Cache	
Customer Experience report successfully uploaded.  Thank you for participating.  For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.
 
I appreciate the compliment, you're great to work with :)



If you run regedit and browse to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\ is there a key named x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_0.0.0.0_pt or some other variation of x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_0.0.0.0_pt-br_a8eb7e3c36a4bf75?

If so, try to open the key. Let me know if you get an error message and what the full name of the key is.
 
Yes, there is. But it errors as soon as I click on it.

x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_0.0.0.0_pt

Code:
x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_0.0.0.0_pt cannot be opened. An error is preventing this key from being opened. Details: The system cannot find the file specified.
 
Additionally there are two other keys with pt that work...

x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_0.0.0.0_pt-br_a8eb7e3c36a4bf75
x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_0.0.0.0_pt-pt_a9cd4da836142f51
 
OK. It would appear that there is a bit flipped in that key.

Are you familiar with the Windows Recovery Environment?
Is this a physical machine or a VM?
 
I'm not, I've not used Windows RE before.
It's a VM running on ESX 5.5. Additionally it's the only domain controller and Exchange server in this particular environment(trust me, I know, I'd have it differently if I could).
 
OK. That makes it a little easier, at least you can make snapshots.

I'll need a copy of the SOFTWARE hive from the server so I can find the problem and practice a fix.

Export SOFTWARE Hive

Please download RegBak (by AceLogix Software) from the link below and save it to your Desktop.


  • Right-click on regbak.zip then select Extract all... and extract the files to your Desktop

    For 32-bit (x86) editions of Windows, double-click on regbak.exe
    For 64-bit (x64) editions of Windows, double-click on regbak64.exe

    If you are unsure whether you have x86 or x64 Windows, see here

  • Without changing any options, click Next. RegBak will now backup all of your registry hives.
  • Navigate to C:\Windows\RegBak\{Date}\ and copy the SOFTWARE file (it has no extension) to your Desktop
  • Right click on the SOFTWARE file on your Desktop and choose Send To -> Compressed (zipped) Folder.
  • Upload this zip file for me to analyse:

    Microsoft Onedrive
    Dropbox
    SendSpace (or any other file-sharing site of your preference)​

When you have uploaded the zip, send me a private message here: Send zcomputerwiz a PM with a link to the uploaded file.

WARNING: Do NOT post the link on this public forum! Your software hive contains sensitive information such as product keys!

Once I have practiced the fix we can schedule a day and time when we can both be online.
What does your usual schedule look like? When we do the actual fixing I'll need a fresh copy of the software hive and then the server will need to remain shut down until you can replace the software hive with the repaired version.
 
Hmmm. Schedule, I'm available Mon-Fri 9am-4pm CST. But, if I need to shut the server down I'll have to work with the client to get a time, unless I can do it after 5pm. Not next Tuesday, but the following, they will be in maintenance from 6pm-11pm Central, so that would be ideal all around though I will schedule it whenever works for you that I can get some downtime for the client.
 
Hey, zcomputerwiz! Just wanted to touch base and see if I'd be good to do the remaining work on this tonight with the maintenance. If not, no worries, let me know when would be good for you. Thank you again for your continued help with all of this. I greatly appreciate it.
 
Yes, that should work.

Use these instructions to export the hive and send me a link when you are ready:

Export SOFTWARE Hive

Please download RegBak (by AceLogix Software) from the link below and save it to your Desktop.

  • Right-click on regbak.zip then select Extract all... and extract the files to your Desktop
    For 32-bit (x86) editions of Windows, double-click on regbak.exe
    For 64-bit (x64) editions of Windows, double-click on regbak64.exe

    If you are unsure whether you have x86 or x64 Windows, see here
  • Without changing any options, click Next. RegBak will now backup all of your registry hives.
  • Navigate to C:\Windows\RegBak\{Date}\ and copy the SOFTWARE file (it has no extension) to your Desktop
  • Right click on the SOFTWARE file on your Desktop and choose Send To -> Compressed (zipped) Folder.
  • Upload this zip file for me to analyse:
    Microsoft Onedrive
    Dropbox
    SendSpace (or any other file-sharing site of your preference)​

When you have uploaded the zip, send me a private message here: Send zcomputerwiz a PM with a link to the uploaded file.

I will do the edit and upload the file to a file sharing service, then reply to your PM with a link.

The instructions for performing the replacement are as follows:

SOFTWARE Hive Replacement with RegBak

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Close all open programs and save all your work. You will need to reboot the machine during this process.
  2. Download SOFTWARE.zip from the link I sent you to your desktop and extract the file SOFTWARE to your desktop (it has no file extension)
  3. Double click on regbak64.exe where you extracted it earlier to launch RegBak. Press Yes on the UAC prompt that will appear
  4. Click New Backup to open the new backup window. Leave the backup path as the default.
  5. Click Click here to view details and uncheck all options except for C:\Windows\System32\config\SOFTWARE. Press OK
  6. Click Start to create a backup.
  7. Once the backup is done, click Close to return to the main RegBak screen. You have now backed up the registry. Close RegBak
  8. Navigate to the folder you saved your backup (It should be C:\Windows\RegBak\PC-NAME\DATE)
  9. Inside the folder, double click Windows, System 32 and config to get to a folder with the SOFTWARE hive in:
    2014-10-1818_56_49-config_zpscbb8aad0.png
  10. Copy the SOFTWARE file from your desktop (not the zip file), to that folder. When asked if you want to replace the current SOFTWARE file, choose yes.
  11. Open RegBak again. Highlight the backup in the list (it should be the only one), and press Restore. Click Start. RegBak will reboot your computer to complete the restore process.

Let me know if you have any questions about the process at this point.
 
Just to clarify, if you need the updates to be completed first then don't do the replacement with the hive that I just sent you.
Allow the updates to go through at 6PM, then take a snapshot and send me a fresh copy of the software hive when the server is back up and running.
I can do the edit at that time then send it back to you so you can replace it.
 
I'll try and see if I can do the work before the patches download. I'm just stuck in a meeting for the next two to three hours. I'll let you know either way. Thank you so much!
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top