Answered by:
Windows 7 Non-genuine Issue

Question
-
I am building a computer for my father and installed an OEM version of Windows 7. I have validated it online and by phone and still keep getting the same window popping up to tell me that this is not a genuine Windows system. The code at the bottom of the window is 0x8004fe21. Looking online, it seems that this is a common issue for Windows! Below is the WGA. I have the OEM disk. I do not have Vistalizator on my computer (which seems to be a common problem) as far as I can tell (I am a newbie). Any help out there?
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 0x8004FE21
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-YDF8F-PC72K-PBM9F
Windows Product Key Hash: qMJMj7qvEb9llfAKArhRyL3tOs4=
Windows Product ID: 00371-OEM-9044783-59228
Windows Product ID Type: 3
Windows License Type: OEM System Builder
Windows OS version: 6.1.7600.2.00010100.0.0.048
ID: {A51D3EB6-D263-42FD-80AC-B85EB06C6752}(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.101026-1503
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)\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\en-US\sppc.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\sppcext.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\slc.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\slcext.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\sppuinotify.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\slui.exe.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\sppcomapi.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\sppcommdlg.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\sppsvc.exe.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\user32.dll.mui[6.1.7600.16385], Hr = 0x800b0100
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{A51D3EB6-D263-42FD-80AC-B85EB06C6752}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-PBM9F</PKey><PID>00371-OEM-9044783-59228</PID><PIDType>3</PIDType><SID>S-1-5-21-3488413639-4289860858-2696467944</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>1702 </Version><SMBIOSVersion major="2" minor="5"/><Date>20101222000000.000000+000</Date></BIOS><HWID>8AB83607018400FA</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>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_COA_NSLP channel
Activation ID: e120e868-3df2-464a-95a0-b52fa5ada4bf
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00371-00180-447-859228-02-1033-7600.0000-1192011
Installation ID: 020650306991158315833404839163809062315656091651377084
Processor Certificate URL:
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: PBM9F
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 4/30/2011 9:38:57 PM
Windows Activation Technologies-->
HrOffline: 0x8004FE21
HrOnline: N/A
HealthStatus: 0x000000000000EF60
Event Time Stamp: 4:29:2011 17:41
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:
Tampered File: %systemroot%\system32\sppc.dll|sppc.dll.mui
Tampered File: %systemroot%\system32\sppcext.dll|sppcext.dll.mui
Tampered File: %systemroot%\system32\slc.dll|slc.dll.mui
Tampered File: %systemroot%\system32\slcext.dll|slcext.dll.mui
Tampered File: %systemroot%\system32\sppuinotify.dll|sppuinotify.dll.mui
Tampered File: %systemroot%\system32\slui.exe|slui.exe.mui|COM Registration
Tampered File: %systemroot%\system32\sppcomapi.dll|sppcomapi.dll.mui
Tampered File: %systemroot%\system32\sppcommdlg.dll|sppcommdlg.dll.mui
Tampered File: %systemroot%\system32\sppsvc.exe|sppsvc.exe.mui
HWID Data-->
HWID Hash Current: NgAAAAEABgABAAEAAAACAAAAAQABAAEA6GE4z6C2EDP04+7pMA9IxFTyUjAsAepFPpMWVI4u
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 122210 APIC1056
FACP 122210 FACP1056
SRAT AMD FAM_F_10
HPET 122210 OEMHPET
MCFG 122210 OEMMCFG
OEMB 122210 OEMB1056
SSDT A M I POWERNOW
Sunday, May 1, 2011 10:15 AM
Answers
-
"polymersn" wrote in message news:4c9f4fb0-a1ff-4d90-9790-98f9f31d7c07...
I am building a computer for my father and installed an OEM version of Windows 7. I have validated it online and by phone and still keep getting the same window popping up to tell me that this is not a genuine Windows system. The code at the bottom of the window is 0x8004fe21. Looking online, it seems that this is a common issue for Windows! Below is the WGA. I have the OEM disk. I do not have Vistalizator on my computer (which seems to be a common problem) as far as I can tell (I am a newbie). Any help out there?
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 0x8004FE21
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-YDF8F-PC72K-PBM9F
Windows Product Key Hash: qMJMj7qvEb9llfAKArhRyL3tOs4=
Windows Product ID: 00371-OEM-9044783-59228
Windows Product ID Type: 3
Windows License Type: OEM System Builder
Windows OS version: 6.1.7600.2.00010100.0.0.048
File Scan Data-->
File Mismatch: C:\Windows\system32\en-US\sppc.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\sppcext.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\slc.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\slcext.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\sppuinotify.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\slui.exe.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\sppcomapi.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\sppcommdlg.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\sppsvc.exe.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\user32.dll.mui[6.1.7600.16385], Hr = 0x800b0100
Your problem has been caused by the (non-legal) installation of alternative Language interfaces, using a program called Vistalizator - please see the following stickie for details.
http://social.microsoft.com/Forums/en-US/genuinewindows7/thread/6f6b1cb8-e84e-4c1f-a2ac-181a77d2f772
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth- Marked as answer by Darin Smith MS Monday, May 2, 2011 11:11 PM
Sunday, May 1, 2011 12:29 PMModerator
All replies
-
"polymersn" wrote in message news:4c9f4fb0-a1ff-4d90-9790-98f9f31d7c07...
I am building a computer for my father and installed an OEM version of Windows 7. I have validated it online and by phone and still keep getting the same window popping up to tell me that this is not a genuine Windows system. The code at the bottom of the window is 0x8004fe21. Looking online, it seems that this is a common issue for Windows! Below is the WGA. I have the OEM disk. I do not have Vistalizator on my computer (which seems to be a common problem) as far as I can tell (I am a newbie). Any help out there?
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 0x8004FE21
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-YDF8F-PC72K-PBM9F
Windows Product Key Hash: qMJMj7qvEb9llfAKArhRyL3tOs4=
Windows Product ID: 00371-OEM-9044783-59228
Windows Product ID Type: 3
Windows License Type: OEM System Builder
Windows OS version: 6.1.7600.2.00010100.0.0.048
File Scan Data-->
File Mismatch: C:\Windows\system32\en-US\sppc.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\sppcext.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\slc.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\slcext.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\sppuinotify.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\slui.exe.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\sppcomapi.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\sppcommdlg.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\sppsvc.exe.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\user32.dll.mui[6.1.7600.16385], Hr = 0x800b0100
Your problem has been caused by the (non-legal) installation of alternative Language interfaces, using a program called Vistalizator - please see the following stickie for details.
http://social.microsoft.com/Forums/en-US/genuinewindows7/thread/6f6b1cb8-e84e-4c1f-a2ac-181a77d2f772
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth- Marked as answer by Darin Smith MS Monday, May 2, 2011 11:11 PM
Sunday, May 1, 2011 12:29 PMModerator -
Since I was the only one to install anything on the computer and I am pretty sure I did not install any alternative language interfaces, I'm not completely convinced that this was the problem. Anyhow, I did contact Microsoft Tech support, they tried the standard stuff, weren't interested in the diagnostic report, did not fix the problem, scheduled a call back that they did not follow up on. I tried Restore and that did not work. Since there was nothing on the computer of any importance, I did a custom installation and all is working now. This may be enough to send me back to Mac's or try Linux. Great job, Microsoft. Remind me again...what the hell I'm am paying for???????Friday, May 6, 2011 10:21 AM
-
Look at the "MUI" in the file name extensions. MUI = multilingual user interface. Read the sticky above and contact support for the removal tool. Whether you are the person who installed it or not you still need to resolve the problem. If you use two or more language interfaces on your computer simply upgrade to Ultimate and then download all the language packs you want for free.
Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.Friday, May 6, 2011 2:28 PMAnswerer -
"Cbarnhorst" wrote in message news:82184f15-8030-4d53-91f3-e5fc136500c8...Look at the "MUI" in the file name extensions. MUI = multilingual user interface. Read the sticky above and contact support for the removal tool. Whether you are the person who installed it or not you still need to resolve the problem. If you use two or more language interfaces on your computer simply upgrade to Ultimate and then download all the language packs you want for free.
Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
(He did resolve it by a Recovery, Colin)
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed SlothFriday, May 6, 2011 4:13 PMModerator -
I did look at the file extensions. I did contact support for the tool...that became another frustrating problem. They have their own way of going about the problem and want you to follow their process. They were not intersted in looking at the diagnostic report. They did not call me back when they said they would. If this had been anything other than a new computer, this email would not have been anything close to civil in terms of words about Microsoft. I did not lose any files and all I needed to do was reinstall windows 7 and the drivers. That took less time than waiting for Microsoft to finally figure out how to pick up the phone and dial my number. In a less sarcastic note, thanks goes to Noel for helping...although your post to this thread was not the answer I used, your suggestions to others with similar/same problems solved the problem (at least for now). Good luck to the rest you.
Saturday, May 7, 2011 10:34 AM -
"polymersn" wrote in message news:b56f6ee6-5660-46f9-858b-3e258547af29...
I did look at the file extensions. I did contact support for the tool...that became another frustrating problem. They have their own way of going about the problem and want you to follow their process. They were not intersted in looking at the diagnostic report. They did not call me back when they said they would. If this had been anything other than a new computer, this email would not have been anything close to civil in terms of words about Microsoft. I did not lose any files and all I needed to do was reinstall windows 7 and the drivers. That took less time than waiting for Microsoft to finally figure out how to pick up the phone and dial my number. In a less sarcastic note, thanks goes to Noel for helping...although your post to this thread was not the answer I used, your suggestions to others with similar/same problems solved the problem (at least for now). Good luck to the rest you.
Good luck! - glad I was able to point you in the right direction :)MS are usually pretty good about call-backs, but 'stuff' happens, and this may have been outsourced to Delhi or somewhere :)
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed SlothSaturday, May 7, 2011 12:41 PMModerator