Windows Genuine and Activation Issue Posting Instructions

[Brink]

Windows Genuine and Activation Issue Posting Instructions​

​

   Information

This is a set of posting instructions to use so that you can get better help here at SevenForums.com when you have a Windows non-genuine and/or activation issue.

Here's How:

1. Click on the Download buttons below to download the MGADiag Tool .

Download

View attachment MGADiag.exe
​

2. Save the MGADiag.exe file to your desktop and run it.

3. If prompted, click on Run and Yes (UAC).

4. Click on the Continue button. (see screenshot below)

​

5. When the report is finished, click on the Copy button. (see screenshot below)
NOTE: Often, when clicking the Copy button, you may get an error message. Just ignore the error. All it means is that the backup copies of certain files couldn't be saved to disk (in the root directory). The Copy process will still work, and pasting to your post will still function as expected.

​

6. Right click on a empty area in your post here at Seven Forums, and click on Paste to place a copy of the MGADiag report into your post.
NOTE: The MGADIAG report does not contain any sensitive or personal information, and is best posted un-edited for us to be able to help.

7. In your post, select (highlight) all of the MGADiag report that you just pasted, and click on the code box # toolbar icon to wrap the report in a code box when posted. (see screenshot below)

​

8. Add any additional details you like about your issue before or after the code wrapped MGADiag report, then click on Submit New Thread at the bottom of the post.


That's it,
Shawn

Related Tutorials

---

• How to Activate Windows 7 Online
• How to Activate Windows 7 by Phone
• How to Change the Product Key Number in Windows 7
• How to Find and See the Windows 7 Product Key Number

 

[Dwarf]

Please DO NOT forget Step 7 to enclose the resultant report in a code box as this makes it easier for us to read, especially when we refer backwards and forwards to it from any subsequent replies in your thread. I've had to add the code tags to a few reports lately because of this.