Windows Update Error Code 800B0100 - Urgent Please
- Thread starter shankdil
- Start date
Hello shankdil, welcome to Sysnative!
The files that need replacing are associated with Windows Activation, so I'd just like to check there aren't any problems there first:
MGADiag
Tom
The files that need replacing are associated with Windows Activation, so I'd just like to check there aren't any problems there first:
MGADiag
- Download MGADiag (by Microsoft) from the link below:
http://go.microsoft.com/fwlink/?linkid=52012
- Run the tool by double clicking on the file. Press Continue when prompted
- When it has finished, press Copy then Paste (Ctrl+V) this into your next post
Tom
Thanks Tom for the response. Will provide you the data tomorrow ... Much appreciated.
Here is the requested data...
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-MV8MH-98QJM-24367
Windows Product Key Hash: wgci5Gdejx4esg7++zTOe3LWF+4=
Windows Product ID: 55041-OEM-8992671-00437
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7600.2.00010100.0.0.048
ID: {4B0A67D4-2236-407D-B4DB-B40FB432FB8C}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Professional
Architecture: 0x00000000
Build lab: 7600.win7_gdr.130318-1532
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: 109 N/A
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
Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files\Internet Explorer\IEXPLORE.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[Hr = 0x800b0003]
File Mismatch: C:\Windows\system32\wat\npwatweb.dll[Hr = 0x800b0003]
File Mismatch: C:\Windows\system32\wat\watux.exe[Hr = 0x800b0003]
File Mismatch: C:\Windows\system32\wat\watweb.dll[Hr = 0x800b0003]
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{4B0A67D4-2236-407D-B4DB-B40FB432FB8C}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.048</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-24367</PKey><PID>55041-OEM-8992671-00437</PID><PIDType>2</PIDType><SID>S-1-5-21-4207277384-2445451547-1361014572</SID><SYSTEM><Manufacturer>LENOVO</Manufacturer><Model>0163D5A</Model></SYSTEM><BIOS><Manufacturer>LENOVO</Manufacturer><Version>9GKT28AUS</Version><SMBIOSVersion major="2" minor="6"/><Date>20101217000000.000000+000</Date></BIOS><HWID>B2B93607018400FC</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Malay Peninsula Standard Time(GMT+08:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>LENOVO</OEMID><OEMTableID>TC-9G </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>
Spsys.log Content: 0x80070002
Licensing Data-->
Software licensing service version: 6.1.7600.16385
Name: Windows(R) 7, Professional edition
Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
Activation ID: 50e329f7-a5fa-46b2-85fd-f224e5da7764
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00371-00178-926-700437-02-1033-7600.0000-2022009
Installation ID: 009531758763442941074570880981115530378362419760203432
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: 24367
License Status: Licensed
Remaining Windows rearm count: 2
Trusted time: 12/31/2013 11:34:39 AM
Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Not Registered - 0x800700c1
Admin Service: Not Registered - 0x80070005
HealthStatus Bitmask Output:
HWID Data-->
HWID Hash Current: LAAAAAEAAgABAAEAAAABAAAAAQABAAEAJJQUcU5hUn7mdmqaFlboTCJmXF0=
OEM Activation 1.0 Data-->
N/A
OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x20001
OEMID and OEMTableID Consistent: yes
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC LENOVO TC-9G
FACP LENOVO TC-9G
HPET LENOVO TC-9G
MCFG LENOVO TC-9G
SSDT LENOVO TC-9G
SLIC LENOVO TC-9G
Code:
File Scan Data-->
File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[Hr = 0x800b0003]
File Mismatch: C:\Windows\system32\wat\npwatweb.dll[Hr = 0x800b0003]
File Mismatch: C:\Windows\system32\wat\watux.exe[Hr = 0x800b0003]
File Mismatch: C:\Windows\system32\wat\watweb.dll[Hr = 0x800b0003]Very unusual errors in the log, there!
They almost certainly are the result of an Activation Exploit attempting to remove the WAT Update or prevent it doing its job.
Code:
ActiveX: Not Registered - 0x800700c1
Admin Service: Not Registered - 0x80070005
HealthStatus Bitmask Output:Having said that, the default shipping OS for this system (Lenovo 0163D5A) appears to be Windows 7 Pro, so there is no need for a hack.
Let's see what attempting to uninstall the update does...
Open an Elevated Command Prompt window, and type the following command
wusa /uninstall /kb:971033
and hit the Enter key
Accept the warnings/confirmations, and wait for it to complete
copy and paste the output (if any) from the command prompt window to a reply here,
Reboot
reinstall the update from Description of the update for Windows Activation Technologies
Reboot
run another MGADiag report, and post it.
Here are some instructions to make life easier :)
1) To open an Elevated Command Prompt Window (the ECP window), click on Start, All Programs, Accessories – then right-click on Command Prompt, and select Run as Administrator. Accept the UAC prompt.
2) To run the commands easier, highlight the block of commands, and right-click on the highlight – select Copy. In the CP Window, click on the black/white icon at top left – select Paste. The commands will run but may not complete the last command, so hit the Enter Key once.
3) To copy the results... click on the Black/White icon in the top left, and select Edit... 'Select All', and hit the Enter key - then use Ctrl+V or r-click+Paste to paste it into your response.
NoelDP said:
They actually look like they could be caused by the SURT corruptions in the first post.
What do you think about me repairing the SURT corruptions and seeing what that does? Could that backfire? We may well have to do it anyway to get it to uninstall, but we probably try that simple way first regardless.
Interesting :)
Richard
It was a toss-up for me which to try first. :)
If the uninstall/reinstall doesn't work, then the cat/mum replacement is the obvious way to go - but the resulting installation may still not work. It'll be interesting to see both, as I've never seen this specific error-pattern before.
If the uninstall/reinstall doesn't work, then the cat/mum replacement is the obvious way to go - but the resulting installation may still not work. It'll be interesting to see both, as I've never seen this specific error-pattern before.
Yeah, it will definitely be interesting, as I haven't seen anything like this either (not that I do much MGADiag stuff, but I don't think I've ever seen corrupt WAT cat/mum files either...)
Anyway, we'll have to wait and see :)
Richard
While uninstalling using the command wusa /uninstall /kb:971033 in command prompt, i got an error (screenshot attached).
Attachments
That basically confirms what I suspected, and means that we have to go to Plan B and replace the missing CAT and MUM files using ChekcSUR....
I'll post the protocol in a few minutes.
I'll post the protocol in a few minutes.
I've uploaded a file - sdlaa.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder sdlaa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)
Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages
And the content of the manifests folder (.manifest files) into this folder:
C:\Windows\Temp\CheckSur\Winsxs\Manifests
Now run the CheckSUR tool again (it may take a while)
Post the new CheckSUR.log file, and the CheckSUR.persist.log file.
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder sdlaa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)
Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages
And the content of the manifests folder (.manifest files) into this folder:
C:\Windows\Temp\CheckSur\Winsxs\Manifests
Now run the CheckSUR tool again (it may take a while)
Post the new CheckSUR.log file, and the CheckSUR.persist.log file.
... forgot to add -
Reboot
Please also run a new MGADiag report and post the new results, and test Windows Update and see whether that now works
Reboot
Please also run a new MGADiag report and post the new results, and test Windows Update and see whether that now works
It worked fine... Great Thanks a lot guys for your support.... Really looking forward for your awesome support
Please post the CheckSUR log, and the new MGADiag report so we can confirm that everything is OK now.
Has Sysnative Forums helped you? Please consider donating to help us support the site!