Windows 7 Advantage error 0xC8000247

Alle besvarelser

• 7. maj 2012 18:45

  Redaktør

   

   
  

  0
  "Ron Perh" wrote in message news:16655702-af65-4fca-ad71-a5f12656b25d...

  my quad core 64 bit PC with a 2tb hard drive
  
  with Windows 7 home premium has this pop up
  
  that shows up 4-5 times a day and says "this
  
  is not a genuine copy of windows ask for
  
  genuine microsoft software." then at the
  
  bottom it says resolve online. so i
  
  downloaded the windows activation update that
  
  it told me to. i ran it and just as its
  
  almost finished it says "update installation
  
  failed. Error information - 0xC8000247." Iran
  
  another dianostic program that checked all
  
  the issues related to this problem (eg
  
  cookies, etc) which said everything was fine.
  
  I have installed hundreds of copies of xp and
  
  never seen anything this insane. Has
  
  microsoft gotten so greedy that its virtually
  
  impossible to install a legitmate copy of Win
  
  ??? I have wasted a lot of time and effort on
  
  what should be a simple installation.
  
  In any event I in wasting a lot of time on
  
  research I found that i HAD TO DUMP THE
  
  STATUS OF MY pc WHICH IS AS FOLLOWS:
  
  Diagnostic Report (1.9.0027.0):
  -----------------------------------------
  Windows Validation Data-->
  
  Validation Code: 0x8004FE21
  Cached Online Validation Code: N/A, hr =
  
  0xc004f012
  Windows Product Key: *****-*****-9JJQW-
  
  T728B-49MCK
  Windows Product Key Hash:
  
  IgqQ3a8/tASKnpHXzBQT+ScViLo=
  Windows Product ID: 00359-OEM-8703773-38574
  Windows Product ID Type: 3
  Windows License Type: OEM System Builder
  Windows OS version:
  
  6.1.7601.2.00010300.1.0.003
  
  
  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-->

  <SYSTEM><Manufacturer>INTEL</Manufacturer><Model>DG43NB</Model></SYSTEM><BIOS><Manufacturer>Intel Corp.</Manufacturer><Version>NBG4310H.86A.0104.2010.0122.1624</Version>

  <SMBIOSVersion major="2" minor="4"/><Date>20100122000000.000000+000</Date></BIOS

  
  
  Licensing Data-->
  Software licensing service version: 6.1.7601.17514
  Name: Windows(R) 7, HomePremium edition
  Description: Windows Operating System -
  
  Windows(R) 7, OEM_COA_NSLP channel
  Partial Product Key: 49MCK
  License Status: Licensed
  Remaining Windows rearm count: 3
  Trusted time: 4/30/2012 10:05:52 AM
  
  Windows Activation Technologies-->
  HrOffline: 0x8004FE21
  
  
  
  OEM Activation 2.0 Data-->
  BIOS valid for OA 2.0: yes, but no SLIC table
  
  
  What should I do to solve this problem??
  
  Thanks
  
   

   

  The problem lies with the file integrity.

  This may simply be caused by a bad set of Intel Rapid Storage Technology drivers -

  Installing the Intel Rapid Storage Drivers

  try downloading and installing them from here -

  http://downloadcenter.intel.com/Detail_Desc.aspx?ProductID=2101&DwnldID=20624

  Once complete, please reboot twice, then post another MGADiag report.

  ---

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

  • Foreslået som svar af Darin Smith MSOwner 7. maj 2012 19:24
  • Fjernet som foreslået som svar af Carey FrischMVP 8. maj 2012 01:26
  • Markeret som svar af Darin Smith MSOwner 8. maj 2012 21:18
  •  
  • Besvar
  • Citer

   
• 8. maj 2012 05:09

   

   
  

  0

  Mr Paton

  I did exactly what you asked above, rebooted twice 

  and the report is below. Maybe its just me but I don't
  
  see what updating the intel raid driver has
  
  to do with licensing?? The PC doesn't have
  
  raid drives anyway?
  
  What happened here is we built a model PC win
  
  7 system for our company to replace all of
  
  our XP systems. This took a lot of effort
  
  since we installed a lot of software apps on
  
  the model win 7 system. All other PC's have
  
  the exact same hardware, so we planned to
  
  clone the model system to each of these PCs
  
  using Win 7 image backup/restore software. We
  
  didn't want to put the license on the model
  
  system until after it was cloned, but we ran
  
  past the 30 day grace period and the license
  
  error message became a real nuisance!! So we
  
  put in the first license in the model system
  
  by necessity. We reasoned that win 7 had a way
  
  to change the license, so it SHOULD WORK BUT
  
  DIDN'T. We have no authentication errors on
  
  our model system, but do on the clone with
  
  the only difference being we changed the
  
  serial number on the clone to another VALID
  
  license!! Because you have apparently
  
  over killed the license process, we are not
  
  sure how to get out of this mess. We
  
  certainly don't want too waste days building
  
  another model system simply because Win 7 has
  
  screwed up authentication system or possibly
  
  backup/restore system does not work properly? Clearly something is
  
  nowhere near user friendly. What do we do!!
  
  We are behind schedule and very close to
  
  scraping the project. We will return the PCs and WIN 7
  
  software until Win 7 gets its act together. We
  
  never had this problem building Win XP
  
  systems.
  
  
  
  Diagnostic Report (1.9.0027.0):
  -----------------------------------------
  Windows Validation Data-->
  
  Validation Code: 0
  Cached Online Validation Code: N/A, hr =
  
  0xc004f012
  Windows Product Key: *****-*****-9JJQW-
  
  T728B-49MCK
  Windows Product Key Hash:
  
  IgqQ3a8/tASKnpHXzBQT+ScViLo=
  Windows Product ID: 00359-OEM-8703773-38574
  Windows Product ID Type: 3
  Windows License Type: OEM System Builder
  Windows OS version:
  
  6.1.7601.2.00010300.1.0.003
  ID: {7E46C585-397A-4AF7-8D84-3D9BF6145536}(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.120305-1505
  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 Standard 2007 - 100 Genuine
  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:\Program Files
  
  (x86)\Mozilla Firefox\firefox.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>
  
  {7E46C585-397A-4AF7-8D84-3D9BF6145536}
  
  </UGUID><Version>1.9.0027.0</Version><OS>6.1.
  
  7601.2.00010300.1.0.003</OS><Architecture>x64
  
  </Architecture><PKey>*****-*****-*****-
  
  *****-49MCK</PKey><PID>00359-OEM-8703773-
  
  38574</PID><PIDType>3</PIDType><SID>S-1-5-21
  
  -3985407528-3907389872-
  
  934000862</SID><SYSTEM><Manufacturer>INTEL</M
  
  anufacturer><Model>DG43NB</Model></SYSTEM><BI
  
  OS><Manufacturer>Intel
  
  Corp.</Manufacturer><Version>NBG4310H.86A.010
  
  4.2010.0122.1624</Version><SMBIOSVersion
  
  major="2"
  
  minor="4"/><Date>20100122000000.000000+000</D
  
  ate></BIOS><HWID>DC643407018400F8</HWID><User
  
  LCID>0409</UserLCID><SystemLCID>0409</SystemL
  
  CID><TimeZone>Pacific Standard Time(GMT-
  
  08:00)
  
  </TimeZone><iJoin>0</iJoin><SBID><stat>3</sta
  
  t><msppid></msppid><name></name><model></mode
  
  l></SBID><OEM/><GANotification/></MachineData
  
  ><Software><Office><Result>100</Result><Produ
  
  cts><Product GUID="{91120000-0012-0000-0000-
  
  0000000FF1CE}"><LegitResult>100</LegitResult>
  
  <Name>Microsoft Office Standard
  
  2007</Name><Ver>12</Ver><Val>4778CC0245EF710<
  
  /Val><Hash>eLKkhTPuBzgwp8l2twBQB1wwrsQ=</Hash
  
  ><Pid>81607-904-2065357-
  
  64186</Pid><PidType>1</PidType></Product></Pr
  
  oducts><Applications><App Id="16"
  
  Version="12" Result="100"/><App Id="18"
  
  Version="12" Result="100"/><App Id="1A"
  
  Version="12" Result="100"/><App Id="1B"
  
  Version="12"
  
  Result="100"/></Applications></Office></Softw
  
  are></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_COA_NSLP channel
  Activation ID: 586bc076-c93d-429a-afe5-
  
  a69fbc644e88
  Application ID: 55c92734-d682-4d71-983e-
  
  d6ec3f16059f
  Extended PID: 00359-00174-037-738574-02-1033
  
  -7601.0000-1212012
  Installation ID:
  
  022145538545181876038241633173836182651944649
  
  852876620
  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: 49MCK
  License Status: Licensed
  Remaining Windows rearm count: 3
  Trusted time: 5/7/2012 9:38:58 PM
  
  Windows Activation Technologies-->
  HrOffline: 0x00000000
  HrOnline: 0x00000000
  HealthStatus: 0x0000000000000000
  Event Time Stamp: 5:6:2012 22:06
  ActiveX: Registered, Version: 7.1.7600.16395
  Admin Service: Registered, Version:
  
  7.1.7600.16395
  HealthStatus Bitmask Output:
  
  
  HWID Data-->
  HWID Hash Current:
  
  MgAAAAIAAwABAAEAAAACAAAAAQABAAEA6GGOk
  
  +7YlMHKzUBT4l8UTzCzYj0arNosTFg=
  
  OEM Activation 1.0 Data-->
  N/A
  
  OEM Activation 2.0 Data-->
  BIOS valid for OA 2.0: yes, but no SLIC table
  Windows marker version: N/A
  OEMID and OEMTableID Consistent: N/A
  BIOS Information:
    ACPI Table Name    OEMID Value    
  
  OEMTableID Value
    APIC            INTEL        
  
  DG43NB
    FACP            INTEL        
  
  DG43NB
    HPET            INTEL         
  
  DG43NB  
    MCFG            INTEL         
  
  DG43NB  
    ASF!            INTEL         
  
  DG43NB
  
  

  • Besvar
  • Citer

   
• 8. maj 2012 07:23

  Redaktør

   

   
  

  0
  "Ron Perh" wrote in message news:b03796f8-7a13-4da7-b08e-1f8a93007446...

  Mr Paton

  I did exactly what you asked above, rebooted twice

  and the report is below. Maybe its just me but I don't
  
  see what updating the intel raid driver has
  
  to do with licensing?? The PC doesn't have
  
  raid drives anyway?
  
  What happened here is we built a model PC win
  
  7 system for our company to replace all of
  
  our XP systems. This took a lot of effort
  
  since we installed a lot of software apps on
  
  the model win 7 system. All other PC's have
  
  the exact same hardware, so we planned to
  
  clone the model system to each of these PCs
  
  using Win 7 image backup/restore software. We
  
  didn't want to put the license on the model
  
  system until after it was cloned, but we ran
  
  past the 30 day grace period and the license
  
  error message became a real nuisance!! So we
  
  put in the first license in the model system
  
  by necessity. We reasoned that win 7 had a way
  
  to change the license, so it SHOULD WORK BUT
  
  DIDN'T. We have no authentication errors on
  
  our model system, but do on the clone with
  
  the only difference being we changed the
  
  serial number on the clone to another VALID
  
  license!! Because you have apparently
  
  over killed the license process, we are not
  
  sure how to get out of this mess. We
  
  certainly don't want too waste days building
  
  another model system simply because Win 7 has
  
  screwed up authentication system or possibly
  
  backup/restore system does not work properly? Clearly something is
  
  nowhere near user friendly. What do we do!!
  
  We are behind schedule and very close to
  
  scraping the project. We will return the PCs and WIN 7
  
  software until Win 7 gets its act together. We
  
  never had this problem building Win XP
  
  systems.
  
  
  
  Diagnostic Report (1.9.0027.0):
  -----------------------------------------
  Windows Validation Data-->
  
  
  
  
  
  

   

  I'm not sure what it does either - but it does fix around 80% of the instances of this problem (which appears to be related to the Cryptographics services). It provides drivers not only for RAID, but also for ordinary hard drive access.

   

  It's fixed your problem anyhow :)

   

  Win 7 is very much more stable than XP - and much more secure - and since XP goes out of support soon, you'd be well-advised to continue with Win7. You'll have to learn the wrinkles sooner or later, and it's better, sooner, or you'll end up having to  make the jump direct to Win8 - which I suspect is going to cause problems in the business market, unless MS do something unexpected.

   

   

   

  ---

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

   
• 8. maj 2012 17:47

   

   
  

  0

  Mr. Paton

  Your fix worked. We can't believe that a driver caused this problem because the clone PC is identical to the master PC, so the drivers should have worked??

  We would have never figured this out without your help. Thank You!!

  We felt that running the driver update wasn't even worth testing until we got your reply. When we attempted to do a WIN 7 update it worked and we haven't had any pop up licensing error messages, so I guess we are good to go. Thanks again!!!

  Ron

  • Besvar
  • Citer

   
• 8. maj 2012 18:11

  Redaktør

   

   
  

  0
  "Ron Perh" wrote in message news:56f76136-1ff2-47f8-b7b9-d26b5c0895ae...

  Mr. Paton

  Your fix worked. We can't believe that a driver caused this problem because the clone PC is identical to the master PC, so the drivers should have worked??

  We would have never figured this out without your help. Thank You!!

  We felt that running the driver update wasn't even worth testing until we got your reply. When we attempted to do a WIN 7 update it worked and we haven't had any pop up licensing error messages, so I guess we are good to go. Thanks again!!!

  Ron

  <chuckle> - Surprised the heck out of me when it worked on a machine that I didn't even think the drivers would install on, first time!

   

  Glad it worked for you.

   

  Good luck.

   

  ---

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