locked
Windows 7 64-bit not Genuine after new hard drive and Windows 7 System Image RRS feed

  • Question

  • Hi I have a new 750G hard drive to replace a 640G hard drive in my laptop. I tried to clone the drive with no success using Acronis.  This failed the Genuine test after completion.   So I decided to try the Microsoft official version for restoring a computer.  Well I still get a "not genuine" statement.

    What I did was create a system Image from the Control panel screen.  I backed this up to my windows home server.  I then created a Repair Disk for Windows 7 64-bit.  I put in the new hard drive, added a network driver from flash drive, found the system image and had windows format the drive and load the image, my intent was to later come back and resize the partitions using Windows disk tools.

    Anyway - I did the above and then a validate and low and behold - NOT GENUINE!!!  This is very frustrating.  Any help is welcomed.

    Diagnostic Report (1.9.0027.0):

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

    Windows Validation Data-->

     

    Validation Code: 0x8004FE21

    Cached Online Validation Code: 0x0

    Windows Product Key: *****-*****-MV8MH-98QJM-24367

    Windows Product Key Hash: wgci5Gdejx4esg7++zTOe3LWF+4=

    Windows Product ID: 55041-OEM-8992671-00437

    Windows Product ID Type: 2

    Windows License Type: OEM SLP

    Windows OS version: 6.1.7601.2.00010100.1.0.048

    ID: {6B6FFD17-E51C-4B14-8C4B-7143D24B5433}(3)

    Is Admin: Yes

    TestCab: 0x0

    LegitcheckControl ActiveX: N/A, hr = 0x80070002

    Signed By: N/A, hr = 0x80070002

    Product Name: Windows 7 Professional

    Architecture: 0x00000009

    Build lab: 7601.win7sp1_gdr.110622-1506

    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: 100 Genuine

    Microsoft Office Enterprise 2007 - 100 Genuine

    2007 Microsoft Office system - 100 Genuine

    Microsoft Office Project Standard 2007 - 100 Genuine

    Microsoft Office Visio Professional 2007 - 100 Genuine

    OGA Version: N/A, 0x80070002

    Signed By: N/A, hr = 0x80070002

    Office Diagnostics: 77F760FE-153-80070002_7E90FEE8-175-80070002_77F760FE-153-80070002_7E90FEE8-175-80070002_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_B4D0AA8B-920-80070057

     

    Browser Data-->

    Proxy settings: N/A

    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)

    Default Browser: C:\Users\Jerry\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-->

    File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[7.1.7600.16395], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\wat\watux.exe[7.1.7600.16395], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\sppobjs.dll[6.1.7601.17514], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\sppc.dll[6.1.7601.17514], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\sppcext.dll[6.1.7600.16385], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\sppwinob.dll[6.1.7601.17514], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\slc.dll[6.1.7600.16385], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\slcext.dll[6.1.7600.16385], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\sppuinotify.dll[6.1.7600.16385], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\slui.exe[6.1.7601.17514], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\sppcomapi.dll[6.1.7601.17514], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\sppcommdlg.dll[6.1.7600.16385], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\sppsvc.exe[6.1.7601.17514], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\drivers\spsys.sys[6.1.7127.0], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\drivers\spldr.sys[6.1.7127.0], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7601.17514], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\user32.dll[6.1.7601.17514], Hr = 0x800b0100

     

    Other data-->

    Office Details: <GenuineResults><MachineData><UGUID>{6B6FFD17-E51C-4B14-8C4B-7143D24B5433}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-24367</PKey><PID>55041-OEM-8992671-00437</PID><PIDType>2</PIDType><SID>S-1-5-21-2849940305-3255880196-3748733037</SID><SYSTEM><Manufacturer>LENOVO</Manufacturer><Model>2516CTO</Model></SYSTEM><BIOS><Manufacturer>LENOVO</Manufacturer><Version>6IET49WW (1.09 )</Version><SMBIOSVersion major="2" minor="6"/><Date>20100107000000.000000+000</Date></BIOS><HWID>F1280A00018400FC</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>LENOVO</OEMID><OEMTableID>TP-6I   </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>9E4C20855E116D4</Val><Hash>Z0vGNB+mJUXFXxCB4E2zzimbf4I=</Hash><Pid>81599-874-6114612-65076</Pid><PidType>1</PidType></Product><Product GUID="{91120000-0031-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>2007 Microsoft Office system</Name><Ver>12</Ver><PidType>19</PidType></Product><Product GUID="{91120000-003A-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Project Standard 2007</Name><Ver>12</Ver><Val>6696CB4E20B96CE</Val><Hash>xFpbMRE7GRLUTWPtXavjR/dfbgE=</Hash><Pid>84888-871-3556054-63276</Pid><PidType>1</PidType></Product><Product GUID="{91120000-0051-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Visio Professional 2007</Name><Ver>12</Ver><Val>4DF24E03D8EFECE</Val><Hash>e4hx+MGZb+xLKMt2O3tdLB5Si5I=</Hash><Pid>84890-871-3549536-63811</Pid><PidType>1</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"/><App Id="3A" Version="12" Result="100"/><App Id="44" Version="12" Result="100"/><App Id="53" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/><App Id="BA" Version="12" Result="100"/></Applications></Office></Software></GenuineResults>  

     

    Spsys.log Content: 0x80070002

     

    Licensing Data-->

    Software licensing service version: 6.1.7601.17514

     

    Name: Windows(R) 7, Professional edition

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

    Activation ID: 50e329f7-a5fa-46b2-85fd-f224e5da7764

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

    Extended PID: 00371-00178-926-700437-02-1033-7600.0000-2062009

    Installation ID: 017553786494519276104086871495099871505313431500902880

    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: 24367

    License Status: Licensed

    Remaining Windows rearm count: 3

    Trusted time: 10/11/2011 9:16:40 AM

     

    Windows Activation Technologies-->

    HrOffline: 0x8004FE21

    HrOnline: N/A

    HealthStatus: 0x000000000001EFF0

    Event Time Stamp: 10:11:2011 08:51

    ActiveX: Registered, Version: 7.1.7600.16395

    Admin Service: Registered, Version: 7.1.7600.16395

    HealthStatus Bitmask Output:

    Tampered File: %systemroot%\system32\sppobjs.dll

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

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

    Tampered File: %systemroot%\system32\sppwinob.dll

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

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

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

    Tampered File: %systemroot%\system32\slui.exe|slui.exe.mui|COM Registration

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

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

    Tampered File: %systemroot%\system32\sppsvc.exe|sppsvc.exe.mui

    Tampered File: %systemroot%\system32\drivers\spsys.sys

     

     

    HWID Data-->

    HWID Hash Current: MAAAAAAAAgABAAEAAAABAAAABAABAAEA6GF6FB7edK5YsxDiBu76HkJ+puxOsVxd

     

    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 LENOVO TP-6I   

      FACP LENOVO TP-6I   

      HPET LENOVO TP-6I   

      BOOT LENOVO TP-6I   

      MCFG LENOVO TP-6I   

      SSDT LENOVO TP-6I   

      ECDT LENOVO TP-6I   

      ASF! LENOVO TP-6I   

      SLIC LENOVO TP-6I   

      SSDT LENOVO TP-6I   

      TCPA PTL CRESTLN

      SSDT LENOVO TP-6I   

      SSDT LENOVO TP-6I   

      SSDT LENOVO TP-6I

     

     

     

    Tuesday, October 11, 2011 1:19 PM

Answers

  • BGEggsperienced has unmarked 'Propose as Answer' for Noel's second post but has not replied to the thread to explain what the results of Noel's steps were. 

    At this point (7 days since last post) I assumed the issue has been resolved but not from any suggestions given in this thread.

     

    Thank you,


    Darin MS
    • Marked as answer by Darin Smith MS Tuesday, October 18, 2011 9:36 PM
    Tuesday, October 18, 2011 9:36 PM

All replies

  • "BGEggsperienced" wrote in message news:af9b9d59-ce0e-4e68-a1db-397ec4c331e0...

    Hi I have a new 750G hard drive to replace a 640G hard drive in my laptop. I tried to clone the drive with no success using Acronis.  This failed the Genuine test after completion.   So I decided to try the Microsoft official version for restoring a computer.  Well I still get a "not genuine" statement.

    What I did was create a system Image from the Control panel screen.  I backed this up to my windows home server.  I then created a Repair Disk for Windows 7 64-bit.  I put in the new hard drive, added a network driver from flash drive, found the system image and had windows format the drive and load the image, my intent was to later come back and resize the partitions using Windows disk tools.

    Anyway - I did the above and then a validate and low and behold - NOT GENUINE!!!  This is very frustrating.  Any help is welcomed.

    Diagnostic Report (1.9.0027.0):

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

    Windows Validation Data-->

     

    Validation Code: 0x8004FE21

    Cached Online Validation Code: 0x0

    Windows Product Key: *****-*****-MV8MH-98QJM-24367

    Windows Product Key Hash: wgci5Gdejx4esg7++zTOe3LWF+4=

    Windows Product ID: 55041-OEM-8992671-00437

    Windows Product ID Type: 2

    Windows License Type: OEM SLP

    Windows OS version: 6.1.7601.2.00010100.1.0.048

     

     

    File Scan Data-->

    File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[7.1.7600.16395], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\wat\watux.exe[7.1.7600.16395], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\sppobjs.dll[6.1.7601.17514], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\sppc.dll[6.1.7601.17514], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\sppcext.dll[6.1.7600.16385], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\sppwinob.dll[6.1.7601.17514], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\slc.dll[6.1.7600.16385], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\slcext.dll[6.1.7600.16385], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\sppuinotify.dll[6.1.7600.16385], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\slui.exe[6.1.7601.17514], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\sppcomapi.dll[6.1.7601.17514], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\sppcommdlg.dll[6.1.7600.16385], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\sppsvc.exe[6.1.7601.17514], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\drivers\spsys.sys[6.1.7127.0], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\drivers\spldr.sys[6.1.7127.0], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7601.17514], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\user32.dll[6.1.7601.17514], Hr = 0x800b0100

     

     
    Have you  restored your machine from a backup image – possibly using Acronis software?
     
    This appears to be the cause of many problems with this exact set of errors – but we have yet to identify any easy way to repair the install, other than a repair installation of the OS (which is not possible using Recovery disks).
    If you’re in no hurry for a fix, I’d be happy to work with you on this – but the quick solution is the repair install using Retail disks.
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, October 11, 2011 1:56 PM
    Moderator
  • "BGEggsperienced" wrote in message news:af9b9d59-ce0e-4e68-a1db-397ec4c331e0...

    Hi I have a new 750G hard drive to replace a 640G hard drive in my laptop. I tried to clone the drive with no success using Acronis.  This failed the Genuine test after completion.   So I decided to try the Microsoft official version for restoring a computer.  Well I still get a "not genuine" statement.

    What I did was create a system Image from the Control panel screen.  I backed this up to my windows home server.  I then created a Repair Disk for Windows 7 64-bit.  I put in the new hard drive, added a network driver from flash drive, found the system image and had windows format the drive and load the image, my intent was to later come back and resize the partitions using Windows disk tools.

    Anyway - I did the above and then a validate and low and behold - NOT GENUINE!!!  This is very frustrating.  Any help is welcomed.

     

     

    Let me try that again :)
     
    I suspect that the problem arises because of the partitioning of the hard drive – and that something in the restored image is reacting badly to a missing Recovery partition that was present in the original HD.
    This makes it difficult to simulate in Virtual machines – which makes it correspondingly difficult to properly identify the errors.
    If you want to work on it, it would probably be best  to do it off-forum by email exchange.
    If you want to give it a go, please email me at ngsSTcrashfixpcDOTcoDOTuk (make appropriate changes) and we’ll take it from there.
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Proposed as answer by Darin Smith MS Tuesday, October 11, 2011 9:43 PM
    • Unproposed as answer by BGEggsperienced Wednesday, October 12, 2011 3:17 AM
    Tuesday, October 11, 2011 2:04 PM
    Moderator
  • Once the image is problematic the best course is probably to use the recovery software from the manufacturer to recover the computer to factory condition on the new drive and then restore your files and settings and then install your programs.  That may be the only way to continue to use the OEM SLP license. 
    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Tuesday, October 11, 2011 2:12 PM
    Answerer
  • "Cbarnhorst" wrote in message news:b4f1e91b-0a37-4d31-bf30-e33a66cb42e0...
    Once the image is problematic the best course is probably to use the recovery software from the manufacturer to recover the computer to factory condition on the new drive and then restore your files and settings and then install your programs.  That may be the only way to continue to use the OEM SLP license. 
    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
     
    I don’t believe the Key type is germane to the problem here – or that changing the Key to the COA would either obviate the problem or cure it. (I could be wrong – >90% of the instances that I recall have been OEM_SLP Keys.... maybe I should check that!)
     
    Whatever the cause, it’s too common a problem to be ignored, and I really would like to find a cure, as well as a preventive, as in all too many cases the backup is the only available data, after HD crashes or accidental data-loss.
     
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, October 11, 2011 2:34 PM
    Moderator
  • I didn't propose using the COA key.  I proposed using the SLP key (by implication) by using the recovery software. 

    Common problem or not, if your analysis of the problem as being caused by the image transfer process is right (I have no reason to doubt it) then the resolution is far beyond repairing the sp files because who knows what other files are faulty.  Once the integrity of the system is in question reinstallation is the safest.  That was my thinking.

    If you think the issue is exacerbated by differences in the old and new hdd structures (recovery partitions) then we cannot recommend anything that would "repair" it.  However, one problem coming into focus is the transfer from hdds to ssds.  Few users think to add that detail to their problem descriptions so maybe we should be asking now.  Certainly that drive geometry is very different and image transfers in such scenarios do have a history of failure.  However, I suspect that we don't see the problem much here because other, more serious issues arise and I would think are usually surfaced in such places as the hardware forums.


    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.

    Tuesday, October 11, 2011 2:51 PM
    Answerer
  • "Cbarnhorst" wrote in message news:d2b3aad4-6c5f-46c3-9cfa-3ea9c68869dd...

    I didn't propose using the COA key.  I proposed using the SLP key (by implication) by using the recovery software.

    Common problem or not, if your analysis of the problem as being caused by the image transfer process is right (I have no reason to doubt it) then the resolution is far beyond repairing the sp files because who knows what other files are faulty.  Once the integrity of the system is in question reinstallation is the safest.  That was my thinking.

    If you think the issue is exacerbated by differences in the old and new hdd structures (recovery partitions) then we cannot recommend anything that would "repair" it.  However, one problem coming into focus is the transfer from hdds to ssds.  Few users think to add that detail to their problem descriptions so maybe we should be asking now.  Certainly that drive geometry is very different and image transfers in such scenarios do have a history of failure.  However, I suspect that we don't see the problem much here because other, more serious issues arise and I would think are usually surfaced in such places as the hardware forums.


    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.

     
     
    I really think that possibly as little as one entry in the registry may be the problem – which leads to the set of files being mis-permissioned. The problem is trying to work out where to start the hunt for Red October :)
     
    If we can find that, then an instant cure  is possible, and it’s possible to find a preventive.
    My problem is simply the ability to reproduce the problem in the first place – now that BGEggsperienced has stated that he gets the problem even with the Windows7 Backup, a way is open for me to try testing to see what I can find.
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, October 11, 2011 3:20 PM
    Moderator
  • OT, did you get the Xmas gift?  Do I need to resend?
    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Tuesday, October 11, 2011 3:58 PM
    Answerer
  • BGEggsperienced has unmarked 'Propose as Answer' for Noel's second post but has not replied to the thread to explain what the results of Noel's steps were. 

    At this point (7 days since last post) I assumed the issue has been resolved but not from any suggestions given in this thread.

     

    Thank you,


    Darin MS
    • Marked as answer by Darin Smith MS Tuesday, October 18, 2011 9:36 PM
    Tuesday, October 18, 2011 9:36 PM
  • "Darin Smith MS" wrote in message news:cbe8ccc5-4148-441f-be2d-b02d29cc40c7...

    BGEggsperienced has unmarked 'Propose as Answer' for Noel's second post but has not replied to the thread to explain what the results of Noel's steps were.

    At this point (7 days since last post) I assumed the issue has been resolved but not from any suggestions given in this thread.

     

    Thank you,


    Darin MS
     
     
    As far as I am aware, we are awaiting input from MS before attempting further repairs.
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, October 18, 2011 9:46 PM
    Moderator
  • I had a similar problem.  (See my post at http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_install/message-that-windows-is-not-genuine-update-wont/f7592722-38c9-43ed-9b2b-2e8d8f8f0d5a.)  I made my system image using Windows.

    I tried something I found on a thread that seems to have fixed my problem. I found it on this thread: http://social.technet.microsoft.com/Forums/en-US/w7itproperf/thread/3b716d4c-fb5f-411b-9aee-38af1c529336

    and I used Humprey's solution, which was to update the Intel Rapid Storage Technology Driver. It is a simple download from http://h10025.www1.hp.com/ewfrf/wc/document?docname=c02219204&cc=nl&lc=en&dlc=en&product.

     

    I saw from other writers that it worked for people who didn't have HPs and for people whose hard drives were less than 700GB.

     

    This fixed everything for me, the message about Windows not being genuine and the problem of not being able to update. The only thing it didn't fix was my Toshiba BIOS recognition by the "Health Monitor", but I found another thread for that.

     

    I did not have to re-install Windows or re-enter the product key. Just downloaded the updated driver for Intel. I am not a technician, so I don't know why this worked but it did.

    Wednesday, October 19, 2011 5:21 PM
  • "lassieowl" wrote in message news:23a9a34c-f41d-46f3-a2db-d8a8d2d2f897...
    IIRC, The OP has already tried that fix and it did not work.
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, October 19, 2011 5:29 PM
    Moderator