Solved Service Pack 1 Install Failed Error 8024200D

[Layback Bear]

I surly don't understand after a Repair Install you should need to do a .Network 4.5 repair unless the media you used is corrupt. The last version is 4.5.2.

Have you completed all the needed Windows 7 Updates??

I think it would be a good idea still to complete this Tutorial.


Windows Genuine and Activation Issue Posting Instructions

 

[Zebo12345]

I am still doing the updates. The first wave of updates had everything work fine, except now starting the second wave of updates, and SP1 is still there, so it must have failed. I noticed when I got the disk for the repair, it looked scratched. No huge scratches or anything, and it wasn't SUPER damaged, but if it is damaged enough, that probably has caused my issue. In that case, what should I do? I am going to try out the tutorial you sent me now, Layback Bear. (I have a windows pro CD which I could backup my important files and do a clean install with, so that's my next backup plan.)

 

[Zebo12345]

I assume you would like me to post the results of this tutorial here, rather than make a whole new post, so here it is for you.

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-FP4WW-RCKMD-K6KK8
Windows Product Key Hash: ie6mY1VJGAo5EQTj3PP8XdzSSGQ=
Windows Product ID: 00432-077-1545051-86146
Windows Product ID Type: 5
Windows License Type: Retail
Windows OS version: 6.1.7600.2.00010100.0.0.028
ID: {FB6ED73C-D10C-4488-B54D-7482E7905352}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Ultimate N
Architecture: 0x00000009
Build lab: 7600.win7_gdr.110408-1633
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 (x86)\Google\Chrome\Application\chrome.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 = 0x80092003
File Mismatch: C:\Windows\system32\wat\watux.exe[7.1.7600.16395], Hr = 0x80092003

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{FB6ED73C-D10C-4488-B54D-7482E7905352}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.028</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-K6KK8</PKey><PID>00432-077-1545051-86146</PID><PIDType>5</PIDType><SID>S-1-5-21-2847955061-2809903897-2795047695</SID><SYSTEM><Manufacturer>To be filled by O.E.M.</Manufacturer><Model>To be filled by O.E.M.</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>2002</Version><SMBIOSVersion major="2" minor="7"/><Date>20140226000000.000000+000</Date></BIOS><HWID>1FBB3607018400F2</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><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, UltimateN edition
Description: Windows Operating System - Windows(R) 7, RETAIL channel
Activation ID: dca01e19-01f5-4ce1-98b1-35fb7a323806
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00432-00172-077-154505-00-1033-7600.0000-2362015
Installation ID: 007824040851632664389241152641179831928963132713796062
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: K6KK8
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 8/24/2015 11:28:08 AM

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 6:23:2015 05:31
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: NAAAAAEAAwABAAEAAAAEAAAAAQABAAEAHKJ6REEuRlJ0xGTHNjTKNoqboK5F4YccgJ5udQ==

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
  FPDT			ALASKA		A M I
  SSDT			AMD   		POWERNOW
  BGRT			ALASKA		A M I

 

[Zebo12345]

Hey! I have great news for you both! As it turns out, service pack 1 was just in the second wave normally-- and it installed properly! I am very excited to see success for once!!! It was a group effort though, so time to use more emoticons! :grouphug: :roflmao: I'm so happy I could cry

Anyways, back to business. Windows says I am up to date, and checking for updates is coming back with nothing, however, 2 updates did fail to install:

Update for Windows 7 for x64-based Systems (KB3015428)
Update for Windows 7 for x64-based Systems (KB2998812)

Why does Windows say I am up to date if those two failed? Are either of those ones things I am going to want?The importance level just says recommended, not important. It says that they're supposed to help resolve issues in windows. I don't suppose that the effect is major enough to worry ourselves over, is it?

 

[Layback Bear]

I do see a problems in your log but don't know how to guide you but Noel will.

File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[7.1.7600.16395], Hr = 0x80092003 File Mismatch: C:\Windows\system32\wat\watux.exe[7.1.7600.16395], Hr = 0x80092003

I would not install either one of those KB's offered until Noel gets back. They could of caused your problem. I would just right tick on them and select Hide. You can always un-Hide them if need be later.
My system doesn't have either of those KB's installed.

 

[Layback Bear]

Just so you understand me correctly.

When it comes to Activation and Windows Updates as far as I'm concerned Noel is Boss.
I help when I can but for the most part I just try and stay out of the way so not to confuse things.

Noel's knowledge on such things is many levels above mine.

 

[Zebo12345]

Noel's knowledge on such things is many levels above mine.

Don't kid yourself. You may say his knowledge is many levels above yours, but that doesn't make you unqualified. What you know is still far above what I know. I understand staying out of his way as much as possible, but you aren't stupid. I am extremely impressed on Noel's understanding of people and computers alike, and more so on his patience, but I am also impressed for the same reasons with you. Don't put yourself down so much. You're just as important.

 

[NoelDP]

Noel's knowledge on such things is many levels above mine.

Don't kid yourself. You may say his knowledge is many levels above yours, but that doesn't make you unqualified. What you know is still far above what I know. I understand staying out of his way as much as possible, but you aren't stupid. I am extremely impressed on Noel's understanding of people and computers alike, and more so on his patience, but I am also impressed for the same reasons with you. Don't put yourself down so much. You're just as important.

I totally agree!

 

[Zebo12345]

So Noel, before I mark this as solved, should we handle that issue that Layback Bear found or would you rather have me make a new thread for that?

(Edit) Or should we have Layback bear handle it?

 

[Layback Bear]

Thank you all for the kind words.

Noel is the one that should handle those problems.
He is probably all read cooking up a batch of magic.

 

[Zebo12345]

Well, since the problem on the top of the post IS solved, I am going to mark it as solved now. This was an adventure, to say the least. If either of you feel it's necessary to fix the new problem that we found, then go ahead and tell me (marking it as solved doesn't disable replies, does it?) and I will comply.

Noel, you are really something else. I'm glad I didn't have to lose anything to fix this problem, because I was getting ready to do a clean install of Windows Pro instead. Glad I found this site, because I am very impressed with you.


If there's anything I could do to repay you two at all (donation pages, maybe?) then by all means, tell me.

 

[NoelDP]

Well - we at last seem to have got there!

As far as the WAT errors are concerned, I've seen this once or twice before - I think it may be the result of installing SP1 with WAT installed...

Close all open windows.
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 http://support.microsoft.com/kb/971033
Reboot

run another MGADiag report, and post it.