locked
MSI Netbook - Windows 7 not genuine build 7601 RRS feed

  • Question

  • Hi,
    Been having the dreaded Windows Is Not Genuine messages for a while now on my MSI netbook - it came with Windows 7 Home Premium pre installed so one would assume it's a totally legit OEM copy.
    Just phoned Microsoft who told me to phone MSI, which I thought was a bit strange as it's surely a Microsoft issue?
    Anyway here's the diagnostic report from MGADIAG, if anyone could help that would be great!
    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Code: 0x8004FE22
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-D96PV-T9B9D-M8X2Q
    Windows Product Key Hash: Fq/JsPUI1NdT6veDtiDB8N1RQUs=
    Windows Product ID: 00359-OEM-8992687-00246
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7601.2.00010300.1.0.003
    ID: {476F99BA-26F3-4A6F-A78F-ABC22D8EF91A}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Home Premium
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_gdr.110408-1631
    TTS Error: 
    Validation Diagnostic: 
    Resolution Status: N/A
    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    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: 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: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    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:\Users\Thomas\AppData\Local\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>{476F99BA-26F3-4A6F-A78F-ABC22D8EF91A}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-M8X2Q</PKey><PID>00359-OEM-8992687-00246</PID><PIDType>2</PIDType><SID>S-1-5-21-4064593905-2348922626-2013407367</SID><SYSTEM><Manufacturer>Micro-Star International</Manufacturer><Model>U230</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>A1243AMS V1.19</Version><SMBIOSVersion major="2" minor="5"/><Date>20100201000000.000000+000</Date></BIOS><HWID>6C343D07018400F6</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>MSI_NB</OEMID><OEMTableID>MEGABOOK</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  
    Spsys.log Content: 0x80070002
    Licensing Data-->
    Software licensing service version: 6.1.7601.17514
    Name: Windows(R) 7, HomePremium edition
    Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
    Activation ID: d2c04e90-c3dd-4260-b0f3-f845f5d27d64
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00359-00178-926-800246-02-2057-7601.0000-1452011
    Installation ID: 012624145540880036203775397525182170577582111325525974
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
    Partial Product Key: M8X2Q
    License Status: Notification
    Notification Reason: 0xC004F063.
    Remaining Windows rearm count: 3
    Trusted time: 31/05/2011 09:18:27
    Windows Activation Technologies-->
    HrOffline: 0x8004FE22
    HrOnline: N/A
    HealthStatus: 0x0000000000002000
    Event Time Stamp: 5:29:2011 15:51
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:
    Tampered File: %systemroot%\system32\sppcomapi.dll|sppcomapi.dll.mui
    HWID Data-->
    HWID Hash Current: NgAAAAAABAABAAIAAAACAAAAAwABAAEA6GFc7N4UEDOwz1TyQB1GsIiS6kU63BC7DCFy5QK0
    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 MSI_NB APIC1505
      FACP MSI_NB MEGABOOK
      HPET MSI_NB OEMHPET 
      MCFG MSI_NB OEMMCFG 
      SLIC MSI_NB MEGABOOK
      OEMB MSI_NB OEMB1505
      SSDT A M I POWERNOW
    Tuesday, May 31, 2011 8:21 AM

Answers

  • "Thomas Orger" wrote in message news:e2c40170-a920-47bf-bb89-df2c3d6a0ef3...

    Yes I'm a bit wary of doing a system restore as it might roll back a lot of things on my system...

    I did install SP1 but I think it was a few weeks after before it started complaining about not being genuine.

    I have another working Windows 7 machine, could I copy the .dll file over from that and see if it fixes it?


    I doubt very much that it would - as I say, if the file itself were damaged, it would be reported earlier as well. It may be worth a go, though.
     
    OK - that rules out SP1 as a cause then - you would probably have started getting non-genuine messages within 72 hours if it were.
     
    System Restore doesn't normally touch user-data (but backups are always a good idea!), so if you've not installed much in the way of programs since the start of the problem, it could also be worth a go - remember that you'd have to reinstall any updates affected, not only for Windows, but also for all other programs and drivers installed. <nag>This is why it's always best to tackle problems early, rather than leave them festering</nag>
     
    I suspect that we're down to emergency measures here.....
    1) a repair install of Windows - which would entail your removing SP1 (etc. etc.) or finding someone with a Retail copy with SP1 already included and borrowing their disk.
    2) Contact MS support, and see if they can help - it may be free, or it may not, depending on exactly how they work it nowadays.
    Hopefully they'll be able to get you sorted without having to reinstall.
     
    North America: http://support.microsoft.com/contactus/cu_sc_genadv_master?ws=support&ws=support#tab4
     
    Outside North America:
    http://support.microsoft.com/contactus/?ws=support#tab0
     
    Please let us know if  (and how!) MS manage to repair the problem without a repair install of the OS - it would be useful for future reference!

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, May 31, 2011 10:32 AM
    Moderator

All replies

  • Tampered File: %systemroot%\system32\sppcomapi.dll|sppcomapi.dll.mui


    Click the Start Orb & type cmd.exe into the search. Right click it & run as administrator.

    Type the following command: sfc /scannow & hit enter.

    Wait for the process to finish, then reboot the system. Then try & Validate Online using Internet Explorer.

     

    If the tampered file cannot be fixed by the sfc /scannow. You can attempt a system restore to a previous point before you had this problem.



    Tuesday, May 31, 2011 8:49 AM
  • This is the result of running SFC:

     

    Beginning system scan.  This process will take some time.

     

    Beginning verification phase of system scan.

    Verification 100% complete.

    Windows Resource Protection found corrupt files but was unable to fix some of them.

    Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example

    C:\Windows\Logs\CBS\CBS.log

     

    I tried to open CBS.log and it says Access Denied, and it's about 12Mbytes but I can upload it somewhere if that would help?

     

    Thanks,

    Tom

    Tuesday, May 31, 2011 9:21 AM
  • "Thomas Orger" wrote in message news:0eb9a4d2-5fd1-458a-8bcf-a902a72d99d4...

    This is the result of running SFC:

     

    Beginning system scan.  This process will take some time.

     

    Beginning verification phase of system scan.

    Verification 100% complete.

    Windows Resource Protection found corrupt files but was unable to fix some of them.

    Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example

    C:\Windows\Logs\CBS\CBS.log

     

    I tried to open CBS.log and it says Access Denied, and it's about 12Mbytes but I can upload it somewhere if that would help?

     

    Thanks,

    Tom


    You can look at it yourself - see here for instructions....
     
    I know I *hate* looking through the things myself :)
    Most of the time the errors are insignificant, anyhow.
     
    Please post a new MGADiag report after rebooting the system

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, May 31, 2011 9:34 AM
    Moderator
  • There's lots of messages in the SFC log like this:

     

    2011-05-14 17:44:03, Info                  CSI    0000013a [SR] Verifying 100 (0x0000000000000064) components

    2011-05-14 17:44:03, Info                  CSI    0000013b [SR] Beginning Verify and Repair transaction

    2011-05-14 17:44:08, Info                  CSI    0000013c [SR] Cannot repair member file [l:18{9}]"slmgr.vbs" of Microsoft-Windows-Security-SPP-Tools, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked

    2011-05-14 17:44:08, Info                  CSI    0000013d [SR] Cannot repair member file [l:26{13}]"sppcomapi.dll" of Microsoft-Windows-Security-SPP-UX, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked

    2011-05-14 17:44:11, Info                  CSI    0000013e [SR] Cannot repair member file [l:26{13}]"sppcomapi.dll" of Microsoft-Windows-Security-SPP-UX, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked

    2011-05-14 17:44:11, Info                  CSI    0000013f [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"

    2011-05-14 17:44:13, Info                  CSI    00000140 [SR] Cannot repair member file [l:18{9}]"slmgr.vbs" of Microsoft-Windows-Security-SPP-Tools, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked

    2011-05-14 17:44:13, Info                  CSI    00000141 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"

    2011-05-14 17:44:14, Info                  CSI    00000143 [SR] Verify complete

     

    and here's the new MGADIAG:

     

    Diagnostic Report (1.9.0027.0):

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

    Windows Validation Data-->

     

    Validation Code: 0x8004FE22

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

    Windows Product Key: *****-*****-D96PV-T9B9D-M8X2Q

    Windows Product Key Hash: Fq/JsPUI1NdT6veDtiDB8N1RQUs=

    Windows Product ID: 00359-OEM-8992687-00246

    Windows Product ID Type: 2

    Windows License Type: OEM SLP

    Windows OS version: 6.1.7601.2.00010300.1.0.003

    ID: {476F99BA-26F3-4A6F-A78F-ABC22D8EF91A}(3)

    Is Admin: Yes

    TestCab: 0x0

    LegitcheckControl ActiveX: N/A, hr = 0x80070002

    Signed By: N/A, hr = 0x80070002

    Product Name: Windows 7 Home Premium

    Architecture: 0x00000009

    Build lab: 7601.win7sp1_gdr.110408-1631

    TTS Error: 

    Validation Diagnostic: 

    Resolution Status: N/A

     

    Vista WgaER Data-->

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

    Version: N/A, hr = 0x80070002

     

    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: 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: 109 N/A

    OGA Version: N/A, 0x80070002

    Signed By: N/A, hr = 0x80070002

    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:\Users\Thomas\AppData\Local\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>{476F99BA-26F3-4A6F-A78F-ABC22D8EF91A}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-M8X2Q</PKey><PID>00359-OEM-8992687-00246</PID><PIDType>2</PIDType><SID>S-1-5-21-4064593905-2348922626-2013407367</SID><SYSTEM><Manufacturer>Micro-Star International</Manufacturer><Model>U230</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>A1243AMS V1.19</Version><SMBIOSVersion major="2" minor="5"/><Date>20100201000000.000000+000</Date></BIOS><HWID>6C343D07018400F6</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>MSI_NB</OEMID><OEMTableID>MEGABOOK</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

     

    Spsys.log Content: 0x80070002

     

    Licensing Data-->

    Software licensing service version: 6.1.7601.17514

     

    Name: Windows(R) 7, HomePremium edition

    Description: Windows Operating System - Windows(R) 7, OEM_SLP channel

    Activation ID: d2c04e90-c3dd-4260-b0f3-f845f5d27d64

    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f

    Extended PID: 00359-00178-926-800246-02-2057-7601.0000-1452011

    Installation ID: 012624145540880036203775397525182170577582111325525974

    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338

    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339

    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341

    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340

    Partial Product Key: M8X2Q

    License Status: Notification

    Notification Reason: 0xC004F063.

    Remaining Windows rearm count: 3

    Trusted time: 31/05/2011 10:40:02

     

    Windows Activation Technologies-->

    HrOffline: 0x8004FE22

    HrOnline: N/A

    HealthStatus: 0x0000000000002000

    Event Time Stamp: 5:31:2011 10:27

    ActiveX: Registered, Version: 7.1.7600.16395

    Admin Service: Registered, Version: 7.1.7600.16395

    HealthStatus Bitmask Output:

    Tampered File: %systemroot%\system32\sppcomapi.dll|sppcomapi.dll.mui

     

     

    HWID Data-->

    HWID Hash Current: NgAAAAAABAABAAIAAAACAAAAAwABAAEA6GFc7N4UEDOwz1TyQB1GsIiS6kU63BC7DCFy5QK0

     

    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 MSI_NB APIC1505

      FACP MSI_NB MEGABOOK

      HPET MSI_NB OEMHPET 

      MCFG MSI_NB OEMMCFG 

      SLIC MSI_NB MEGABOOK

      OEMB MSI_NB OEMB1505

      SSDT A M I POWERNOW

     

     

    Tuesday, May 31, 2011 9:39 AM
  • "Thomas Orger" wrote in message news:1f16beb1-2e43-4531-8874-5fa85c0231c9...

    There's lots of messages in the SFC log like this:

     

    2011-05-14 17:44:03, Info                  CSI    0000013a [SR] Verifying 100 (0x0000000000000064) components

    2011-05-14 17:44:03, Info                  CSI    0000013b [SR] Beginning Verify and Repair transaction

    2011-05-14 17:44:08, Info                  CSI    0000013c [SR] Cannot repair member file [l:18{9}]"slmgr.vbs" of Microsoft-Windows-Security-SPP-Tools, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked

    2011-05-14 17:44:08, Info                  CSI    0000013d [SR] Cannot repair member file [l:26{13}]"sppcomapi.dll" of Microsoft-Windows-Security-SPP-UX, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked

    2011-05-14 17:44:11, Info                  CSI    0000013e [SR] Cannot repair member file [l:26{13}]"sppcomapi.dll" of Microsoft-Windows-Security-SPP-UX, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked

    2011-05-14 17:44:11, Info                  CSI    0000013f [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"

    2011-05-14 17:44:13, Info                  CSI    00000140 [SR] Cannot repair member file [l:18{9}]"slmgr.vbs" of Microsoft-Windows-Security-SPP-Tools, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked

    2011-05-14 17:44:13, Info                  CSI    00000141 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"

    2011-05-14 17:44:14, Info                  CSI    00000143 [SR] Verify complete

     

    and here's the new MGADIAG:

     

    Diagnostic Report (1.9.0027.0):

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

    Windows Validation Data-->

     

    Validation Code: 0x8004FE22

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

    Windows Product Key: *****-*****-D96PV-T9B9D-M8X2Q

    Windows Product Key Hash: Fq/JsPUI1NdT6veDtiDB8N1RQUs=

    Windows Product ID: 00359-OEM-8992687-00246

    Windows Product ID Type: 2

    Windows License Type: OEM SLP

    Windows OS version: 6.1.7601.2.00010300.1.0.003

     

    Name: Windows(R) 7, HomePremium edition

    Description: Windows Operating System - Windows(R) 7, OEM_SLP channel

    Partial Product Key: M8X2Q

    License Status: Notification

    Notification Reason: 0xC004F063.

    Remaining Windows rearm count: 3

    Trusted time: 31/05/2011 10:40:02

     

    Windows Activation Technologies-->

    HrOffline: 0x8004FE22

    HrOnline: N/A

    HealthStatus: 0x0000000000002000

    Event Time Stamp: 5:31:2011 10:27

    ActiveX: Registered, Version: 7.1.7600.16395

    Admin Service: Registered, Version: 7.1.7600.16395

    HealthStatus Bitmask Output:

    Tampered File: %systemroot%\system32\sppcomapi.dll|sppcomapi.dll.mui


    It looks to me as if the problem lies in the registry rather than with the filesystem - if the file were the problem it would appear under the File Scan Data heading as well.
    Since you say you've ignored this for a while, I suspect that using System Restore may not be the best approach - unless your system is relatively stable, with no/few installs/uninstalls since this started happening?
     
    I see you installed SP1 from Windows Updates - was that possibly the trigger that caused the problem?
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, May 31, 2011 10:01 AM
    Moderator
  • Yes I'm a bit wary of doing a system restore as it might roll back a lot of things on my system...

    I did install SP1 but I think it was a few weeks after before it started complaining about not being genuine.

    I have another working Windows 7 machine, could I copy the .dll file over from that and see if it fixes it?

    Tuesday, May 31, 2011 10:18 AM
  • "Thomas Orger" wrote in message news:e2c40170-a920-47bf-bb89-df2c3d6a0ef3...

    Yes I'm a bit wary of doing a system restore as it might roll back a lot of things on my system...

    I did install SP1 but I think it was a few weeks after before it started complaining about not being genuine.

    I have another working Windows 7 machine, could I copy the .dll file over from that and see if it fixes it?


    I doubt very much that it would - as I say, if the file itself were damaged, it would be reported earlier as well. It may be worth a go, though.
     
    OK - that rules out SP1 as a cause then - you would probably have started getting non-genuine messages within 72 hours if it were.
     
    System Restore doesn't normally touch user-data (but backups are always a good idea!), so if you've not installed much in the way of programs since the start of the problem, it could also be worth a go - remember that you'd have to reinstall any updates affected, not only for Windows, but also for all other programs and drivers installed. <nag>This is why it's always best to tackle problems early, rather than leave them festering</nag>
     
    I suspect that we're down to emergency measures here.....
    1) a repair install of Windows - which would entail your removing SP1 (etc. etc.) or finding someone with a Retail copy with SP1 already included and borrowing their disk.
    2) Contact MS support, and see if they can help - it may be free, or it may not, depending on exactly how they work it nowadays.
    Hopefully they'll be able to get you sorted without having to reinstall.
     
    North America: http://support.microsoft.com/contactus/cu_sc_genadv_master?ws=support&ws=support#tab4
     
    Outside North America:
    http://support.microsoft.com/contactus/?ws=support#tab0
     
    Please let us know if  (and how!) MS manage to repair the problem without a repair install of the OS - it would be useful for future reference!

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, May 31, 2011 10:32 AM
    Moderator
  • I contacted MS in the first instance who told me to call MSI (who I didn't bother calling as I suspect they'd just ask me to call Microsoft because it's a Windows issue), but then I went on their support link that you provided and it told me it would cost £46 to speak to someone as I had an OEM copy!!

     

    I'm going to have a look and see if I feel brave enough to system restore, and see if that does anything. It's very frustrating though, as I obviously did something Windows didn't like, but if it would just tell me then I could revert very easily!! Am sat on my desktop PC with Win 7 Professional now just hoping it doesn't decide my legally purchased copy isn't mine anymore!!

    Wednesday, June 1, 2011 7:43 AM
  • "Thomas Orger" wrote in message news:ae10bdc3-5820-4c2d-97a6-c3bebc0ebc8a...

    I contacted MS in the first instance who told me to call MSI (who I didn't bother calling as I suspect they'd just ask me to call Microsoft because it's a Windows issue), but then I went on their support link that you provided and it told me it would cost £46 to speak to someone as I had an OEM copy!!

     

    I'm going to have a look and see if I feel brave enough to system restore, and see if that does anything. It's very frustrating though, as I obviously did something Windows didn't like, but if it would just tell me then I could revert very easily!! Am sat on my desktop PC with Win 7 Professional now just hoping it doesn't decide my legally purchased copy isn't mine anymore!!


    I was afraid that may happen - in the US, WGA support is (I think) free - but it varies by region elsewhere.
    Check in your Event Viewer, and see if you can pin down the exact start of your problem- then have a look for error messages in the previous 3 days to see if anything looks suspicious. If nothing else, doing so will mean that you're not restoring back too far if you go that route!
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, June 1, 2011 8:09 AM
    Moderator