Remove From My Forums

Genuine Windows 7 no longer Genuine

Question
0

Sign in to vote

I posted up here months ago about this problem, Darin Smith you even ran my serial key and found it to be valid, your suggestion was to contact Microsoft GA support regarding the issue, which i did and it was a frustrating process in which they told me to contact regular microsoft support and start all over again with explaining, so the thing i did was just install the corresponding update (KB971033) which triggers the message and been living my life fine since, however it gets annoying i have this update in my queue and i was wondering if perhaps some new information has come into light that would fix my issue. I am posting my diag log and hopefully something stands out now that it didnt before, i see some tampered file warnings could that be it? if so how can i repair them

Diagnostic Report (1.9.0027.0):

-----------------------------------------

Windows Validation Data-->

Validation Code: 0x8004FE22

Cached Online Validation Code: N/A, hr = 0xc004f012

Windows Product Key: *****-*****-QK6V4-MYHG3-2T2G2

Windows Product Key Hash: xce6EIS9Iaxq/vzsoRdhAEpuOZo=

Windows Product ID: 00371-152-1195714-85237

Windows Product ID Type: 5

Windows License Type: Retail

Windows OS version: 6.1.7600.2.00010100.0.0.048

ID: {3FD2EB08-0CBC-45FE-AC86-DB59BD1FA3B7}(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: 7600.win7_gdr.100226-1909

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 Home and Student 2007 - 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

Browser Data-->

Proxy settings: N/A

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)

Default Browser: C:\Program Files (x86)\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\sppuinotify.dll[6.1.7600.16385], Hr = 0x80092003

Other data-->

Office Details: <GenuineResults><MachineData><UGUID>{3FD2EB08-0CBC-45FE-AC86-DB59BD1FA3B7}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-2T2G2</PKey><PID>00371-152-1195714-85237</PID><PIDType>5</PIDType><SID>S-1-5-21-1624814990-4046877217-409962553</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Studio XPS 1340</Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A11</Version><SMBIOSVersion major="2" minor="5"/><Date>20090908000000.000000+000</Date></BIOS><HWID>70BA3607018400F8</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>QA09 </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><Val>74402BE752D4F10</Val><Hash>pUEN9aSIiDIjsEBKYwX7T6K3seI=</Hash><Pid>81602-904-2662723-68317</Pid><PidType>1</PidType></Product></Products><Applications><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/></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, RETAIL channel

Activation ID: e838d943-63ed-4a0b-9fb1-47152908acc9

Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f

Extended PID: 00371-00170-152-119571-01-1033-7600.0000-2972009

Installation ID: 013443044341091501020176120053721283761353821470138082

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: 2T2G2

License Status: Licensed

Remaining Windows rearm count: 3

Trusted time: 7/27/2010 3:02:30 PM

Windows Activation Technologies-->

HrOffline: 0x8004FE22

HrOnline: N/A

HealthStatus: 0x0000000000000400

Event Time Stamp: 7:27:2010 15:01

ActiveX: Registered, Version: 7.1.7600.16395

Admin Service: Registered, Version: 7.1.7600.16395

HealthStatus Bitmask Output:

Tampered File: %systemroot%\system32\sppuinotify.dll|sppuinotify.dll.mui

HWID Data-->

HWID Hash Current: NgAAAAEABAABAAIAAAACAAAAAgABAAEA6GE2V1hpUMP4SZaZAE5qYZJbhKFah9wimjUCaUbK

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 PTLTD APIC

  FACP NVIDIA MCP79

  HPET PTLTD HPETTBL

  BOOT PTLTD $SBFTBL$

  MCFG PTLTD MCFG

  SLIC DELL QA09

  OSFR DELL DELL

  SSDT PmRef Cpu0Tst

  SSDT PmRef Cpu0Tst

  SSDT PmRef Cpu0Tst

  SSDT PmRef Cpu0Tst

  SSDT PmRef Cpu0Tst

  SSDT PmRef Cpu0Tst

  SSDT PmRef Cpu0Tst

  SSDT PmRef Cpu0Tst

  SSDT PmRef Cpu0Tst

Tuesday, July 27, 2010 7:08 PM

Answers

0

Sign in to vote
Hello DCosta43,

Your Product Key is not the issue. I have checked it and it is Valid and Genuine.

In your original post, I now see there were two issues.

a) The WAT update installed yet four of it's files were showing as not present.

b) One additional file was showing as corrupt or modified

Since you had the WAT update uninstalled, issue #1 was removed but issue #2 still remains. In other words, the problem is that there is a system file (sppuinotify.dll) that has become corrupt or has been modified in some way.

Once this file is repaired, you should be able to reinstall the WAT update and not receive a Non-gnuine error (assuming it installs correctly this time)

----------------from Diagnostic Report-----------------

File Scan Data-->

File Mismatch: C:\Windows\system32\sppuinotify.dll[6.1.7600.16385], Hr = 0x80092003

Tampered File: %systemroot%\system32\sppuinotify.dll|sppuinotify.dll.mui

----------------------------------------------------------

There are two things I can suggest to repair the file.

1. System Scan. The scan will look for bad Windows files and will attempt to repair them, if possible.

1) Click the Start Button
2) Type: cmd.exe
3) Right-click the cmd.exe file and select 'Run as Administrator'
4) In the CMD window, type: sfc /scannow
5) Reboot and see if that resolves the issue.

2. Repairing Windows using System Restore:

1) Click the Start button
2) In the Start Search field, type: System Restore and hit “Enter”
3) Select "Choose Different Restore Point", Put a check in the box that says "Show restore points older than 5 days", select the restore point that corresponds to the date Before you first noticed the issue.
4) Click the "Next" button.
5) Reboot and see if that resolves the issue.

If neither of those resolves the issue, I would normally refer you to Windows support. But since I have a feeling that would not appeal to you, the only other options I can provide would be to either Reinstall Windows or you can configure Windows Update to hide the WAT update (this will remove the update from the update queue).

I hope that is helpful and sorry I missed issue #2 in your original posting,

Darin MS
- Marked as answer by Darin Smith MS Tuesday, July 27, 2010 8:37 PM
Tuesday, July 27, 2010 8:35 PM

All replies

0

Sign in to vote
correction, my cd key was never checked by smith, he checked someone elses in my prior thread, my mistake, Windows GA support did validate it though, but i can provide it again, i just wanna resolve this issue without dealing with microsoft tech support.
- Proposed as answer by jackson gaice Sunday, August 1, 2010 9:22 PM
Tuesday, July 27, 2010 7:17 PM
0

Sign in to vote
Hello DCosta43,

Your Product Key is not the issue. I have checked it and it is Valid and Genuine.

In your original post, I now see there were two issues.

a) The WAT update installed yet four of it's files were showing as not present.

b) One additional file was showing as corrupt or modified

Since you had the WAT update uninstalled, issue #1 was removed but issue #2 still remains. In other words, the problem is that there is a system file (sppuinotify.dll) that has become corrupt or has been modified in some way.

Once this file is repaired, you should be able to reinstall the WAT update and not receive a Non-gnuine error (assuming it installs correctly this time)

----------------from Diagnostic Report-----------------

File Scan Data-->

File Mismatch: C:\Windows\system32\sppuinotify.dll[6.1.7600.16385], Hr = 0x80092003

Tampered File: %systemroot%\system32\sppuinotify.dll|sppuinotify.dll.mui

----------------------------------------------------------

There are two things I can suggest to repair the file.

1. System Scan. The scan will look for bad Windows files and will attempt to repair them, if possible.

1) Click the Start Button
2) Type: cmd.exe
3) Right-click the cmd.exe file and select 'Run as Administrator'
4) In the CMD window, type: sfc /scannow
5) Reboot and see if that resolves the issue.

2. Repairing Windows using System Restore:

1) Click the Start button
2) In the Start Search field, type: System Restore and hit “Enter”
3) Select "Choose Different Restore Point", Put a check in the box that says "Show restore points older than 5 days", select the restore point that corresponds to the date Before you first noticed the issue.
4) Click the "Next" button.
5) Reboot and see if that resolves the issue.

If neither of those resolves the issue, I would normally refer you to Windows support. But since I have a feeling that would not appeal to you, the only other options I can provide would be to either Reinstall Windows or you can configure Windows Update to hide the WAT update (this will remove the update from the update queue).

I hope that is helpful and sorry I missed issue #2 in your original posting,

Darin MS
- Marked as answer by Darin Smith MS Tuesday, July 27, 2010 8:37 PM
Tuesday, July 27, 2010 8:35 PM
0

Sign in to vote
the system restore probably wouldnt work since the issue happened as soon as i installed the corresponding windows update that started the message, so i got a feeling the file has been long corrupted, i did the scan it said it found corrupt files and was unable to fix some of them. if i was to replace that .dll would that work? or is it unique for every system/install ? would a reinstall over my current windows os work? i definitely dont want to install all over again, especially since i only have a windows 7 upgrade disc and no need to be sorry about before, perfectly alright
- Proposed as answer by jackson gaice Sunday, August 1, 2010 9:22 PM
Wednesday, July 28, 2010 4:19 AM
0

Sign in to vote
Replacing the file can sometimes work but the file must be the exact same (including the same build number 6.1.7600.16385) as the, now corrupt, file. It is more likely to work in Windos 7 since it's soo new, it is less likely to have many different build numbers for the same file.

Sorry I couldn't be more help,
Darin MS
- Proposed as answer by jackson gaice Sunday, August 1, 2010 9:22 PM
Wednesday, July 28, 2010 6:33 PM
0

Sign in to vote
you have been very helpful, but im wondering if you know where i could find a replacement file to try it out? i searched google and i didnt like the results i was coming across.
- Proposed as answer by jackson gaice Sunday, August 1, 2010 9:22 PM
Sunday, August 1, 2010 5:00 AM
0

Sign in to vote
"DCosta43" wrote in message news:cb8439b8-f783-4f0d-adee-a9490b3b9cae...
you have been very helpful, but im wondering if you know where i could find a replacement file to try it out? i searched google and i didnt like the results i was coming across.

You should be able to extract the original file from the system disk (or at least another running system), at it appears to be the RTM version.

The proper procedures for this are not simple - it's far better to use the SFC system to do the job for you if you can. - here's a link to a relevant post http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/6f7c07f8-ad92-419b-adff-12a5b96041f1

You didn't post a new result of the MGADiag report after running SFC - please do so, so that we can check that nothing important has come to light.

HTH

--

Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
- Proposed as answer by jackson gaice Sunday, August 1, 2010 9:22 PM
Sunday, August 1, 2010 9:23 AM

Moderator

Answered by:

Genuine Windows 7 no longer Genuine

Question

Answers

All replies