Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Non-genuine windows 7 message RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    I'm having trouble with my OEM copy of Windows 7. It came pre-installed with my Sony VAIO, and it's now saying that it's not a genuine copy. The thing is, when i run the diagnostics tool, it says that my copy is genuine. When I go to http://www.microsoft.com/genuine/ and click 'Validate Windows' it says that it's not genuine too. I can't tell wich of them is correct.

    EDIT: I read another topic about this, where someone said that a program called 'vistalizator' might be the cause. Is this correct? Because the tech-guy installed this in my laptop. He installed Office 2007 too, and said it was a trial version. Is this correct? It doesn't seem to be a trial version...

    Diagnostic Report (1.9.0019.0):

    -----------------------------------------

    WGA Data-->

    Validation Status: Genuine

    Validation Code: 0

     

    Cached Validation Code: N/A, hr = 0xc004f012

    Windows Product Key: *****-*****-VGV87-C7XPK-CGKHQ

    Windows Product Key Hash: sdEjrEJjW0FuXAhegYxl8GAkBYg=

    Windows Product ID: 00359-OEM-8992687-00016

    Windows Product ID Type: 2

    Windows License Type: OEM SLP

    Windows OS version: 6.1.7600.2.00010300.0.0.003

    ID: {3D37528D-EB9A-49E0-A7C7-C00BF64FD231}(3)

    Is Admin: Yes

    TestCab: 0x0

    WGA Version: N/A, hr = 0x80070002

    Signed By: N/A, hr = 0x80070002

    Product Name: Windows 7 Home Premium

    Architecture: 0x00000009

    Build lab: 7600.win7_rtm.090713-1255

    TTS Error: 

    Validation Diagnostic: 

    Resolution Status: N/A

     

    WgaER Data-->

    ThreatID(s): N/A, hr = 0x80070002

    Version: N/A, hr = 0x80070002

     

    WGA 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: 103 Blocked VLK

    Microsoft Office Enterprise 2007 - 103 Blocked VLK

    OGA Version: N/A, 0x80070002

    Signed By: N/A, hr = 0x80070002

    Office Diagnostics: B4D0AA8B-604-645_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)\Google\Chrome\Application\chrome.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-->

     

    Other data-->

    Office Details: <GenuineResults><MachineData><UGUID>{3D37528D-EB9A-49E0-A7C7-C00BF64FD231}</UGUID><Version>1.9.0019.0</Version><OS>6.1.7600.2.00010300.0.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-CGKHQ</PKey><PID>00359-OEM-8992687-00016</PID><PIDType>2</PIDType><SID>S-1-5-21-1100102089-4182998913-3393405583</SID><SYSTEM><Manufacturer>Sony Corporation</Manufacturer><Model>VGN-NW350F</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>R2010Y4</Version><SMBIOSVersion major="2" minor="4"/><Date>20091113000000.000000+000</Date></BIOS><HWID>AFB83607018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0416</SystemLCID><TimeZone>Hora oficial do Brasil(GMT-03:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>Sony</OEMID><OEMTableID>VAIO</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>103</Result><Products><Product GUID="{90120000-0030-0000-0000-0000000FF1CE}"><LegitResult>103</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>ACD7202654E586</Val><Hash>fFic3JgCreGGRxyF8uMWB4R4Jcg=</Hash><Pid>89388-707-1528066-65315</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="12" Result="103"/><App Id="16" Version="12" Result="103"/><App Id="18" Version="12" Result="103"/><App Id="19" Version="12" Result="103"/><App Id="1A" Version="12" Result="103"/><App Id="1B" Version="12" Result="103"/><App Id="44" Version="12" Result="103"/><App Id="A1" Version="12" Result="103"/><App Id="BA" Version="12" Result="103"/></Applications></Office></Software></GenuineResults>  

     

    Spsys.log Content: 0x80070002

     

    Licensing Data-->

    Versão do serviço de licença do software: 6.1.7600.16385

     

    Nome: Windows(R) 7, HomePremium edition

    Descrição: Windows Operating System - Windows(R) 7, OEM_SLP channel

    Identificação da Ativação: d2c04e90-c3dd-4260-b0f3-f845f5d27d64

    Identificação da Aplicação: 55c92734-d682-4d71-983e-d6ec3f16059f

    PID estendido: 00359-00178-926-800016-02-2057-7600.0000-3132009

    Identificação da Instalação: 016450058234567612107136460575430933920342342721088816

    URL do Certificado do Processador: http://go.microsoft.com/fwlink/?LinkID=88338

    URL do Certificado da Máquina: http://go.microsoft.com/fwlink/?LinkID=88339

    URL da Licença de Uso: http://go.microsoft.com/fwlink/?LinkID=88341

    URL do Certificado da Chave do Produto (Product Key): http://go.microsoft.com/fwlink/?LinkID=88340

    Chave do Produto (Product Key) Parcial: CGKHQ

    Status da Licença: Licenciado

    Contagem de rearmação restante do Windows: 3

    Hora confiável: 4/3/2010 12:19:25 PM

     

    Windows Activation Technologies-->

    HrOffline: 0x8004FE21

    HrOnline: 0x00000000

    HealthStatus: 0x000000000000EF60

    Event Time Stamp: 4:3:2010 11:42

    WAT Activex: Registered

    WAT Admin Service: Registered

     

    HWID Data-->

    HWID Hash Current: MgAAAAEAAwABAAIAAAABAAAAAgABAAEA6GFy+LQEMsG+lSBAljdEUeihzkdkCnx5Rso=

     

    OEM Activation 1.0 Data-->

    N/A

     

    OEM Activation 2.0 Data-->

    BIOS valid for OA 2.0: yes

    Windows marker version: 0x20001

    OEMID and OEMTableID Consistent: yes

    BIOS Information: 

      ACPI Table Name OEMID Value OEMTableID Value

      APIC Sony VAIO

      FACP Sony VAIO

      HPET Sony VAIO

      MCFG Sony VAIO

      SLIC Sony VAIO

      SSDT Sony VAIO

      SSDT Sony VAIO

     

    Saturday, April 3, 2010 3:21 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi, I was just re reading the unaswered questions and see you asked about vistlizator, yes, that is probably the cause of your problem. Remove it, reboot and try validating again. Sorry it took so long to see that and respond. Someone was playing games with this thread but that isn't an escuse for me missing something that obvious, especialy when you specificaly asked.

    Again, sorry

    Carl

    Monday, April 5, 2010 11:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi, I was just re reading the unaswered questions and see you asked about vistlizator, yes, that is probably the cause of your problem. Remove it, reboot and try validating again. Sorry it took so long to see that and respond. Someone was playing games with this thread but that isn't an escuse for me missing something that obvious, especialy when you specificaly asked.

    Again, sorry

    Carl


    Be sure that you set your Windows laguage files back to normal before you uninstall the Vistalator. Vistalator causes the problem by changing laguage files (known as Mui files) in versions of Windows that arn't supposed to have that ability.  Windows checks it's own Activation and Validation related system files (and thier mui counterparts) and if the files don't match what Windows knows should be there, Windows can't trust the files and therefore can't trust any Activation or Validation that occured with those files. to resolve the issue reset the mui files back to the way they were, uninstall vistalator and then go to http://microsoft.com/geuine and click the Validate Windows button.

    Tell us how that has worked for you,

     

    Darin MS
    Tuesday, April 6, 2010 9:44 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    It appears that something may be interfering with your activation files, you have an HrOffline error code. Also you have a blocked VLK for office 2007 enterprise. My suggestion is uninstall office 2007 enteriprise and try to validate again by going to www.microsoft.com/genuine and validate windows. If that clears up the problem then you will need to obtain a valid copy of office. I would suggest you take part in the public beta for office 2010, and purchase a copy of that when it comes available sometime in June. The Beta is good for several months beyone the June release (as rumor would have it).

    If after fixing the office issue you still have validation issues then post a new report.

    Thanks

    Carl

    Download and run MGAdiag and paste the results in your thread go.microsoft.com/fwlink/?linkid=52012
    Saturday, April 3, 2010 5:38 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi, I was just re reading the unaswered questions and see you asked about vistlizator, yes, that is probably the cause of your problem. Remove it, reboot and try validating again. Sorry it took so long to see that and respond. Someone was playing games with this thread but that isn't an escuse for me missing something that obvious, especialy when you specificaly asked.

    Again, sorry

    Carl

    Monday, April 5, 2010 11:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi, I was just re reading the unaswered questions and see you asked about vistlizator, yes, that is probably the cause of your problem. Remove it, reboot and try validating again. Sorry it took so long to see that and respond. Someone was playing games with this thread but that isn't an escuse for me missing something that obvious, especialy when you specificaly asked.

    Again, sorry

    Carl


    Be sure that you set your Windows laguage files back to normal before you uninstall the Vistalator. Vistalator causes the problem by changing laguage files (known as Mui files) in versions of Windows that arn't supposed to have that ability.  Windows checks it's own Activation and Validation related system files (and thier mui counterparts) and if the files don't match what Windows knows should be there, Windows can't trust the files and therefore can't trust any Activation or Validation that occured with those files. to resolve the issue reset the mui files back to the way they were, uninstall vistalator and then go to http://microsoft.com/geuine and click the Validate Windows button.

    Tell us how that has worked for you,

     

    Darin MS
    Tuesday, April 6, 2010 9:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi, I was just re reading the unaswered questions and see you asked about vistlizator, yes, that is probably the cause of your problem. Remove it, reboot and try validating again. Sorry it took so long to see that and respond. Someone was playing games with this thread but that isn't an escuse for me missing something that obvious, especialy when you specificaly asked.

    Again, sorry

    Carl


    Be sure that you set your Windows laguage files back to normal before you uninstall the Vistalator. Vistalator causes the problem by changing laguage files (known as Mui files) in versions of Windows that arn't supposed to have that ability.  Windows checks it's own Activation and Validation related system files (and thier mui counterparts) and if the files don't match what Windows knows should be there, Windows can't trust the files and therefore can't trust any Activation or Validation that occured with those files. to resolve the issue reset the mui files back to the way they were, uninstall vistalator and then go to http://microsoft.com/geuine and click the Validate Windows button.

    Tell us how that has worked for you,

     

    Darin MS
    Tuesday, April 6, 2010 9:44 PM