[SOLVED] Windows 7: Some Updates were not installed / Bad Image Error trying to run SFCFix.exe

[haganm]

Greetings.
Appreciate in advance any help you can provide.

I am trying to install the following Windows "Important" Updates:

Microsoft .NET Framework 3.5 Family Update (KB959209) x86
Microsoft .NET Framework 4.5.1 for Windows Vista (KB2858725)
Security Update for Microsoft .NET Framework 3.5 SP1 on Windows XP, Windows Server 2003, Windows Vista, ....

​

but am encountering one of two messages:

Sometimes I get: HOTIRON Hotfix Install stopped working and was closed
Other times I get: Windows Installer stopped working and was closed.

I did try to run SFC from the CMD line and received the following message:
Windows Resource Protection found corrupt files but was unable to fix some of them.

Note: When I try to attach the CBS log file to this post, I get a message saying the file is too large.


I also downloaded, per the forum instructions, SFCFix.exe but when I try to execute it, I get the following message:

SFCFix.exe - Bad Image
C:\Windows\system32\msi.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support.

Any help greatly appreciated! PS: I'm not a PC/Windows techie.....
Thanks!

 

[haganm]

Just realized I could compress the CBS.log so here it is. Again, thanks in advance for any and all help as I'm currently stuck....

 

[Go The Power]

Hello and welcome to the forum :)

This a bit of a catch 22, SFC has detected a corrupt file with msi.dll, but the reason why SFCFix can not repair it is that that file is corrupt. Now for this we are just going to focus on repairing the MSI file first that way we should be able to SFCFix for the other one's. This is the file we will try and repair first:

\SystemRoot\WinSxS\x86_microsoft-windows-installer-engine_31bf3856ad364e35_6.0.6002.19116_none_055c12b3b0add65d\msi.dll do not match actual file [l:14{7}]"msi.dll" :
{l:32 b:5rh/ogCrVxBWuWF5TY7ygMNXx0CvxzNRHv/z7sqeLHg=}

This will take a little be longer than normal as without SFCFix everything needs to be done manually.

1. Click on the
   
   button. Inside the search box type in CMD
2. Right click on CMD => Choose Run as Administrator
3. Inside the Command Prompt windows copy and paste the following commands (one by one)

mkdir %userprofile%\backup

icacls C:\Windows\WinSxS\x86_microsoft-windows-installer-engine_31bf3856ad364e35_6.0.6002.19116_none_055c12b3b0add65d\msi.dll /save %userprofile%\backup\ACLFile

takeown /f C:\Windows\WinSxS\x86_microsoft-windows-installer-engine_31bf3856ad364e35_6.0.6002.19116_none_055c12b3b0add65d\msi.dll

icacls C:\Windows\WinSxS\x86_microsoft-windows-installer-engine_31bf3856ad364e35_6.0.6002.19116_none_055c12b3b0add65d\msi.dll /grant administrators:F

copy C:\Windows\WinSxS\x86_microsoft-windows-installer-engine_31bf3856ad364e35_6.0.6002.19116_none_055c12b3b0add65d\msi.dll %userprofile%\backup\

Now that the files have been backed up and the permissions have been saved lets replace the file

Please download msi.dll from the link provided, and save it to your desktop, Please make sure it is directly to your desktop otherwise this command will fail.

copy %userprofile%\Desktop\msi.dll C:\Windows\WinSxS\x86_microsoft-windows-installer-engine_31bf3856ad364e35_6.0.6002.19116_none_055c12b3b0add65d\msi.dll

icacls C:\Windows\WinSxS\x86_microsoft-windows-installer-engine_31bf3856ad364e35_6.0.6002.19116_none_055c12b3b0add65d\ /restore %userprofile%\backup\ACLFile

If all goes to plan the file should be replaced successful. If you get no errors after doing this please continue, if you get an error please stop and provide me the error message.

SFC /SCANNOW

1. Click on the
   
   button. Inside the search box type in CMD
2. Right click on CMD => Choose Run as Administrator
3. Inside the Command Prompt windows copy and paste the following command SFC /SCANNOW
4. Please wait for this to Finish before continuing with the rest of the steps.

Convert CBS.log to CBS.txt

1. Click on the
   
   button => Inside the search box copy and paste the following command:
   

   cmd /c copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

2. Press Enter
3. Once this has completed please go to your Desktop and you will find CBS.txt => Please upload CBS.txt to this thread

Please Note:: if the file is too big to upload to you next post please upload via Dropbox or ge.tt

 

[haganm]

"Go The Power",
Thank you very much for your reply. I will the follow the steps you provided for me. I am leaving for work currently so will not be able to do this until this evening.

I will update as you ask.
Thanks again!!

 

[haganm]

"Go The Power",
I did all the steps you provided. I did not receive any errors until I ran the SFC /SCANNOW and I got the following:

Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.log windir\Logs\CBS\CBS.log.

I've attached the CBS.txt per your instructions.

Question: This is my father's PC. He recently clicked on a link in an email that he though was from me but wasn't. Could these problems be a result of him doing that?

Thanks again for all your time/assistance!

 

[Go The Power]

Hello again :)

SFC is not detecting MSI.DLL as being corrupt anymore which is good news :)

Can you please try and run SFCFix again?

Download and Run SFCFix

Please download and run SFCFix from >Here<


It will take about 15 minutes to process. Once the scan has completed a notepad file will launch with the results. Please copy and paste the entire contents of the results and post them back into this thread. Please put [CODE][/CODE] tags around the log to break up the text.

 

[Go The Power]

Question: This is my father's PC. He recently clicked on a link in an email that he though was from me but wasn't. Could these problems be a result of him doing that?

This could be the cause just depends on what type of file it was. Can you please do a scan for Malware with MalwareBytes and let me know what it reports :)

 

[haganm]

Greetings - and thanks again for your time and help. I very much appreciate it!

Find attached the contents of the notepad doc that open after running SFCFix (see below) - hopefully I did the Code \Code thing right..... I also attached results of running the "Threat Scan" in Malwarebytes.

SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-09-09 21:08:53.572
Not using a script file.
 

AutoAnalysis::
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-dsquery_31bf3856ad364e35_6.0.6001.18000_none_2dc52ffdfe4bfd41\dsquery.dll

SUMMARY: Some corruptions could not be fixed automatically and others were unimportant. Seek advice from helper or sysnative.com.
   CBS & SFC total detected corruption count:     3
   CBS & SFC total unimportant corruption count:  1
   CBS & SFC total fixed corruption count:        0
   SURT total detected corruption count:          0
   SURT total unimportant corruption count:       0
   SURT total fixed corruption count:             0
AutoAnalysis:: directive completed successfully.
 


Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-09-09 21:12:57.852
----------------------EOF-----------------------

 

[Go The Power]

Hello again :)

Malwarebytes looked like it just removed a few temp files, nothing of too concern.

Is the computer getting any strange pop-ups? or weird alerts?

Now that SFCFix is running well again, lets get that last corrupt file fixed up :)

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 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.

SFC /SCANNOW

1. Click on the
   
   button. Inside the search box type in CMD
2. Right click on CMD => Choose Run as Administrator
3. Inside the Command Prompt windows copy and paste the following command SFC /SCANNOW
4. Please wait for this to Finish before continuing with the rest of the steps.

Convert CBS.log to CBS.txt

1. Click on the
   
   button => Inside the search box copy and paste the following command:
   

   cmd /c copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

2. Press Enter
3. Once this has completed please go to your Desktop and you will find CBS.txt => Please upload CBS.txt to this thread

Please Note:: if the file is too big to upload to you next post please upload via Dropbox or ge.tt

How are updates going now?

Alex

 

[haganm]

Greetings.
I was able to download SFCFix.exe just fine and place it on the desktop. However, when I click on SFCFix.zip, I get the following message within my browser window:

Internet Explorer cannot display the webpage


Again, appreciate all help and your time!


[TABLE="width: 730"]
[TR]
[TD="width: *"][h=1][TABLE="width: 730"]
[TR]
[TD][/TD]
[/TR]
[/TABLE][/h][/TD]
[/TR]


[/TABLE]

 

[Go The Power]

Hello,

Sorry about the link, I think I forgot to upload the file :huh:

I will upload it when I get home from work (about 8 hours)

Alex

 

[haganm]

Alex,
Again - thank you so much for your help. Realize I say that each time I post but I honestly appreciate folks like yourself that take the time to help us non-gurus out.

Per your last request:

Here is the contents of the SFCFix results:

SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-09-11 18:44:55.004
Using .zip script file at C:\Users\jerry_ann\Desktop\SFCFix.zip [0]
 

PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_d278d2aaa749970e\tcpmon.ini
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-dsquery_31bf3856ad364e35_6.0.6001.18000_none_2dc52ffdfe4bfd41\dsquery.dll
Line blocked (SFCFix.txt): "C:\Users\jerry_ann\AppData\Local\niemiro\Archive\SFCFix.txt" C:\Windows\SFCFix.txt.
Successfully copied file C:\Users\jerry_ann\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_d278d2aaa749970e\tcpmon.ini to C:\Windows\winsxs\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_d278d2aaa749970e\tcpmon.ini.
Successfully copied file C:\Users\jerry_ann\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-dsquery_31bf3856ad364e35_6.0.6001.18000_none_2dc52ffdfe4bfd41\dsquery.dll to C:\Windows\winsxs\x86_microsoft-windows-dsquery_31bf3856ad364e35_6.0.6001.18000_none_2dc52ffdfe4bfd41\dsquery.dll.
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_d278d2aaa749970e\tcpmon.ini
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_d278d2aaa749970e\tcpmon.ini
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-dsquery_31bf3856ad364e35_6.0.6001.18000_none_2dc52ffdfe4bfd41\dsquery.dll
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-dsquery_31bf3856ad364e35_6.0.6001.18000_none_2dc52ffdfe4bfd41\dsquery.dll
PowerCopy:: directive completed successfully.
 

Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2014-09-11 18:44:56.517
Script hash: E6shpwwBF9LjWvU+QONqeamwdFdsJigQicMMMvyHM54=
----------------------EOF-----------------------

Also attached is the CBS log file (Compressed)

Finally, to answer some of the questions you asked:
1). Yes, Windows Updates are not (sorry - meant "now") installing fine
2). No weird pop-ups, etc
3). In addition to running Malwarebyte (shared those results already), I also ran the Malwarebytes Anti-Rootkit (Beta) with clean results.

Do have one additional question for you: What is the best way to check if a keylogger program has been installed on your system? Will the combination of the Malwarebyte programs check for that or do I need to run a differnt utility?

Thanks again!!

 

[Go The Power]

Hi haganm,

Again - thank you so much for your help. Realize I say that each time I post but I honestly appreciate folks like yourself that take the time to help us non-gurus out.

Your more than welcome :)

The CBS log is not not showing any more errors which is a good sign. As for the Windows update errors, lets see if we can get some information out of SURT.

Please read the guide Here for SURT instructions. Once the SURT has been installed please post the contents of.

• C:\Windows\Logs\CBS\CheckSUR.log
• C:\Windows\Logs\CBS\CheckSUR.persist.log

Do have one additional question for you: What is the best way to check if a keylogger program has been installed on your system? Will the combination of the Malwarebyte programs check for that or do I need to run a differnt utility?

Security analysis is not something I have looked at to in a very long time, thankfully we have a some Malware Removal experts here at Sysnative that would be able to ensure that your machine is clean. Please follow the instructions Here.

Thanks

Alex

 

[haganm]

Alex,
Actually it does appear now that the Windows updates are running properly. However, I decided to go ahead and run SURT just to be safe. SURT does appear to report 1 error. Here are the file contents you requested:

CheckSUR.log

=================================
Checking System Update Readiness.
Binary Version 6.0.6002.23186
Package Version 24.0
2014-09-13 13:27
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
(f) CSI Manifest Zero Length 0x00000000 winsxs\Manifests\x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406.manifest x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406
Summary:
Seconds executed: 3705
Found 1 errors
CSI Manifest Zero Length Total count: 1
Unavailable repair files:
winsxs\manifests\x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406.manifest

Checking CoreOS key for repairing corruptions.
Winner version: 6.0.6002.18971.
Processor architecture: x86.
Check key to be repaired: wcm://Microsoft-Windows-CoreOS?version=6.0.6002.18971&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers\metadata\elements\ComputerName
Recreated value: @_type.
Recreated value: @dataOnly.
Recreated value: @default.
Recreated value: @description.
Recreated value: @displayName.
Recreated value: @handler.
Recreated value: @legacyName.
Recreated value: @legacyType.
Recreated value: @migrate.
Recreated value: @scope.
Recreated value: @xsd:type.


CheckSUR.persist.log

=================================
Checking System Update Readiness.
Binary Version 6.0.6002.23186
Package Version 24.0
2014-09-13 09:45
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
(f) CSI Manifest Zero Length 0x00000000 winsxs\Manifests\x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406.manifest x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406
Summary:
Seconds executed: 12360
Found 1 errors
CSI Manifest Zero Length Total count: 1
Unavailable repair files:
winsxs\manifests\x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406.manifest

Checking CoreOS key for repairing corruptions.
Winner version: 6.0.6002.18971.
Processor architecture: x86.
Check key to be repaired: wcm://Microsoft-Windows-CoreOS?version=6.0.6002.18971&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers\metadata\elements\ComputerName
Recreated value: @_type.
Recreated value: @dataOnly.
Recreated value: @default.
Recreated value: @description.
Recreated value: @displayName.
Recreated value: @handler.
Recreated value: @legacyName.
Recreated value: @legacyType.
Recreated value: @migrate.
Recreated value: @scope.
Recreated value: @xsd:type.

=================================
Checking System Update Readiness.
Binary Version 6.0.6002.23186
Package Version 24.0
2014-09-13 13:27
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
(f) CSI Manifest Zero Length 0x00000000 winsxs\Manifests\x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406.manifest x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406
Summary:
Seconds executed: 3705
Found 1 errors
CSI Manifest Zero Length Total count: 1
Unavailable repair files:
winsxs\manifests\x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406.manifest

Checking CoreOS key for repairing corruptions.
Winner version: 6.0.6002.18971.
Processor architecture: x86.
Check key to be repaired: wcm://Microsoft-Windows-CoreOS?version=6.0.6002.18971&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers\metadata\elements\ComputerName
Recreated value: @_type.
Recreated value: @dataOnly.
Recreated value: @default.
Recreated value: @description.
Recreated value: @displayName.
Recreated value: @handler.
Recreated value: @legacyName.
Recreated value: @legacyType.
Recreated value: @migrate.
Recreated value: @scope.
Recreated value: @xsd:type.


Thanks again!!!

 

[Go The Power]

That's good news that the updates are working :)

Lets get the one file fixed up so it doesn't cause any hassles later down the track.

• Right-click on the file and select Extract All...
• Tick the box labelled Show extracted files when complete then click Extract
• A window will open showing two folders, Manifests and Packages
• Open the Manifests folder and copy the files into the following folder (if there are any files)
  
  C:\Windows\Temp\CheckSur\Winsxs\Manifests
  
• Open the Packages folder and copy the files into the following folder (if there are any files)
  
  C:\Windows\Temp\CheckSur\Servicing\Packages
  
• Run the System Update Readiness Tool (SURT) again.
• When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:
  
  C:\Windows\Logs\CBS\CheckSUR.log
  C:\Windows\Logs\CBS\CheckSUR.persist.log

 

[haganm]

Question: How do I run the SURT tool after I have already downloaded it? Sorry for the dumb question but it's not clear to me how I run it a second time.

THanks!!

 

[Go The Power]

Go to where you downloaded and saved SURT the first time, then double click on the installer again to re run :)

 

[haganm]

Alex,
Ok, copied the files over, per your instructions, and re-ran SURT. The contents of the requested files are below. To my "untrained" eye, I think it looks good - hopefully you agree :->

C:\Windows\Logs\CBS\CheckSUR.log

=================================
Checking System Update Readiness.
Binary Version 6.0.6002.23186
Package Version 24.0
2014-09-14 10:37

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Manifest Zero Length 0x00000000 winsxs\Manifests\x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406.manifest x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406
(fix) CSI Manifest Zero Length CSI File Replaced File: x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406.manifest From: C:\Windows\CheckSur\v1.0\windows6.0-6000-client-wave0.cab

Summary:
Seconds executed: 4360
Found 1 errors
Fixed 1 errors
CSI Manifest Zero Length Total count: 1
Fixed: CSI Manifest Zero Length. Total count: 1

Checking CoreOS key for repairing corruptions.
Winner version: 6.0.6002.18971.
Processor architecture: x86.
Check key to be repaired: wcm://Microsoft-Windows-CoreOS?version=6.0.6002.18971&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers\metadata\elements\ComputerName
Recreated value: @_type.
Recreated value: @dataOnly.
Recreated value: @default.
Recreated value: @description.
Recreated value: @displayName.
Recreated value: @handler.
Recreated value: @legacyName.
Recreated value: @legacyType.
Recreated value: @migrate.
Recreated value: @scope.
Recreated value: @xsd:type.


C:\Windows\Logs\CBS\CheckSUR.persist.log

=================================
Checking System Update Readiness.
Binary Version 6.0.6002.23186
Package Version 24.0
2014-09-13 09:45

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Manifest Zero Length 0x00000000 winsxs\Manifests\x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406.manifest x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406

Summary:
Seconds executed: 12360
Found 1 errors
CSI Manifest Zero Length Total count: 1

Unavailable repair files:
winsxs\manifests\x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406.manifest


Checking CoreOS key for repairing corruptions.
Winner version: 6.0.6002.18971.
Processor architecture: x86.
Check key to be repaired: wcm://Microsoft-Windows-CoreOS?version=6.0.6002.18971&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers\metadata\elements\ComputerName
Recreated value: @_type.
Recreated value: @dataOnly.
Recreated value: @default.
Recreated value: @description.
Recreated value: @displayName.
Recreated value: @handler.
Recreated value: @legacyName.
Recreated value: @legacyType.
Recreated value: @migrate.
Recreated value: @scope.
Recreated value: @xsd:type.


=================================
Checking System Update Readiness.
Binary Version 6.0.6002.23186
Package Version 24.0
2014-09-13 13:27

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Manifest Zero Length 0x00000000 winsxs\Manifests\x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406.manifest x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406

Summary:
Seconds executed: 3705
Found 1 errors
CSI Manifest Zero Length Total count: 1

Unavailable repair files:
winsxs\manifests\x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406.manifest


Checking CoreOS key for repairing corruptions.
Winner version: 6.0.6002.18971.
Processor architecture: x86.
Check key to be repaired: wcm://Microsoft-Windows-CoreOS?version=6.0.6002.18971&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers\metadata\elements\ComputerName
Recreated value: @_type.
Recreated value: @dataOnly.
Recreated value: @default.
Recreated value: @description.
Recreated value: @displayName.
Recreated value: @handler.
Recreated value: @legacyName.
Recreated value: @legacyType.
Recreated value: @migrate.
Recreated value: @scope.
Recreated value: @xsd:type.


=================================
Checking System Update Readiness.
Binary Version 6.0.6002.23186
Package Version 24.0
2014-09-14 10:37

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Manifest Zero Length 0x00000000 winsxs\Manifests\x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406.manifest x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406
(fix) CSI Manifest Zero Length CSI File Replaced File: x86_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20674_none_24ec37830546c406.manifest From: C:\Windows\CheckSur\v1.0\windows6.0-6000-client-wave0.cab

Summary:
Seconds executed: 4360
Found 1 errors
Fixed 1 errors
CSI Manifest Zero Length Total count: 1
Fixed: CSI Manifest Zero Length. Total count: 1

Checking CoreOS key for repairing corruptions.
Winner version: 6.0.6002.18971.
Processor architecture: x86.
Check key to be repaired: wcm://Microsoft-Windows-CoreOS?version=6.0.6002.18971&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers\metadata\elements\ComputerName
Recreated value: @_type.
Recreated value: @dataOnly.
Recreated value: @default.
Recreated value: @description.
Recreated value: @displayName.
Recreated value: @handler.
Recreated value: @legacyName.
Recreated value: @legacyType.
Recreated value: @migrate.
Recreated value: @scope.
Recreated value: @xsd:type.

 

[Go The Power]

Looks good, good work :)

Found 1 errors
Fixed 1 errors

Any issues with updates?

 

[haganm]

Alex - everything appears to be functioning properly. Think we can consider this one fixed and closed out!

I know I said this frequently but I don't feel I can actually say it enough: Thank you so much for your time, patience, and expertise in getting my issue resolved. I really appreciate your willingness to help so many out, including me. I will absolutely recommend Sysnative to others. A donation to your site will be my next step.

Note: Anyone who reads this, please consider donating once your problem/issue is resolved. I can only imagine how expensive if I would have taken my system to a typical box store to fix (and I'm not certain they would have really fixed it as well). Well, well worth a donation to keep sites like this up and running!