Genuine Advantage Validation

Back in 2006 after getting upset over all the pirated copies of Windows XP being used, Microsoft decided to roll out Windows Genuine Advantage. This “critical” Windows update would be installed on your machine and then the Windows Product key being used would be checked against known blacklisted keys and whether it’s been activated before. If the information in the Microsoft database doesn’t match the identity of your machine, the check for a genuine Windows will fail and cause the wallpaper and background to reset every 60 minutes.

This will throw notifications on your desktop that Windows is not a genuine copy and you won’t be able to get all important Windows updates because of the online WGA validation component. The Genuine Advantage components (WGA Notifications and WGA Validation) would be fine if they were 100% accurate, but of course they aren’t. It’s entirely possible to get a genuine failure even if your Windows is fully legitimate.

Office Genuine Advantage (OGA) was a program by Microsoft, similar to Windows Genuine Advantage (WGA). Validation rejects those product keys that have either been leaked widely or those key-generated to pass through activation but not validation. Starting October 27, 2006, users of Office Update were required to validate the legitimacy of. Windows Genuine Advantage Validation V1.9.42.0.rar - DOWNLOAD.

Being Windows, there are ways around this such as the removing WGA notifications tool after it’s been installed or bypassing the online validation component that stops you updating. But if you feel your Windows SHOULD be passing these checks and want to try and find out a bit more about why it’s failing, there is a tool to help.

The Microsoft Genuine Advantage Diagnostic Tool runs a check and gives several pieces of information about the parts of your system that affect its Genuine status and what is possibly causing it to fail. There are a few cases where it might automatically resolve any problems for you, but if not, you could get a much better idea about why the failure has occurred.

Simply download the tool and run the MGADiag.exe and click to Continue for the check results. There will be some useful information such as the Validation Status might tell you if the product key is invalid or a blacklisted corporate key. You might also get notified if the LegitCheckControl.dll file has been tampered with in which case there could be some form of crack on your Windows install which has been detected. If there is an issue the tool can fix, click the Resolve button.

Because Office also has a similar Office Genuine Advantage (OGA) component, there is a tab to check that too. The Browser tab will gather the security settings from Internet Explorer to make sure they are correct to allow the WGA component to connect with the internet.

WGA Notification settings are checked for errors in the Notifications tab and it will tell you if the components are installed and whether they are correct and digitally signed. If you’re being nagged with the black background and not genuine watermark, you can remove WGA Notifications using a small utility while you investigate the causes.

Download Microsoft Genuine Advantage Diagnostic Tool

If the diagnostic tool is showing what you believe to be the incorrect product key, or you have a known pirated key and want to legitimize Windows XP with a real key you have, there is a tool available that lets you do this. It’s called the Windows Product key Update Tool from Microsoft and will let you enter another XP product key and then activate Windows online.

Download and run the tool and it will first check for corrupt or non standard DLL and executable files that can affect activation and ask if you want to repair any that are found. After that simply enter your product key making sure you’re trying to enter the correct key for the correct version of Windows XP (Home / Pro etc.), and once accepted, it will activate your copy of Windows online making it genuine.

If you want to do a similar thing on Vista or Windows 7, visit this Microsoft webpage for updating your product key.

Download Windows Product Key Update Tool

You might also like:

Remove Windows XP Genuine Advantage Notifications with RemoveWGAmuBlinder – Blind Microsoft/Windows Update ValidationUnable to Activate Windows 7 Error Code 0xC004C008Fix for Blank or Empty Windows Features List in Vista and 7Error Code 66A when Updating Microsoft .NET Framework 4 from Windows Update

excellent work brother. you are amazing

Reply

thanks a lot!!! it made my windows a genuine one!!!

Reply

thank you raymond.
now my pc was genuine…
thanks a lot

Reply

Windows Genuine Advantage Validation Tool Windows 10

Thank you Raymond

Reply

Nice …

Reply

thanks this very helpful

Windows Genuine Advantage Validation Tool

Reply

Thanks man Hid dtc1000 windows 10 driver.

Reply

very good

Reply-->

This article introduces how to validate the OEM activation key in Windows 10.

Original product version: Windows 10 - all editions
Original KB number: 4346763

Background

Starting at Windows 10 Creators Update (build 1703), Windows activation behavior has changed so that the unique OA3 Digital Product Key (DPK) is not always presented as the currently installed key in the device. Instead, the system behaves as follows:

• Windows 10 (including all versions starting at Windows 10 Creators Update) is deployed to a device by having the appropriate default product key. You can run slmgr /dli or slmgr /dlv Top 10 offline games like pubg under 50mb. Adobe illustrator barcode plugin. to show the partial default product key instead of the OA3 DPK as the current license in the firmware. The product ID that is displayed on the Settings > System > About page is not unique for the Windows 10 key that is being used.

• A device that is running any Windows 10 OEM client edition, such as Windows Home or Windows Professional, and is activated by using the OA3 DPK in the firmware is upgraded to a newer version of Windows (for example, build 1703 to build 1709). However, sometimes running slmgr /dli or slmgr /dlv does not show the OA3 DPK as the current license. Instead, these commands show the default product key.

The behavior that is described here is by design. The activation and user experience are not affected. However, OA validation in the factory may be affected as follows:

• The output of the slmgr /dlv or slmgr /dli command is not necessarily the last five (5) digits of the injected DPK. Therefore, you can no longer rely upon these commands to return the expected results.

Recommendations for validating the product ID against the product key ID of OA3 DPK

Every OEM has a different manufacturing process that they have adopted through years of experience in manufacturing Windows. Specifically, to validate the DPK against the installed Windows 10 edition, we recommend that you not rely on the output of slmgr /dlv or slmgr/dli but, instead, use the latest OA3Tool as follows:

• OA3TOOL /Validate

  Runs a validation pass to make sure that the MSDM table exists, the MSDM table header includes all the required fields, and the MSDM table entries exist and comply with the correct formats.

• OA3TOOL /CheckEdition

  Does a cross-check between the injected DPK and the target Windows edition if they match.

Can Microsoft ensure that the system will always activate if I do the recommended steps

The Windows activation system is designed to use the product key that is injected into the firmware of the computer during manufacturing. It automatically activates the device when the device first comes online. This operation is used daily on thousands of devices. As an additional check, OEMs are encouraged to run the complete end-to-end validation process, including activation on a subset of the devices, to validate the user experience with their PCs. If you experience any issues, engage with us through the usual channels.

Why did Microsoft remove the ability to check the last five digits of the product by using slmgr

SLMGR is a legacy tool. Although we have not updated slmgr, and because of updates in successive system builds, the last five digits of the product key that are shown by slmgr /dlv or /dli do not match the product key that is injected into the system BIOS. This is by design. We have no intentions of validating SLMGR for every Windows 10 release or making any other changes. We are very open to feedback regarding the OA3 tool and what additional capabilities we can add to it to improve the manufacturing flow.