Service Pack 2, Windows update, Software Licensing issues

All Replies

• Tuesday, May 15, 2012 9:38 PM

  Moderator

   

   
  

  1
  "Darkmeow" wrote in message news:fcfe07e7-15aa-4dd5-bec3-e83292de3d85...

  Diagnostic Report (1.9.0027.0):
  -----------------------------------------
  Windows Validation Data-->
  Validation Status: Genuine
  Validation Code: 0
  Cached Online Validation Code: N/A, hr = 0x80070426
  Windows Product Key: *****-*****-67PP7-HBFG7-MK7JP
  Windows Product Key Hash: 3I/wZPJawfdpog2OchDjQl3VcNg=
  Windows Product ID: 89583-OEM-7360014-28834
  Windows Product ID Type: 3
  Windows License Type: OEM System Builder
  Windows OS version: 6.0.6002.2.00010300.1.0.003
  ID: {45159D53-AB1C-4B3A-AAC2-08178C85123D}(1)
  Is Admin: Yes
  TestCab: 0x0
  LegitcheckControl ActiveX: N/A, hr = 0x80070002
  Signed By: N/A, hr = 0x80070002
  Product Name: Windows Vista (TM) Home Premium
  Architecture: 0x00000009
  Build lab: 6002.vistasp2_gdr.101014-0432
  TTS Error: P:20120515123813199
  

  
  
  Other data-->
  SYSTEM><Manufacturer>Micro-Star International</Manufacturer><Model>GX720</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>A1722IG6 V1.0O</Version><SMBIOSVersion major="2" minor="5"/><Date>20081203000000.000000+000</Date></BIOS

  
  
  Licensing Data-->
  Software Licensing service is not running.
  
  
  
  OEM Activation 2.0 Data-->
  BIOS valid for OA 2.0: no, inconsistent OEMID or OEMTableID
  Windows marker version: N/A
  OEMID and OEMTableID Consistent: no
  BIOS Information:
    ACPI Table Name OEMID Value OEMTableID Value
    SLIC 120308 SLIC1150
  
  

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

  Windows Vista Home Premium 64 bit, been trying to install sp2 for vista.  First that failed, and another fix stated to attempt again, and now (after it failed at step 3 for about an hour and gave a black splash screen with white text and a .dll file flashing in there) I cannot use windows update.  When I try to start software licensing to fix THAT issue, I get an error saying it cannot.  0xc004d10a:0xc004d10a  is the error code.  Hoping for help :D

  Now there's a VERY rare beast!  - a P-type TTS error.

  TTS Error: P:20120515123813199

  The only reference I can find is from two years ago

   

  http://social.microsoft.com/Forums/en/genuinevista/thread/7b4f1b37-32a7-4817-b7c5-e66f2580f0d8

   

  See Darin's response there.

   

  Please let us know if you manage to find a solution, or need further assistance - I'd be happy to help!

   

   

  ---

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

  • Marked As Answer by Darin Smith MSOwner Wednesday, May 16, 2012 5:59 PM
  •  
  • Reply
  • Quote

   
• Wednesday, May 16, 2012 12:04 AM

  Moderator

   

   
  

  1
  "Darkmeow" wrote in message news:fcfe07e7-15aa-4dd5-bec3-e83292de3d85...

  Windows Vista Home Premium 64 bit, been trying to install sp2 for vista.  First that failed, and another fix stated to attempt again, and now (after it failed at step 3 for about an hour and gave a black splash screen with white text and a .dll file flashing in there) I cannot use windows update.  When I try to start software licensing to fix THAT issue, I get an error saying it cannot.  0xc004d10a:0xc004d10a  is the error code.  Hoping for help :D

  Also - the following article is worth checking - follow the advice, even if it seems unrelated.

  http://social.microsoft.com/Forums/en-US/genuinevista/thread/e0ad2f27-e743-4e00-b80e-309fc6821ca5

  ---

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

  • Edited by Noel D PatonMicrosoft Community Contributor, Editor Wednesday, May 16, 2012 12:04 AM include link!
  •  
  • Reply
  • Quote

   
• Wednesday, May 16, 2012 4:31 AM

   

   
  

  0
  Did as the page had offered, and after running sfc /scannow I recieved a message that let me know it found corruption in some files but was unable to fix them all.  I haven't yet reboot my computer, but wanted to post each step as I go just to ensure I don't forget important details :D
  • Reply
  • Quote

   
• Wednesday, May 16, 2012 4:54 AM

   

   
  

  0

  I just rebooted, and it would seem my initial problem has been solved in that the Software licensing is now started and listed so.  The bad news is I still have a P type error (I reran the diagnostic tool and am copy-pasta-ing here, again just to keep track of my steps).

  Diagnostic Report (1.9.0027.0):
  -----------------------------------------
  Windows Validation Data-->
  Validation Status: Genuine
  Validation Code: 0
  Cached Online Validation Code: N/A, hr = 0xc004f012
  Windows Product Key: *****-*****-67PP7-HBFG7-MK7JP
  Windows Product Key Hash: 3I/wZPJawfdpog2OchDjQl3VcNg=
  Windows Product ID: 89583-OEM-7360014-28834
  Windows Product ID Type: 3
  Windows License Type: OEM System Builder
  Windows OS version: 6.0.6001.2.00010300.1.0.003
  ID: {45159D53-AB1C-4B3A-AAC2-08178C85123D}(3)
  Is Admin: Yes
  TestCab: 0x0
  LegitcheckControl ActiveX: N/A, hr = 0x80070002
  Signed By: N/A, hr = 0x80070002
  Product Name: Windows Vista (TM) Home Premium
  Architecture: 0x00000009
  Build lab: 6001.vistasp1_gdr.101014-0432
  TTS Error: P:20120515123813199
  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:\Program Files (x86)\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>{45159D53-AB1C-4B3A-AAC2-08178C85123D}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6001.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-MK7JP</PKey><PID>89583-OEM-7360014-28834</PID><PIDType>3</PIDType><SID>S-1-5-21-148597169-110654915-1674424678</SID><SYSTEM><Manufacturer>Micro-Star International</Manufacturer><Model>GX720</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>A1722IG6 V1.0O</Version><SMBIOSVersion major="2" minor="5"/><Date>20081203000000.000000+000</Date></BIOS><HWID>8A303507018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>120308</OEMID><OEMTableID>SLIC1150</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.0.6001.18000
  Name: Windows(TM) Vista, HomePremium edition
  Description: Windows Operating System - Vista, OEM_COA_NSLP channel
  Activation ID: f3acdd3c-119a-4932-a3d7-0b6f33a1dca9
  Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
  Extended PID: 89583-00146-600-128834-02-1033-6001.0000-2242009
  Installation ID: 011361170793531086653465084550611600648231755494895430
  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: MK7JP
  License Status: Licensed
  
  Windows Activation Technologies-->
  N/A
  
  HWID Data-->
  HWID Hash Current: OAAAAAEAAQABAAEAAwACAAAABAABAAEA6GGGCTj9isQA3tJael0Y4vL01pvObORbGpmsVmpDTFg=
  
  OEM Activation 1.0 Data-->
  N/A
  
  OEM Activation 2.0 Data-->
  BIOS valid for OA 2.0: no, inconsistent OEMID or OEMTableID
  Windows marker version: N/A
  OEMID and OEMTableID Consistent: no
  BIOS Information: 
    ACPI Table Name OEMID Value OEMTableID Value
    APIC 120308 APIC1150
    FACP 120308 FACP1150
    HPET 120308 OEMHPET 
    MCFG 120308 OEMMCFG 
    SLIC 120308 SLIC1150
    OEMB 120308 OEMB1150
    ASF! LEGEND I865PASF
    GSCI 120308 GMCHSCI 
    SSDT PmRef CpuPm4
  
  

  I will now be heading back to follow up with the other 2 methods listed, and then referring to the bottom article posted.

  • Reply
  • Quote

   
• Wednesday, May 16, 2012 5:05 AM

   

   
  

  0

  Alright.  So this is the last step I'm at along with any lasting pertinent information.

  • I fixed my issue with Windows Update, along with SVC being able to start through following directions as posted (super thank you on that note :D), TTS error still exists and unsure of how to approach it in any way
  • The origination of the discovery of this issue was attempting to install Diablo 3 (newer video game released recently), error said Operating System was outdated
  • Following forum post online as others advised, attempted to install service pack 2 for vista 64 bit, left computer and when I returned I got a black splash screen with a .dll file extension listed in almost CMD prompt fashion (the flashing text was positioned in the middle of my screen, in no particular form of organization).  I cold shut off my CPU after waiting about 15 minutes with the flashing .dll file (I think it was .dll) not changing, and when restarted the welcome splash screen stated installing part 3 of 3, stayed at 0% a while and then when computer finished booting (turned on and off during startup a couple times) finally logged in and got the notice that it did not install correctly.  I'm unsure of why this is, but I'm going to attempt to install service pack 2 again and see if the results differ from the last time.
  • [EDIT]  This PC had a virus on it not too long ago that was semi-serious (commonly known as 'scare ware'), and I had to install half a dozen anti virus/malware programs to fix the issue.  I had to unhide files and run something called 'rkiller' if you are familiar.  Unsure if this information is pertinent, but I figured it was the last thing I can remember that might affect this situation.  (This is not quite as detailed as every process I followed to remove it, but about as detailed as I imagine it needs to be.

  
  

  • Edited by Darkmeow Wednesday, May 16, 2012 5:07 AM (added information from previous events)
  •  
  • Reply
  • Quote

   
• Wednesday, May 16, 2012 8:35 AM

  Moderator

   

   
  

  1
  "Darkmeow" wrote in message news:2f790a16-ff37-4520-9f98-44de59a7bb6f...

  I just rebooted, and it would seem my initial problem has been solved in that the Software licensing is now started and listed so.  The bad news is I still have a P type error (I reran the diagnostic tool and am copy-pasta-ing here, again just to keep track of my steps).

  Diagnostic Report (1.9.0027.0):
  -----------------------------------------
  Windows Validation Data-->
  Validation Status: Genuine
  Validation Code: 0
  Cached Online Validation Code: N/A, hr = 0xc004f012
  Windows Product Key: *****-*****-67PP7-HBFG7-MK7JP
  Windows Product Key Hash: 3I/wZPJawfdpog2OchDjQl3VcNg=
  Windows Product ID: 89583-OEM-7360014-28834
  Windows Product ID Type: 3
  Windows License Type: OEM System Builder
  Windows OS version: 6.0.6001.2.00010300.1.0.003
  ID: {45159D53-AB1C-4B3A-AAC2-08178C85123D}(3)
  Is Admin: Yes
  TestCab: 0x0
  LegitcheckControl ActiveX: N/A, hr = 0x80070002
  Signed By: N/A, hr = 0x80070002
  Product Name: Windows Vista (TM) Home Premium
  Architecture: 0x00000009
  Build lab: 6001.vistasp1_gdr.101014-0432
  TTS Error: P:20120515123813199
  
  
  

  I will now be heading back to follow up with the other 2 methods listed, and then referring to the bottom article posted.

  The good news is that your service has started, and your system appears to be activated fine.

  The better news is that the fact that the timestamp on the TTS error hasn't changed - therefore the problem has not been detected again. (one day I'll find out how to clear the error to confirm this!)

   

  It does sound as if your problem may have originated either with the virus infection, or your clean-up attempts.

   

   

  ---

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

   
• Wednesday, May 16, 2012 5:59 PM

  Owner

   

   
  

  1

  Noel is correct, that TTS error code will stay even when the issue is resolved. So as long as the time stamp doesn't change (and you are no longer getting any Non-Genuine errors) the issue is resolved.

  I'm glad we could help with such a rare issue!

  Thanks,

  ---

  Darin MS

  • Reply
  • Quote

   
• Wednesday, May 16, 2012 11:36 PM

   

   
  

  0
  Yes, the issue was indeed resolved.  As far as installing service pack 2, I still have a corrupt .DLL after running Chkdsk and the install hangs with a common error code.  Decided to just backup my drivers and do a factory restore to solve the issue, because fiddling with .dlls usually ends up with tons of wasted hours T-T  Thanks again though guys!
  • Reply
  • Quote

   
• Thursday, May 17, 2012 7:12 AM

  Moderator

   

   
  

  0
  "Darkmeow" wrote in message news:83bc0f5e-bb3d-4157-9207-54ba1e81c182...

  Yes, the issue was indeed resolved.  As far as installing service pack 2, I still have a corrupt .DLL after running Chkdsk and the install hangs with a common error code.  Decided to just backup my drivers and do a factory restore to solve the issue, because fiddling with .dlls usually ends up with tons of wasted hours T-T  Thanks again though guys!

   

  Often, the CheckSUR tool can repair such entries - http://support.microsoft.com/kb/947821 - and it's a lot quicker than a reinstall!

  ---

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