Knowledge Base

Resolve Windows 7 "not genuine" issues



Dell OEM Microsoft Windows 7 install suddenly becomes "not genuine" by Windows Genuine Advantage (WGA)


Windows is not Genuine issues that may include error 0xC8000247

User was receiving a popup that told him his version of windows was not authentic.


Why is this happening?

There are numerous items that can cause a "Windows is not Genuine" error in Windows 7. Dell Original Equipment Manufacturer (OEM) Windows uses a special OEM (system Locked Pre-installation (SLP) key and OEM Basic in/out system (BIOS) Flag for activation of the operating system (OS).

In some cases the BIOS flag is set for an older version of Windows and after a period of time WGA will flag the OS as "NOT GENUINE". These include but are not limited to the following:

  • Time and date not correct on the system, or time zone selected not matching time zone of actual location.
  • All required Windows Updates not installed (Several have to do with changes legislated on Daylight Savings Time).
  • Software or driver corruption of the OS
  • Viruses and malware
NOTE: This article supplies only ONE possible solution to a specific WGA issue where the BIOS flag has been set, it does not apply to all WGA issues.

What is the solution?

There are several steps that can be used to address this issue. Once time/Date/Time zone and Windows updates have been addressed, if the issue still occurs try the following:

  • Download and install the Latest Available BIOS revision for the system then re-run the WGA tool (https://www.microsoft.com/genuine/validate/ , Click Validate Now Button) Issue should be resolved.
  • For systems equipped with Intel Rapid Storage Technology, update the IRST drivers from http://support.dell.com or Intel Drivers & Software. Once the driver has been updated, cold reboot (Reboot system from an OFF Power state) the system TWICE . Reference: http://social.microsoft.com/Forums/en-US/genuinewindows7/thread/3d9c5a6c-812b-4a7d-8b67-209b4d974e34
  • If this does not resolve, try these steps:
    1. Click the Start button
    2. Type: CMD.exe in the start search field
    3. Right-Click on CMD.exe and select Run as Administrator
    4. Type: net stop sppsvc and press the Enter key. (You may be asked if you are sure, select yes)
    5. Type: cd c:\windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform and press the Enter key.
    6. Type: rename tokens.dat tokens.bar and press the Enter key.
    7. Type: slui and press the Enter key.
    8. After a couple of seconds Windows Activation dialog will appear. You likely be asked to re-enter your product key and/or re-activate. For Dell systems it will auto-authenticate.
  • If still not resolved continue with these steps:
    1. Use the command prompt window you have open, or if closed re-open Run as Administrator
    2. Open Folder Options in control panel and change the Hidden Files and Folders to "Show hidden files, folders, and drives"
    3. Open Windows Explorer and navigate to: c:\windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform.
    4. Rename all files except the Cache folder. (example: REN Tokens.dat tokens_.dat then press the Enter key.)
    5. Right-Click in the SoftwareProtectionPlatform folder and choose properties and click on the Previous Versions tab.
    6. Choose a date before the issue started and copy just the tokens.dat file to the cache folder.
    7. Type: slui and press the Enter key.
  • If still not resolved your system may have other factors causing this issue, the most notable are viruses and malware. Ensure that you have you system checked for these potential threats.
  • If you have tried all these options without success, contact technical support for additional troubleshooting options.
NOTE: If your system is no longer under warranty, operating system support by Dell Technical Support is a fee based service.




Article ID: SLN104591

Last Date Modified: 01/03/2018 01:08 PM


Rate this article

Accurate
Useful
Easy to understand
Was this article helpful?
Yes No
Send us feedback
Comments cannot contain these special characters: <>()\
Sorry, our feedback system is currently down. Please try again later.

Thank you for your feedback.