The message NOT GENUINE windows...really? because the software was pre loaded in the laptop purchased from Best Buys?!

All replies

• 

  

  0

  Sign in to vote

  From your MGADiag Report above:

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

   

  1. Click the Start Orb & type in cmd.exe into the search menu.

  2. Right click it and Run as administrator.

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

  4. Wait for the process to finish, once it's done. Reboot the system.

  5. Repost another MGADiag Report.

   

   

  Monday, August 22, 2011 3:24 AM
• 

  

  0

  Sign in to vote

  From your MGADiag Report above:

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

   

  1. Click the Start Orb & type in cmd.exe into the search menu.

  2. Right click it and Run as administrator.

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

  4. Wait for the process to finish, once it's done. Reboot the system.

  5. Repost another MGADiag Report.

  Diagnostic Report (1.9.0027.0):

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

  Windows Validation Data-->

   

  Validation Code: 0x8004FE22

  Cached Online Validation Code: 0x0

  Windows Product Key: *****-*****-2QWT6-HCQXJ-9YQTR

  Windows Product Key Hash: PVjSC5x6njvqunmbCY3lOD7rYDo=

  Windows Product ID: 00359-OEM-8992687-00007

  Windows Product ID Type: 2

  Windows License Type: OEM SLP

  Windows OS version: 6.1.7601.2.00010300.1.0.003

  ID: {A2375B9F-7B40-47A1-950A-739CAC183DBE}(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_rtm.101119-1850

  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\Kristie\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\sppcommdlg.dll[Hr = 0x800b0100]

   

  Other data-->

  Office Details: <GenuineResults><MachineData><UGUID>{A2375B9F-7B40-47A1-950A-739CAC183DBE}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-9YQTR</PKey><PID>00359-OEM-8992687-00007</PID><PIDType>2</PIDType><SID>S-1-5-21-1229871310-1232316378-1066563181</SID><SYSTEM><Manufacturer>ASUSTeK Computer Inc.        </Manufacturer><Model>K52F</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>K52F.210</Version><SMBIOSVersion major="2" minor="6"/><Date>20100830000000.000000+000</Date></BIOS><HWID>F0E53207018400FC</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>_ASUS_</OEMID><OEMTableID>Notebook</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-800007-02-1033-7600.0000-2092009

  Installation ID: 094435508615514490402492502781930836895831638043803176

  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: 9YQTR

  License Status: Licensed

  Remaining Windows rearm count: 3

  Trusted time: 8/22/2011 12:11:08 AM

   

  Windows Activation Technologies-->

  HrOffline: 0x8004FE22

  HrOnline: N/A

  HealthStatus: 0x0000000000004000

  Event Time Stamp: 8:20:2011 17:16

  ActiveX: Registered, Version: 7.1.7600.16395

  Admin Service: Registered, Version: 7.1.7600.16395

  HealthStatus Bitmask Output:

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

   

   

  HWID Data-->

  HWID Hash Current: LgAAAAEAAQABAAEAAAABAAAAAwABAAEAeqgK3HKaABcWVp4EFC8EdkIMcP5cXQ==

   

  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 _ASUS_ Notebook

    FACP _ASUS_ Notebook

    DBGP _ASUS_ Notebook

    HPET _ASUS_ Notebook

    MCFG _ASUS_ Notebook

    ECDT _ASUS_ Notebook

    SLIC _ASUS_ Notebook

    SSDT PmRef CpuPm

   

  The above is generated AFTER following your instructions!

  THANKS!

   

  
  

  ---

  Kristie Jenkins

  Monday, August 22, 2011 4:13 AM
• 

  

  0

  Sign in to vote

  I see the sfc /scannow command wasn't able to fix it.

  Try this -  Do a search for sppcommdlg.dll.mui on the hard drive that Windows 7 is installed on.

  Make a copy of the sppcommdlg.dll.mui file that shows under the directory folder (C:\Windows\winsxs\ given in the search result.

  Replace it with the one found in the (C:\Windows\System32\en-US directory.

   

  Run the sfc /scannow command again. Then reboot & repost another MGADiag Report.

  
  

  Monday, August 22, 2011 5:08 AM
• 

  

  0

  Sign in to vote

  "tb19" wrote in message news:1d587ce4-d6a5-4fee-a39a-4b310e0f3d28...

  I see the sfc /scannow command wasn't able to fix it.

  Try this -  Do a search for sppcommdlg.dll.mui on the hard drive that Windows 7 is installed on.

  Make a copy of the sppcommdlg.dll.mui file that shows under the directory folder (C:\Windows\winsxs\ given in the search result.

  Replace it with the one found in the (C:\Windows\System32\en-US directory.

   

  Run the sfc /scannow command again. Then reboot & repost another MGADiag Report.

  
  

   

   

  Tb19/Kristiejenk

   

  The problem does NOT lie with the .mui file – but with the ..dll file (see the File Scan Data section)

  File Scan Data-->

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

  Since the SFC did not fix the problem, and the error message indicates that the problem is with registration of some sort, it’s likely that the actual problem is in the registry somewhere.

  As such, the best solution would probably be using System Restore to get back to a time when the system was working properly.

   

   

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

  Monday, August 22, 2011 8:26 AM

  Moderator
• 

  

  0

  Sign in to vote

  "Noel D Paton" wrote in message news:8a9e3bc7-07e2-40e0-abc2-3bf21f2739e0...

   

  Tb19/Kristiejenk

   

  The problem does NOT lie with the .mui file – but with the ...dll file (see the File Scan Data section)

  File Scan Data-->

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

  Since the SFC did not fix the problem, and the error message indicates that the problem is with registration of some sort, it’s likely that the actual problem is in the registry somewhere.

  As such, the best solution would probably be using System Restore to get back to a time when the system was working properly.

   

   

  Before you try the  System Restore – please do the following (it may give some idea as to what the actual problem is, if we’re lucky!)

  Create a new System Restore point (just in case something goes wrong – it shouldn’t!, but..)

  then open Regedit (click on Start, type REGEDIT in the Search box, and hit the Enter key – accept the UAC prompt)

   

  Click on Edit in the menu bar, then Find...

  in the box, type SPPCOMMDLG and hit the Find Next button.

  If it finds anything (it doesn’t in my system) highlight the found Key, and Export it – call the export sdlg1.txt

  then hit the F3 Key to continue the search, exporting each found Key along the way (increasing the number in the exported file each time)

  Then close Regedit.

  Then email all the exported files (if any) to me at ngsATcrashfixpcDOTcoDOTuk so that I can see what may be there.

   

  Thanks!

  Open Regedit

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

  Monday, August 22, 2011 11:40 AM

  Moderator
• 

  

  0

  Sign in to vote

  "Noel D Paton" wrote in message news:8a9e3bc7-07e2-40e0-abc2-3bf21f2739e0...

   

  Tb19/Kristiejenk

   

  The problem does NOT lie with the .mui file – but with the ...dll file (see the File Scan Data section)

  File Scan Data-->

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

  Since the SFC did not fix the problem, and the error message indicates that the problem is with registration of some sort, it’s likely that the actual problem is in the registry somewhere.

  As such, the best solution would probably be using System Restore to get back to a time when the system was working properly.

    

   

  Before you try the  System Restore – please do the following (it may give some idea as to what the actual problem is, if we’re lucky!)

  Create a new System Restore point (just in case something goes wrong – it shouldn’t!, but..)

  then open Regedit (click on Start, type REGEDIT in the Search box, and hit the Enter key – accept the UAC prompt)

   

  Click on Edit in the menu bar, then Find...

  in the box, type SPPCOMMDLG and hit the Find Next button.

  If it finds anything (it doesn’t in my system) highlight the found Key, and Export it – call the export sdlg1.txt

  then hit the F3 Key to continue the search, exporting each found Key along the way (increasing the number in the exported file each time)

  Then close Regedit.

  Then email all the exported files (if any) to me at ngsATcrashfixpcDOTcoDOTuk so that I can see what may be there.

   

  Thanks!

  Open Regedit

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

  Thank you BUT Regedit didn't offer anything! Nothing showed up! What next??!!!!!!!!

  ---

  Kristie Jenkins

  Tuesday, August 23, 2011 2:26 AM
• 

  

  0

  Sign in to vote

  "Kristiejenk" wrote in message news:2171c65a-fba0-43ef-a32a-c1e02df889a8...

  Thank you BUT Regedit didn't offer anything! Nothing showed up! What next??!!!!!!!!

  ---

  Kristie Jenkins

   

  Try a System Restore.

  I was hoping that we’d find something in the registry that would account for the problem – but obviously not.

   

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

  • Proposed as answer by Darin Smith MS Tuesday, August 23, 2011 8:10 PM

  Tuesday, August 23, 2011 3:41 AM

  Moderator
• 

  

  0

  Sign in to vote

  "Kristiejenk" wrote in message news:2171c65a-fba0-43ef-a32a-c1e02df889a8...

  Thank you BUT Regedit didn't offer anything! Nothing showed up! What next??!!!!!!!!

  ---

  Kristie Jenkins

   

  Try a System Restore.

  I was hoping that we’d find something in the registry that would account for the problem – but obviously not.

   

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

  Thanks, I will...I did try that last week and went back as far as I could...BUT...:(...here I am!

  ---

  Kristie Jenkins

  Tuesday, August 23, 2011 11:19 PM
• 

  

  0

  Sign in to vote

  "Kristiejenk" wrote in message news:50caa9a1-44e6-43f2-ba8d-9735da4faa78...

  "Kristiejenk" wrote in message news:2171c65a-fba0-43ef-a32a-c1e02df889a8...

  Thank you BUT Regedit didn't offer anything! Nothing showed up! What next??!!!!!!!!

  ---

  Kristie Jenkins

   

  Try a System Restore.

  I was hoping that we’d find something in the registry that would account for the problem – but obviously not.

   

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

  Thanks, I will...I did try that last week and went back as far as I could...BUT...:(...here I am!

  ---

  Kristie Jenkins

   

  Ah – in that case, all I can suggest is that you contact WGA Support. (I’ve tried finding a way to reproduce the problem on my system here, and there’s no easy way to do it)

   

  WGA Support can be found here-

  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

  • Proposed as answer by Noel D PatonModerator Saturday, August 27, 2011 11:14 AM
  • Marked as answer by Darin Smith MS Wednesday, August 31, 2011 8:09 PM

  Tuesday, August 23, 2011 11:25 PM

  Moderator