Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
After MSE version update a few days ago it says my Windows is not genuine. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Running XP SP3.   A few days ago MSE reported that a new version was available.   As soon as it finished installed, it turned orange and reported that my Windows install was reported as not genuine.   What's going on?  I have tried to run the validation check in MSE, but it remains orange/not genuine.

    Thanks for any help you can give.


    Microsoft Security Essentials Version:  1.0.1961.0
    Antimalware Client Version: 2.1.6519.0
    Engine Version: 1.1.5502.0
    Antivirus definitions: 1.77.953.0
    Antispyware definitions: 1.77.953.0

    WGA Diag tool shows:

    Diagnostic Report (1.9.0019.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Genuine
    Validation Code: 0

    Cached Validation Code: N/A
    Windows Product Key: *****-*****-9FGKW-DQQBC-JGKFB
    Windows Product Key Hash: e8+QFDdkWEbMQ/RO0hxkw+R23Hw=
    Windows Product ID: 55274-338-4535083-22684
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 5.1.2600.2.00010100.3.0.pro
    ID: {218E7BF8-A171-4332-937E-DD35B6AF58AD}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.9.40.0
    Signed By: Microsoft
    Product Name: N/A
    Architecture: N/A
    Build lab: N/A
    TTS Error: N/A
    Validation Diagnostic: 025D1FF3-230-1
    Resolution Status: N/A

    WgaER Data-->
    ThreatID(s): N/A
    Version: N/A

    WGA Notifications Data-->
    Cached Result: 0
    File Exists: Yes
    Version: 1.9.40.0
    WgaTray.exe Signed By: Microsoft
    WgaLogon.dll Signed By: Microsoft

    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: 1.7.105.35
    OGAExec.exe Signed By: Microsoft
    OGAAddin.dll Signed By: Microsoft

    OGA Data-->
    Office Status: 100 Genuine
    Microsoft Office Enterprise 2007 - 100 Genuine
    OGA Version: Registered, 1.7.111.0
    Signed By: Microsoft
    Office Diagnostics: B4D0AA8B-604-645_B4D0AA8B-604-645_B4D0AA8B-604-645_7E90FEE8-198-80004005_025D1FF3-230-1

     

    • Moved by Stephen Davies MS Monday, March 15, 2010 10:25 PM Validation Issue (From:Microsoft Security Essentials: Getting Started and Upgrading)
    Saturday, March 13, 2010 2:22 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    did you buy it from someone or new from a store?  if it was new it should have a genuine microsoft sticker on it somewhere.  call microsoft and they will ask for the numbers on the sticker and they can help you fix the problem.

    I've heard of a few people with this problem and Microsoft has given them a new product key
    Sunday, March 14, 2010 7:29 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    More people are adding this question to the forum of this problem with XP SP3 and Microsoft Security Essentials version 1.0.1961.0 which is upgrade (as opposed to udate of definitions) issued March 9th. Seems to be a real problem that only affects some computers (my laptop is fine but my desktop has problem). Suggest opening a support case. I figure the more people complain, the quicker Microsoft will try to solve this. I openned  support case and was contacted last Friday. Below is a copy of what I posted in the thread/question I started when I first had this problem. I've been checking the forum for similar posts with this same problem but haven't found any that had an answer.

    Microsoft Support contacted me and spent over 2 hours via shared support accessing my computer. First established without a doubt that Windows was genuine and pretty much narrowed problem down to Microsoft Security Essentials. Went through uninstall. Had older MSE install/exe on my desktop so he reinstalled. Then he upgraded which went through validation okay and then same problem again after upgrade install. He said they've been getting more notices about this and I see another post in the forum. He thanked me for spending so much time with him as they needed to collect more information on why this is happening in some computers. Let's hope there is a fix soon.
    Sunday, March 14, 2010 9:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    integra97,

    Your basic advice to open a support case is good, but your reasoning is a bit off.

    The more people that do this the better the information that Support can provide to the MSE Developers, so the more quickly they can fully understand the true issue and potentially create a real fix.  It's obvious that as you stated, a few specific systems are having this issue, but it's less obvious what the eact reason(s) might be, since there may be more than one.

    The reason you don't see any 'workaround' solutions provided here is that at least at this point there aren't any and I really doubt there ever will be.  Since this issue isn't related to either configuration or something that's normally controllable by the user of the PC, it's most likely going to require some modification to either the MSE code or something within the WGA process itself.

    Rob
    Monday, March 15, 2010 5:31 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Check this link,
    http://social.answers.microsoft.com/Forums/en-US/msestart/thread/3f877be5-3a04-47b7-a3ee-835910633110

    It fixed my problem.
    • Proposed as answer by 120387 Wednesday, March 17, 2010 9:01 PM
    • Marked as answer by Darin Smith MS Friday, March 26, 2010 8:55 PM
    Wednesday, March 17, 2010 5:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The reason you don't see any 'workaround' solutions provided here is that at least at this point there aren't any and I really doubt there ever will be.  Since this issue isn't related to either configuration or something that's normally controllable by the user of the PC, it's most likely going to require some modification to either the MSE code or something within the WGA process itself.

    Rob

    Another reason that you don't see a Workaround coming from WGA is because WGA is working as intended. Customers XP Validates at http://microsoft.com/genuine as Genuine.  Their Diag Reports show Genuine but when installing MSE, it is MSE that is reporting the XP as Non-genuine.

    Any workaround or fix would need to come from the MSE side of the fence.

    However, I have seen a number of people that have fixed the issue by following the steps in the link that KCHUONE provided above.
    (http://social.answers.microsoft.com/Forums/en-US/msestart/thread/3f877be5-3a04-47b7-a3ee-835910633110)

    Thank you,
    Darin MS
    • Marked as answer by richeyrock Thursday, March 18, 2010 2:43 PM
    Wednesday, March 17, 2010 9:19 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This fixed it for me too!
    Thanks!
    Thursday, March 18, 2010 2:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The same for me. Seems to have fixed that annoying message. Been bugging me for many months now, and since one or more of the MS service pack downloads.

    The instructions provided were not quite exact to my XP Pro OS but close enough to figure it out and the messages have ceased.

    Thanks agn -- jg

    Tuesday, March 23, 2010 8:52 PM