Unable to install SP1

I believe this is the other report you wanted.

Code:

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

Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-QCPVQ-KHRB8-RMV82
Windows Product Key Hash: +Rj3N34NLM2JqoBO/OzgzTZXgbY=
Windows Product ID: 00359-OEM-8992687-00095
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7600.2.00010300.0.0.003
ID: {DC7D5FE3-BD59-4B37-B5F9-687A6389C9DE}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: Registered, 1.9.9.1
Signed By: Microsoft
Product Name: Windows 7 Home Premium
Architecture: 0x00000009
Build lab: 7600.win7_gdr.130104-1435
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 Professional Edition 2003 - 100 Genuine
Microsoft Office FrontPage 2003 - 100 Genuine
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: B4D0AA8B-604-645_77F760FE-153-80070002_7E90FEE8-175-80070002_B4D0AA8B-604-645_B4D0AA8B-604-645_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

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
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-->

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{DC7D5FE3-BD59-4B37-B5F9-687A6389C9DE}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010300.0.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-RMV82</PKey><PID>00359-OEM-8992687-00095</PID><PIDType>2</PIDType><SID>S-1-5-21-2797263906-3868735475-3496056987</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Studio XPS 8000</Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A01</Version><SMBIOSVersion major="2" minor="5"/><Date>20090811000000.000000+000</Date></BIOS><HWID>888B3607018400FE</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><OEMID>DELL  </OEMID><OEMTableID>FX09   </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90110409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office Professional Edition 2003</Name><Ver>11</Ver><Val>38EF2A0DBE48502</Val><Hash>dp88hS8gfhgkhkMO6YwnQrOIr3o=</Hash><Pid>73931-641-2280835-57978</Pid><PidType>14</PidType></Product><Product GUID="{90170409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office FrontPage 2003</Name><Ver>11</Ver><Val>983F231E10F4D04</Val><Hash>oBlxA1NUDls17arnMEc7vYhOHE0=</Hash><Pid>72079-642-7878955-55960</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="11" Result="100"/><App Id="16" Version="11" Result="100"/><App Id="17" Version="11" Result="100"/><App Id="18" Version="11" Result="100"/><App Id="19" Version="11" Result="100"/><App Id="1A" Version="11" Result="100"/><App Id="1B" Version="11" Result="100"/><App Id="44" Version="11" Result="100"/></Applications></Office></Software></GenuineResults>  

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7600.16385

Name: Windows(R) 7, HomePremium edition
Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
Activation ID: d2c04e90-c3dd-4260-b0f3-f845f5d27d64
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00359-00178-926-800095-02-1033-7600.0000-2962009
Installation ID: 009013117736136182744053787655437474627656006710913070
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: RMV82
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 3/22/2013 6:17:02 PM

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 2:18:2013 20:22
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:

HWID Data-->
HWID Hash Current: MgAAAAEABAABAAEAAAABAAAAAgABAAEAln2u9iLo9teUVoCWQsZyKxJ4PjfsX5ZwdlY=

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            DELL          FX09    
  FACP            DELL          FX09    
  HPET            DELL          OEMHPET 
  MCFG            DELL          OEMMCFG 
  SLIC            DELL          FX09   
  OSFR            DELL          FX09    
  OEMB            DELL          FX09    
  GSCI            DELL          GMCHSCI 
  SSDT            DpgPmm        CpuPm

Sorry about that - the MGADiag report request is a holdover from the boilerplate that I usually user for Genuine Windows problems - I try to remember to delete it when posting for other problems :) (It does occasionally come in handy for other uses as well)

Great - the fixes worked exactly as they should have done. and your Windows now is back to what passes for normal at least as far as SFC is concerned.

Please try SP1 again now - preferably from the downloaded Standalone installer.

Please post an MGADiag report - it may give us some clues....



https://www.sevenforums.com/windows-updates-activation/234159-windows-genuine-activation-issue-posting-instructions.html

Ignore errors produced when clicking on the Copy button - they simply mean that the tool could not create the backup files for some reason. The data is still copied to the clipboard for pasting to your response.

Dunno why I asked for it again - must have gotten cross-threaded! :)

The simplest solution is probably going to be a repair install - but first please tell us where you got the ISO/disk for SP1 from?

Ah - that should be OK then :)
They are however not ISO files but executables (apart from the 1.9GB multi-purpose one)- you'll need to copy the file to the hard drive and run it from there.

with the 1.9GB one there is a little extra front-end code to allow use from DVD.

zone 5 said:

NoelDP said:

I'll post a fix protocol for these later - but please post the data that Yard Dog requested, as there may be more corruption.

I don't know if it matters, but I saw those errors in the log file too, and even though I have no idea what they mean, I do know, that I do NOT have an AMD processor, I have an intel I7

NoelDP said:

for MS's purposes there are only three types of processor

x86/INTEL - 32-bit Intel or AMD type processors
AMD64 - 64-bit Intel or AMD processors
I64 - Itanium processors.

Yours is an X64 processor from Intel - therefore falls into the AMD64 camp

Please post the CheckSUR report.

Sorry to interrupt guys but I just wanted to share a little information with you quickly. A few months ago I had a user ask me to confirm whether it was the right update because he had a x64 Intel processor and the files clearly said amd64 so I looked into it.

AMD was the first company to bring a 64 bit processor to the market, the Opteron chip:

Opteron - Wikipedia, the free encyclopedia

Windows had to adjust slightly to allow the execution of 64 bit code from within the Windows environment to fully utilise the 64 bit processing power and 64 bit OSs were introduced. As AMD made the chip, these new files/folders were named with amd64... to distinguish them from their 32 bit counterparts, beginning x86.... Since this date, Intel has also brought various 64 bit chips to the market but as the amd64 files were coded into Windows from the beginning it would be very time consuming, and frankly the opportunity cost is way too high, for Microsoft to change these to x64... so the files stayed :) Why they didn't name them x64... in the first place, like they did with 32 bit files, is beyond me!

They had to differentiate from the Itanium chips which were under development at the time as Intel's AMD-buster chips (and have only really ever been used in Servers, since day one).
In various places in the OS, the variants are referred to in different ways as well - e.g. x86 can be called INTEL