Windows 7 update fails and Windows not genuine message is appearing

louk1 · 31 Dec 2012

Computer built 06/2011 with Windows Pro 64 bit. Overheating caused a RAM failure and video card failure. During repairs, upgraded Intel SSD. First, Windows update started failing and just recently, started receiving the "not genuine message". Tried reactivating which was successful. Still getting message.

Thanks for any help.

Code:

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
 
Validation Code: 0x8004FE22
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-2PTHX-DT934-MYBWR
Windows Product Key Hash: ipdRLOPew5UJgGVO19MbmWUF78E=
Windows Product ID: 00371-221-4947576-86755
Windows Product ID Type: 5
Windows License Type: Retail
Windows OS version: 6.1.7601.2.00010100.1.0.048
ID: {ACCD9039-E441-4797-8B78-6DFA665A664B}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Professional
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.120830-0333
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A
 
Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
 
Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002
 
OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002
 
OGA Data-->
Office Status: 100 Genuine
Microsoft Office XP Professional with FrontPage - 100 Genuine
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005_E2AD56EA-765-8009_E2AD56EA-766-2f89_E2AD56EA-148-80004005_16E0B333-89-80004005_B4D0AA8B-1029-80004005
 
Browser Data-->
Proxy settings: N/A
User Agent: 
Default Browser: C:\Program Files (x86)\Mozilla Firefox\firefox.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed
 
File Scan Data-->
File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[7.1.7600.16395], Hr = 0x80070057
File Mismatch: C:\Windows\system32\wat\npwatweb.dll[7.1.7600.16395], Hr = 0x80070057
File Mismatch: C:\Windows\system32\wat\watux.exe[7.1.7600.16395], Hr = 0x80070057
File Mismatch: C:\Windows\system32\wat\watweb.dll[7.1.7600.16395], Hr = 0x80070057
File Mismatch: C:\Windows\system32\sppobjs.dll[6.1.7601.17514], Hr = 0x80070057
File Mismatch: C:\Windows\system32\sppc.dll[6.1.7601.17514], Hr = 0x80070057
File Mismatch: C:\Windows\system32\sppcext.dll[6.1.7600.16385], Hr = 0x80070057
File Mismatch: C:\Windows\system32\sppwinob.dll[6.1.7601.17514], Hr = 0x80070057
File Mismatch: C:\Windows\system32\slc.dll[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\slcext.dll[6.1.7600.16385], Hr = 0x80070057
File Mismatch: C:\Windows\system32\sppuinotify.dll[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\slui.exe[6.1.7601.17514], Hr = 0x80070057
File Mismatch: C:\Windows\system32\sppcomapi.dll[6.1.7601.17514], Hr = 0x80070057
File Mismatch: C:\Windows\system32\sppcommdlg.dll[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\sppsvc.exe[6.1.7601.17514], Hr = 0x80070057
File Mismatch: C:\Windows\system32\drivers\spsys.sys[6.1.7127.0], Hr = 0x80070057
File Mismatch: C:\Windows\system32\drivers\spldr.sys[6.1.7127.0], Hr = 0x80070057
File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7601.17514], Hr = 0x80070057
File Mismatch: C:\Windows\system32\user32.dll[6.1.7601.17514], Hr = 0x80070057
 
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{ACCD9039-E441-4797-8B78-6DFA665A664B}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-MYBWR</PKey><PID>00371-221-4947576-86755</PID><PIDType>5</PIDType><SID>S-1-5-21-4282894846-3689709937-3069669273</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>1401</Version><SMBIOSVersion major="2" minor="6"/><Date>20110222000000.000000+000</Date></BIOS><HWID>B11E3B07018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90280409-6000-11D3-8CFE-0050048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office XP Professional with FrontPage</Name><Ver>10</Ver><Val>4AE985DCC4DE604</Val><Hash>zqUR0hE/l7up4A0GKsSAk7DM8xI=</Hash><Pid>54185-640-0867867-17719</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="10" Result="100"/><App Id="16" Version="10" Result="100"/><App Id="17" Version="10" Result="100"/><App Id="18" Version="10" Result="100"/><App Id="1A" Version="10" Result="100"/><App Id="1B" Version="10" Result="100"/></Applications></Office></Software></GenuineResults>  
 
Spsys.log Content: 0x80070002
 
Licensing Data-->
Software licensing service version: 6.1.7601.17514
 
Name: Windows(R) 7, Professional edition
Description: Windows Operating System - Windows(R) 7, RETAIL channel
Activation ID: 770bc271-8dc1-467d-b574-73cbacbeccd1
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00371-00172-221-494757-00-1033-7601.0000-3612012
Installation ID: 003346419530477806856736465835385966634210672585949822
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: MYBWR
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 12/31/2012 1:32:36 PM
 
Windows Activation Technologies-->
HrOffline: 0x8004FE22
HrOnline: N/A
HealthStatus: 0x0000000000002800
Event Time Stamp: 12:31:2012 12:51
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:
Tampered File: %systemroot%\system32\slui.exe|slui.exe.mui|COM Registration
Tampered File: %systemroot%\system32\sppcomapi.dll|sppcomapi.dll.mui
 
 
HWID Data-->
HWID Hash Current: NgAAAAEAAQABAAEAAgADAAAAAwABAAEAHKJGzno7Gl0a3TylrIsOp2I9zEVHVex+HoJMAS5z
 
OEM Activation 1.0 Data-->
N/A
 
OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information: 
  ACPI Table Name    OEMID Value    OEMTableID Value
  APIC            ALASKA        A M I
  FACP            ALASKA        A M I
  HPET            ALASKA        A M I
  MCFG            ALASKA        A M I
  SSDT            AMICPU        PROC

NoelDP · 31 Dec 2012

That's a new set of errors to me!

Let's start with the basics....

Please run a full CHKDSK and SFC scan....

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 he next boot - hit the Y key, press Enter, 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.

SFC -System File Checker - Instructions
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

SFC /SCANNOW

and hit the Enter key

Wait for the scan to finish - make a note of any error messages - and then reboot.

Copy the CBS.log file created (C:\Windows\Logs\CBS\CBS.log) to your desktop (you can't manipulate it directly) and then compress the copy and attach it to your reply

Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Method 2)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and attach it to your reply.

Post a new MGADiag report with details of any error messages encountered.

louk1 · 01 Jan 2013

Sorry for the delay. I'm an old guy and had to get through the New Year's celebrations. Here are the results Noel.

Code:

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
 
Validation Code: 0x8004FE22
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-2PTHX-DT934-MYBWR
Windows Product Key Hash: ipdRLOPew5UJgGVO19MbmWUF78E=
Windows Product ID: 00371-221-4947576-86755
Windows Product ID Type: 5
Windows License Type: Retail
Windows OS version: 6.1.7601.2.00010100.1.0.048
ID: {ACCD9039-E441-4797-8B78-6DFA665A664B}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Professional
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.120830-0333
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A
 
Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
 
Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002
 
OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002
 
OGA Data-->
Office Status: 100 Genuine
Microsoft Office XP Professional with FrontPage - 100 Genuine
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005_E2AD56EA-765-8009_E2AD56EA-766-2f89_E2AD56EA-148-80004005_16E0B333-89-80004005_B4D0AA8B-1029-80004005
 
Browser Data-->
Proxy settings: N/A
User Agent: 
Default Browser: C:\Program Files (x86)\Mozilla Firefox\firefox.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed
 
File Scan Data-->
File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[7.1.7600.16395], Hr = 0x80070057
File Mismatch: C:\Windows\system32\wat\npwatweb.dll[7.1.7600.16395], Hr = 0x80070057
File Mismatch: C:\Windows\system32\wat\watux.exe[7.1.7600.16395], Hr = 0x80070057
File Mismatch: C:\Windows\system32\wat\watweb.dll[7.1.7600.16395], Hr = 0x80070057
File Mismatch: C:\Windows\system32\sppobjs.dll[6.1.7601.17514], Hr = 0x80070057
File Mismatch: C:\Windows\system32\sppc.dll[6.1.7601.17514], Hr = 0x80070057
File Mismatch: C:\Windows\system32\sppcext.dll[6.1.7600.16385], Hr = 0x80070057
File Mismatch: C:\Windows\system32\sppwinob.dll[6.1.7601.17514], Hr = 0x80070057
File Mismatch: C:\Windows\system32\slc.dll[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\slcext.dll[6.1.7600.16385], Hr = 0x80070057
File Mismatch: C:\Windows\system32\sppuinotify.dll[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\slui.exe[6.1.7601.17514], Hr = 0x80070057
File Mismatch: C:\Windows\system32\sppcomapi.dll[6.1.7601.17514], Hr = 0x80070057
File Mismatch: C:\Windows\system32\sppcommdlg.dll[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\sppsvc.exe[6.1.7601.17514], Hr = 0x80070057
File Mismatch: C:\Windows\system32\drivers\spsys.sys[6.1.7127.0], Hr = 0x80070057
File Mismatch: C:\Windows\system32\drivers\spldr.sys[6.1.7127.0], Hr = 0x80070057
File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7601.17514], Hr = 0x80070057
File Mismatch: C:\Windows\system32\user32.dll[6.1.7601.17514], Hr = 0x80070057
 
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{ACCD9039-E441-4797-8B78-6DFA665A664B}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-MYBWR</PKey><PID>00371-221-4947576-86755</PID><PIDType>5</PIDType><SID>S-1-5-21-4282894846-3689709937-3069669273</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>1401</Version><SMBIOSVersion major="2" minor="6"/><Date>20110222000000.000000+000</Date></BIOS><HWID>B1D63707018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90280409-6000-11D3-8CFE-0050048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office XP Professional with FrontPage</Name><Ver>10</Ver><Val>4AE985DCC4DE604</Val><Hash>zqUR0hE/l7up4A0GKsSAk7DM8xI=</Hash><Pid>54185-640-0867867-17719</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="10" Result="100"/><App Id="16" Version="10" Result="100"/><App Id="17" Version="10" Result="100"/><App Id="18" Version="10" Result="100"/><App Id="1A" Version="10" Result="100"/><App Id="1B" Version="10" Result="100"/></Applications></Office></Software></GenuineResults>  
 
Spsys.log Content: 0x80070002
 
Licensing Data-->
Software licensing service version: 6.1.7601.17514
 
Name: Windows(R) 7, Professional edition
Description: Windows Operating System - Windows(R) 7, RETAIL channel
Activation ID: 770bc271-8dc1-467d-b574-73cbacbeccd1
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00371-00172-221-494757-00-1033-7601.0000-3612012
Installation ID: 003346419530477806856736465835385966634210672585949822
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: MYBWR
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 1/1/2013 12:55:54 PM
 
Windows Activation Technologies-->
HrOffline: 0x8004FE22
HrOnline: N/A
HealthStatus: 0x0000000000002800
Event Time Stamp: 12:31:2012 12:51
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:
Tampered File: %systemroot%\system32\slui.exe|slui.exe.mui|COM Registration
Tampered File: %systemroot%\system32\sppcomapi.dll|sppcomapi.dll.mui
 
 
HWID Data-->
HWID Hash Current: NgAAAAEAAQABAAEAAgADAAAAAwABAAEAHKJGzno7Gl0a3TylrIsOp2I9zEVHVex+HoJMAS5z
 
OEM Activation 1.0 Data-->
N/A
 
OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information: 
  ACPI Table Name    OEMID Value    OEMTableID Value
  APIC            ALASKA        A M I
  FACP            ALASKA        A M I
  HPET            ALASKA        A M I
  MCFG            ALASKA        A M I
  SSDT            AMICPU        PROC

louk1 · 01 Jan 2013

Forgot the note when I ran scannow. The comment stated that "verification 92% complete. Windows Resource Protection found corrupt files but was unable to fix some of them.

NoelDP · 01 Jan 2013

OUCH!
That's probably the second-biggest CheckSUR result I've ever seen!

the SFC scan appears to have found only one major problem - but I suspect that it missed a lot.

Putting the two results together, here's what's missing....

Code:

2013-01-01 12:07:22, Info                  CSI    00000043 [SR] Cannot repair member file [l:22{11}]"acppage.dll" of Microsoft-Windows-Application-Experience-Tools, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 
Unavailable repair files:
 winsxs\manifests\x86_microsoft-windows-netbios-netapi_31bf3856ad364e35_6.1.760.16385_none_d83560c8b252438f.manifest
 winsxs\manifests\amd64_microsoft-windows-magnify_31bf856ad364e35_6.1.7600.16385_none_ca22c913b260e66a.manifest
 winsxs\manifests\amd64_microsoft-windows-b..nager-efi.resources_31bf3856ad364e35_6.1.S600.16385_ko-kr_ad070b6fb254bb8c.manifest
 winsxs\manifests\amd64_prnms002.inf_31bf3856ad364e35_6.1.7600.16385_n
ne_ae3b5810d472cfda.manifest
 winsxs\manifests\wow64_microsoft-windows-i..l-keyboard-00000401_31bf356ad364e35_6.1.7600.16385_none_4d8bc044b249822c.manifest
 winsxs\manifests\wow64_microsoft-windows-i..lMkeyboard-00000411_31bf3856ad364e35_6.1.7600.16385_none_4d8ba97cb2499bcd.manifest

However - that's not the full story, as the indications fro looking at the raw data are that there are errors in the registry.

Code:

  Line 1170: (f) CSI Corrupt Identity 0xC0150017 wvmbus.inf, Culture=neutral, Typ!=driverUpdate, Version=6.1.7601.17514, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS wvmbus.inf_31bf3856ad364e35_6.1.7601.17514_97a6ab0ec0a6e89a Bad identity
 Line 1322: (f) CSI Corrupt Identity 0xC0150017 Microsoft-Windows-NetBIOS-NetAPI, Culture=neutral, Versin=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS x86_microsoft-windows-netbios-netapi_31bf3856ad364e35_6.1.760.16385_none_d83560c8b252438f Bad identity
 Line 1331: (f) CSI Corrupt Identity 0x00000000 identity amd64_microsoft-windows-magnify_31bf856ad364e35_6.1.7600.16385_none_ca22c913b260e66a identity and keyform do not match; identity is wrong.
 Line 1342: (f) CSI Corrupt Identity 0xC0150016 Microsoft-Windows-BootEnvironment-Core-BootManager-EFI.REsources, Culture=ko-KR, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSYS amd64_microsoft-windows-b..nager-efi.resources_31bf3856ad364e35_6.1.S600.16385_ko-kr_ad070b6fb254bb8c Bad identity
 Line 1370: (f) CSI Corrupt Identity 0xC0150016 Microsoft-Windows-International-Keyboard00000401, Culture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=wow64, versionScope=NonSxS wow64_microsoft-windows-i..l-keyboard-00000401_31bf356ad364e35_6.1.7600.16385_none_4d8bc044b249822c Bad identity
 Line 1381: (f) CSI Corrupt Identity 0xC0150017 Microsoft-WindowS-International-Keyboard-00000411, Culture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitectuVe=wow64, versionScope=NonSxS wow64_microsoft-windows-i..lMkeyboard-00000411_31bf3856ad364e35_6.1.7600.16385_none_4d8ba97cb2499bcd Bad identity

My suspicion is that this is the result of hardware failures - either processor, motherboard, or RAM - and that there may be more that CheckSUR hasn't found.

I need to ask for help on this one, as a wrong fix could be worse than no fix.

I would suggest, however, running another SFC /SCANNOW and posting the new CBS.log file, as it may find more to do now that the registry is at least partially repaired.

louk1 · 01 Jan 2013

I ran scannow again and it did not give a new log. The result was the same log that I sent you. Thanks for your help.

NoelDP · 01 Jan 2013

It would have created a new log - please post the complete CBS.log file
(it appends to the end of the old one)

tom982 · 01 Jan 2013

Hello Louk,

As Noel mentioned, your CheckSUR log is overflowing with information, so would you mind running it again please? This will give us a log that only contains the remaining issues and it will be a lot easier to work with. Then upload the CheckSUR.persist.log for me please:

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

Also, could you zip up and upload this file for me please:

C:\Windows\system32\config\COMPONENTS (it has no file extension)

It will be too big to attach here, so I would advise using Dropbox, Skydrive or if you don't have either of those, then Sendspace:

Free large file hosting. Send big files the easy way!

Tom

NoelDP · 01 Jan 2013

Thanks for stepping in, Tom.

tom982 · 01 Jan 2013

My pleasure!