locked
Windows Vista OEM to my laptop becomes "not genuine" RRS feed

  • Question

  • My computer is a Fujitsu v1010.  It comes with Windows Vista Home Basic.  It was working fine until recently when my laptop crashed frequently due to "not enough disk space".  I tried phone activation but it didn't work.

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a8
    Windows Product Key: *****-*****-VFH4D-GBXC8-M4FBQ
    Windows Product Key Hash: jyHjZMNliIafeJ+Z1N1iTUBcbU8=
    Windows Product ID: 89572-OEM-7233974-83221
    Windows Product ID Type: 8
    Windows License Type: COA SLP
    Windows OS version: 6.0.6002.2.00010300.2.0.002
    ID: {91A0F150-BFC2-4FE7-AE12-C08C365BF90E}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Basic
    Architecture: 0x00000000
    Build lab: 6002.vistasp2_gdr.090803-2339
    TTS Error: T:20100309143525146-
    Validation Diagnostic:
    Resolution Status: N/A

    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: 6.0.6002.16398

    Windows XP 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: 100
    Version: 2.0.48.0
    OGAExec.exe Signed By: Microsoft
    OGAAddin.dll Signed By: Microsoft

    OGA Data-->
    Office Status: 100 Genuine
    Microsoft Office Standard 2007 - 100 Genuine
    2007 Microsoft Office system - 100 Genuine
    OGA Version: Registered, 2.0.48.0
    Signed By: Microsoft
    Office Diagnostics: 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\Internet Explorer\iexplore.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-->
    File Mismatch: C:\Windows\system32\ieframe.dll[8.0.6001.18865], Hr = 0x800b0100

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{91A0F150-BFC2-4FE7-AE12-C08C365BF90E}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6002.2.00010300.2.0.002</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-M4FBQ</PKey><PID>89572-OEM-7233974-83221</PID><PIDType>8</PIDType><SID>S-1-5-21-1388734985-3130889115-2159825140</SID><SYSTEM><Manufacturer>FUJITSU</Manufacturer><Model>LifeBook V1020</Model></SYSTEM><BIOS><Manufacturer>FUJITSU // Phoenix Technologies Ltd.</Manufacturer><Version>Version 1.07 </Version><SMBIOSVersion major="2" minor="4"/><Date>20080219000000.000000+000</Date></BIOS><HWID>C7333507018400FA</HWID><UserLCID>0C04</UserLCID><SystemLCID>0C04</SystemLCID><TimeZone>中國標準時間(GMT+08:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>FUJ   </OEMID><OEMTableID>PC      </OEMTableID></OEM><GANotification><File Name="OGAAddin.dll" Version="2.0.48.0"/></GANotification></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-0012-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Standard 2007</Name><Ver>12</Ver><Val>B08CBCBEE772777</Val><Hash>mEL6hsNYYmuWCmi94rZZHUuaUNU=</Hash><Pid>81607-955-0295131-64389</Pid><PidType>1</PidType></Product><Product GUID="{91120000-0031-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>2007 Microsoft Office system</Name><Ver>12</Ver><Val>3104E0B2B3F1826</Val><Hash>auiOvauauC06mcykMX6wyRTMNwg=</Hash><Pid>89451-OEM-6601915-46798</Pid><PidType>11</PidType></Product></Products><Applications><App Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAIdsAAAAAAAAYWECAOQPMaveQHyyUr/KASPvOhE4aiPWkIrToHXwxdqF/Ugq4HcHIwpLNxrgPu3c5x3lsctc+95KrdlC5Gfb7jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw2LChCixnhclyLKxemNGWeAZZ7gKBe0zV79O6WBpkOHI7r2zaE2EWpXYbNEYRYtDUzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM

    Licensing Data-->
    Software licensing service version: 6.0.6002.18005
    Name: Windows(TM) Vista, HomeBasic edition
    Description: Windows Operating System - Vista, OEM_COA_SLP channel
    Activation ID: 91dbad68-4713-4f9c-b351-6e77a8361741
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 89572-00144-339-783221-02-1028-6002.0000-1512010
    Installation ID: 011164509551416786390616618520915403059133874213574906
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43473
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43474
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=43476
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43475
    Partial Product Key: M4FBQ
    License Status: Unlicensed

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: NgAAAAEAAwABAAIAAQABAAAAAwABAAEAeqhyMhD8DjuMwkaDWm+K9x7Z8vSKBx5HAhCsViqF

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x20000
    OEMID and OEMTableID Consistent: yes
    BIOS Information:
      ACPI Table Name OEMID Value OEMTableID Value
      APIC   FUJ     FJNB1E0
      FACP   FUJ     PC     
      HPET   FUJ     FJNB1E0
      BOOT   FUJ     FJNB1E0
      MCFG   FUJ     FJNB1E0
      SSDT   FUJ     FJNB1E0
      SSDT   FUJ     FJNB1E0
      SSDT   FUJ     FJNB1E0
      SSDT   FUJ     FJNB1E0
      SLIC   FUJ     PC     

    Please help!

    Piggybun

     

    Monday, May 31, 2010 9:25 AM

Answers

  • Hello piggybun,

     Your Diagnostic Report is telling me that you Vista is suffering from a Trusted Store Tamper.  There are files, in Windows, that have what is known as a Digital Signature. A Digital Signature is an industry standard that ensures that a file is, in fact, from the specified source

    Example: lets say you get a Printer Driver that is Digitally Signed from HP. Since the Digital Signature was created by a Trusted Source a Certificate is created within Window's Trusted Store. The Digital Signature is dependent on the file's Hash (think fingerprint) so if the file is changed in any way it's Digital Signature then becomes invalid.  So lets say that the HP Driver got modified by some sort of Malware. The File's Hash would no longer match the hash listed in the Digitally Signature (or the Signature may not even be readable at that point). The Digital Signature become invalid because windows now don't know what has been done to that file, so the file can no longer be trusted. This in turn invalidates the corresponding Certificate within the Trusted Store.

      What I have described in the above example is basically what is happening with your Vista.  Some Digitally Signed file has been modified in some way (replaced, rewritten or just become corrupt) and the Certificate within Windows's Trusted Store has become invalid (i.e. no longer trusted) and that is what has triggered the Non-Genuine messaging.

      Unfortunatly, none of my tools are able to pinpoint which file/signature/certificate is causing the problem. However there are a few thing you can try that may correct the issue.


      1) First off not all Digitally Signed files are Drivers, but from experience we have found that this issue seems to occure the most with Drivers.  So my first suggestion is to confirm that all your hardware drivers are up to date. Note: Figuring out id a Driver is up to date and/or replacing a driver with a more current one can sometimes take semi-advanced computer knowledge and me explaining the process is outside the scope of this forum. If you do not know how to work with Drivers seak assistance or skip down to #2 or #3 below

      2) Restore Windows back to a past System Restore Point.

    1) Reboot Vista into Safe Mode
    2) Click the ‘Start’ button
    3) In the Start Search field, type: System Restore and hit “Enter” keyboard key
    4) Select "Choose Different Restore Point", Put a check in the box that says "Show restore points older than 5 days", select the restore point that corresponds to a date Before you first noticed the issue.
    5) Click the "Next" button.
    6) Reboot back into Normal mode

      3) Repair Windows using the 'sfc /scannow' command

    The Scan Now will look for any bad Windows files and attempt to repair them, if possible (it isn't always able to)

    1) Login to Vista in Normal Mode (not safe mode)
    2) Launch an Internet Browser
    3) Type: %windir%\system32\ in the browser's address field
    4) Scroll down till you find the file cmd.exe
    5) Right-click the file and select Run as Administrator
    6) In the CMD window, type: sfc /scannow
    7) Reboot twice and see if that resolves the issue.

    If none of my suggestions resolves the issue, then the only other thing I can suggest is to either create a (no cost) support request at http://support.microsoft.com/gp/contactwga or reinstall Vista.

    Thank you,


    Darin MS
    Thursday, June 3, 2010 7:26 PM

All replies

  • "piggybun" wrote in message news:b8b124b8-1849-4785-8b87-08c6a45007c6...
    > My computer is a Fujitsu v1010. It comes with Windows Vista Home Basic.
    > It was working fine until recently when my laptop crashed frequently due
    > to "not enough disk space". I tried phone activation but it didn't work.
    >
     
     
    It looks as if you may have had a virus infection lately -
    File Scan Data-->
    File Mismatch: C:\Windows\system32\ieframe.dll[8.0.6001.18865], Hr =
    0x800b0100
    This is almost certainly the cause of your problem, an can be the result of
    a virus infection.
     
    I suggest running the System File Checker - it will scan the system files,
    and attempt to repair any damage.
     
    First, though, you need to make sure that your system is free of any viruses
    or other malware - run a full system scan with up-to-date definitions with
    your Anti-Virus (which is?)
    Then download, install, update and run a full scan with MalwareBytes
    Anti-Malware from http://www.malwarebytes.org
     
    once complete, and you've rebooted a couple of times to make sure that all
    work is finished, open an Elevated Command Prompt:-
    Click on Start, and enter CMD in the Search box - this should bring a
    single result into the upper section - right click on the CMD.exe file, and
    select Run As Administrator.
    Accept the UAC prompt if you get one - then at the prompt in the window,
    type
     
    SF /SCANNOW
     
    and hit the Enter key
    wait until it's finished (don't worry if it says that it couldn't repair all
    files - mine always does), and then exit the command window, and reboot.
    The try the Validation again.
     
    HTH
    --
    Noel Paton
    CrashFixPC
     
    Nil Carborundum Illegitemi
    www.crashfixpc.co.uk
     
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Monday, May 31, 2010 10:25 AM
    Moderator
  • Noel,

    Thank you for you prompt reply.

    My Anti-Virus is  AVG9 Free Edition.  I scan/update once a day.  Is it good enough?

    I use wireless router TP-Link TL-WR841ND.  I am pretty much running it on default settings because I don't know how to set it.  I first used it without any encrytion.  Later I found someone that I didn't recognise on the DHCP clients list.  Now I am using WPA2 AES.  I also discovered someone I didn't recognise on UPnP.  Now I disable UPnP.  I live near a college/university so there are kids who know much more than me.  I thought the wireless router has some sort of a firewall, doesn't it?

    Thanks.

    Piggybun

     

    Monday, May 31, 2010 11:08 AM
  • "piggybun" wrote in message news:d8191472-50a3-4ded-b1fa-89d401a1f405...
    > Noel,
    >
    > Thank you for you prompt reply.
    >
    > My Anti-Virus is AVG9 Free Edition. I scan/update once a day. Is it
    > good enough?
    >
    > I use wireless router TP-Link TL-WR841ND. I am pretty much running it on
    > default settings because I don't know how to set it. I first used it
    > without any encrytion. Later I found someone that I didn't recognise on
    > the DHCP clients list. Now I am using WPA2 AES. I also discovered
    > someone I didn't recognise on UPnP. Now I disable UPnP. I live near a
    > college/university so there are kids who know much more than me. I
    > thought the wireless router has some sort of a firewall, doesn't it?
    >
     
    Piggybun
     
    AVG is reasonably good- it's become a bit of a resource hog since v8.5, and
    I've stopped recommending it - but if it works for you, then it works!
    You still need to run the Malwarebytes scan, though - it WILL find things
    that got through AVG - I can almost guarantee that!
     
    WPA is the minimum encryption that's necessary nowadays - WPA2 is fine.
    UPnP - you may be a little confused here - the UPnP server on the router
    often has its own IP address, and MAC number. UPnP depends on an existing
    connection - it's extremely difficult to attack a router or link to it using
    UPnP without already having access.
     
    Firewalls.... you could write a book about them,,,, err.... someone already
    has! <g>
    Seriously - ALL computers should have their own firewall, and have it
    active. In Vista, the Windows Firewall is sufficient (so long as it's
    switched on) for 99.9% of home users (and the other 0.1% deserve everything
    they get <G>). The reason is to prevent cross-infection from other PC's on
    the network, or infection through Wireless networking.
    Your Router does indeed include a NAT firewall, which should keep you safe
    from most problems, but remember that it (almost) never gets updated, so may
    fail if someone comes up with a way through it. Your own PC's firewall acts
    as a backup, which can easily be updated, either by MS through Windows
    Updates, or you (by getting a new firewall, or adjusting the exceptions in
    Windows firewall).
     
    --
    Noel Paton
    CrashFixPC
     
    Nil Carborundum Illegitemi
    www.crashfixpc.co.uk
     
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Monday, May 31, 2010 11:54 AM
    Moderator
  • Hello piggybun,

     Your Diagnostic Report is telling me that you Vista is suffering from a Trusted Store Tamper.  There are files, in Windows, that have what is known as a Digital Signature. A Digital Signature is an industry standard that ensures that a file is, in fact, from the specified source

    Example: lets say you get a Printer Driver that is Digitally Signed from HP. Since the Digital Signature was created by a Trusted Source a Certificate is created within Window's Trusted Store. The Digital Signature is dependent on the file's Hash (think fingerprint) so if the file is changed in any way it's Digital Signature then becomes invalid.  So lets say that the HP Driver got modified by some sort of Malware. The File's Hash would no longer match the hash listed in the Digitally Signature (or the Signature may not even be readable at that point). The Digital Signature become invalid because windows now don't know what has been done to that file, so the file can no longer be trusted. This in turn invalidates the corresponding Certificate within the Trusted Store.

      What I have described in the above example is basically what is happening with your Vista.  Some Digitally Signed file has been modified in some way (replaced, rewritten or just become corrupt) and the Certificate within Windows's Trusted Store has become invalid (i.e. no longer trusted) and that is what has triggered the Non-Genuine messaging.

      Unfortunatly, none of my tools are able to pinpoint which file/signature/certificate is causing the problem. However there are a few thing you can try that may correct the issue.


      1) First off not all Digitally Signed files are Drivers, but from experience we have found that this issue seems to occure the most with Drivers.  So my first suggestion is to confirm that all your hardware drivers are up to date. Note: Figuring out id a Driver is up to date and/or replacing a driver with a more current one can sometimes take semi-advanced computer knowledge and me explaining the process is outside the scope of this forum. If you do not know how to work with Drivers seak assistance or skip down to #2 or #3 below

      2) Restore Windows back to a past System Restore Point.

    1) Reboot Vista into Safe Mode
    2) Click the ‘Start’ button
    3) In the Start Search field, type: System Restore and hit “Enter” keyboard key
    4) Select "Choose Different Restore Point", Put a check in the box that says "Show restore points older than 5 days", select the restore point that corresponds to a date Before you first noticed the issue.
    5) Click the "Next" button.
    6) Reboot back into Normal mode

      3) Repair Windows using the 'sfc /scannow' command

    The Scan Now will look for any bad Windows files and attempt to repair them, if possible (it isn't always able to)

    1) Login to Vista in Normal Mode (not safe mode)
    2) Launch an Internet Browser
    3) Type: %windir%\system32\ in the browser's address field
    4) Scroll down till you find the file cmd.exe
    5) Right-click the file and select Run as Administrator
    6) In the CMD window, type: sfc /scannow
    7) Reboot twice and see if that resolves the issue.

    If none of my suggestions resolves the issue, then the only other thing I can suggest is to either create a (no cost) support request at http://support.microsoft.com/gp/contactwga or reinstall Vista.

    Thank you,


    Darin MS
    Thursday, June 3, 2010 7:26 PM