Vista Validation Error

All replies

• 

  

  0

  Sign in to vote

  I was finally able to run "slui.exe 4" and get the Call activation Window. Unfortunately, the number listed was to the HP Un-Help Desk in India (or Pakistan. Couldn't determine the accent). They had no knowelege of this error and wanted $59 to take a shot at it. I said "No thanks". How do I talk to someone at Microsoft (doesn't have to be Bill...)?

  • Proposed as answer by darrellddd Sunday, March 15, 2009 11:54 PM

  Sunday, March 15, 2009 9:58 PM
• 

  

  0

  Sign in to vote

  as stated in another thread on here--
  1) Open Notepad
  2) Copy the text (in the below box) and paste it into the notepad:

  Windows Registry Editor Version 5.00

  [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\slsvc]

  "DisplayName"="@%SystemRoot%\\system32\\SLsvc.exe,-101"

  "Group"="ProfSvc_Group"

  "ImagePath"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\

  74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,53,\

  00,4c,00,73,00,76,00,63,00,2e,00,65,00,78,00,65,00,00,00

  "Description"="@%SystemRoot%\\system32\\SLsvc.exe,-100"

  "ObjectName"="NT AUTHORITY\\NetworkService"

  "ErrorControl"=dword:00000001

  "Start"=dword:00000002

  "Type"=dword:00000010

  "DependOnService"=hex(7):52,00,70,00,63,00,53,00,73,00,00,00,00,00

  "ServiceSidType"=dword:00000001

  "RequiredPrivileges"=hex(7):53,00,65,00,41,00,75,00,64,00,69,00,74,00,50,00,72,\

  00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,43,00,68,00,\

  61,00,6e,00,67,00,65,00,4e,00,6f,00,74,00,69,00,66,00,79,00,50,00,72,00,69,\

  00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,43,00,72,00,65,00,\

  61,00,74,00,65,00,47,00,6c,00,6f,00,62,00,61,00,6c,00,50,00,72,00,69,00,76,\

  00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,49,00,6d,00,70,00,65,00,\

  72,00,73,00,6f,00,6e,00,61,00,74,00,65,00,50,00,72,00,69,00,76,00,69,00,6c,\

  00,65,00,67,00,65,00,00,00,00,00

  3) In Notepad, click ‘File’ then select ‘Save As’
  4) In the ‘Save As’ window, select ‘Desktop’ as the location to save to.
  5) Click the ‘Save as Type’ dropdown menu and select ‘All File(*.*)’
  6) In the ‘File Name:’ field, type: slsvc_reg.reg
  7) Click the ‘Save’ button
  8) The file should now be on your desktop, double-click it
  9) Reboot
  
  

  Sunday, March 15, 2009 11:55 PM
• 

  

  0

  Sign in to vote

  Hello Thaugh,
  
    You would normally be correct, usually the error 0x80070426 means 'Software Licensing Service has stopped' issue. 
  
    But in your case, The line in your Diagnostic Report
  
  Online Validation Code: 0x80070426
  
  combined with
  
  File Scan Data-->
  File Mismatch: C:\Windows\system32\Slsvc.exe[6.0.6000.16509]
  File Mismatch: C:\Windows\system32\slc.dll[6.0.6000.16509]
  
  

  means that the files slsvc.exe and slc.dll have been Tampered, Modified or has become Corrupt. Vista see this as an attack to bypass it's Licensing security.

  
  To resolve the issue, you need to either repair or replace the file with a known-good one (of the proper file version)

  First try repairing Windows using System Restore:

  1)    Reboot Vista into Safe Mode

  2)    Go to Control Panel

  3)    On the left hand side of the Control Panel window, Click on "Classic View"

  4)    Double-click "Backup and Restore Center"

  5)    On the left hand side of the window, click "Repair Windows using system restore"

  6)    Select "Choose Different Restore Point", Put a check in the box that says "Show restore points older than 5 days", select the restore point that corresponds to the date Before you first noticed the issue.

  7)    Click the "Next" button.

  8)    Reboot back into Normal mode

  9)    Vista should no longer be in Reduced Functionality mode

   

  If that doesn't work, we'll try doing a System Scan. The scan will look for bad Vista files and will attempt to repair them, if possible.

  1)    Login to Vista in Normal Mode (not safe mode)

  2)    Launch an Internet Browser

  3)    Type: %windir%\system32\ in the browser's address field

  4)    Scroll down till you find the file cmd.exe

  5)    Right-click the file and select 'Run as Administrator'

  6)    In the CMD window, type: sfc /scannow

  7)    Reboot twice and see if that resolves the issue.

  If neither of these sets of steps resolves the issue, my only other suggestions would be either to contact Vista support at http://support.microsoft.com or reinstall Vista.

   Thank you,
  Darin MS

  ---

  Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please click the "Post was Helpful" button for that post. This will help us showcase the threads that best help our customers.

  • Marked as answer by Darin Smith MS Monday, March 16, 2009 10:44 PM

  Monday, March 16, 2009 10:43 PM
• 

  

  0

  Sign in to vote

   

  Diagnostic Report (1.9.0006.1):
  -----------------------------------------
  WGA Data-->
  Validation Status: Genuine
  Validation Code: 0
  Online Validation Code: 0x0
  Cached Validation Code: N/A, hr = 0x80004005
  Windows Product Key: *****-*****-GD2PK-BD3R2-44MV3
  Windows Product Key Hash: f7FPE6g/CLFmnJ4E6GbEU9Xn1sA=
  Windows Product ID: 89572-OEM-7332166-00021
  Windows Product ID Type: 2
  Windows License Type: OEM SLP
  Windows OS version: 6.0.6000.2.00010300.0.0.002
  ID: {31820DEC-54F9-4711-8345-625399ABB6F8}(1)
  Is Admin: Yes
  TestCab: 0x0
  WGA Version: Registered, 1.7.69.2
  Signed By: Microsoft
  Product Name: Windows Vista (TM) Home Basic
  Architecture: 0x00000000
  Build lab: 6000.vista_gdr.071009-1548
  TTS Error: M:20081015032443877-
  Validation Diagnostic:
  Resolution Status: N/A

  WgaER Data-->
  ThreatID(s): N/A, hr = 0x80070002
  Version: N/A, hr = 0x80070002

  WGA 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
  WGATray.exe Signed By: N/A, hr = 0x80070002
  OGAAddin.dll Signed By: N/A, hr = 0x80070002

  OGA Data-->
  Office Status: 100 Genuine
  Microsoft Office Professional Edition 2003 - 100 Genuine
  Microsoft Office Visio Professional 2003 - 100 Genuine
  OGA Version: N/A, 0x80070002
  Signed By: N/A, hr = 0x80070002
  Office Diagnostics: B4D0AA8B-604-645_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 7.0; Win32)
  Default Browser: C:\Program Files\Internet Explorer\IEXPLORE.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>{31820DEC-54F9-4711-8345-625399ABB6F8}</UGUID><Version>1.9.0006.1</Version><OS>6.0.6000.2.00010300.0.0.002</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-44MV3</PKey><PID>89572-OEM-7332166-00021</PID><PIDType>2</PIDType><SID>S-1-5-21-2618409392-323304967-228010247</SID><SYSTEM><Manufacturer>Compaq-Presario</Manufacturer><Model>RX896AA-ABA SR5030NX</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>5.12</Version><SMBIOSVersion major="2" minor="4"/><Date>20070418000000.000000+000</Date></BIOS><HWID>DE323507018400E6</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>HPQOEM</OEMID><OEMTableID>SLIC-CPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90110409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office Professional Edition 2003</Name><Ver>11</Ver><Val>63416B9C13D500</Val><Hash>8h9aRoYuJC0CBcBYug7nNRKicww=</Hash><Pid>73931-640-0541236-57605</Pid><PidType>14</PidType></Product><Product GUID="{90510409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office Visio Professional 2003</Name><Ver>11</Ver><Val>B0E2A0DFCDD2D00</Val><Hash>/S5rXV6tLsXH5hTasCxHuLfQe4s=</Hash><Pid>72085-640-1034042-55147</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="11" Result="100"/><App Id="16" Version="11" Result="100"/><App Id="18" Version="11" Result="100"/><App Id="19" Version="11" Result="100"/><App Id="1A" Version="11" Result="100"/><App Id="1B" Version="11" Result="100"/><App Id="44" Version="11" Result="100"/><App Id="51" Version="11" Result="100"/></Applications></Office></Software></GenuineResults> 

  Spsys.log Content: 0x800700EA

  Licensing Data-->
  Software licensing service version: 6.0.6000.16386
  Name: Windows(TM) Vista, HomeBasic edition
  Description: Windows Operating System - Vista, OEM_SLP channel
  Activation ID: 199086aa-6cb8-4e5b-b698-f2be56f1e8ee
  Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
  Extended PID: 89572-00146-321-600021-02-1033-6000.0000-1472007
  Installation ID: 004635786931619003819064109233633574509066868022507855
  Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkId=57201
  Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkId=57203
  Use License URL: http://go.microsoft.com/fwlink/?LinkId=57205
  Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkId=57204
  Partial Product Key: 44MV3
  License Status: Licensed

  HWID Data-->
  HWID Hash Current: MAAAAAEAAgABAAEAAQABAAAAAgABAAEAnJ+W9LygpDmqdv6JaMjy9HjS0C2sVoDX

  OEM Activation 1.0 Data-->
  N/A

  OEM Activation 2.0 Data-->
  BIOS valid for OA 2.0: yes
  Windows marker version: 0x20000
  OEMID and OEMTableID Consistent: yes
  BIOS Information:
    ACPI Table Name OEMID Value OEMTableID Value
    APIC   HPQOEM  SLIC-CPC
    FACP   HPQOEM  SLIC-CPC
    HPET   HPQOEM  SLIC-CPC
    MCFG   HPQOEM  SLIC-CPC
    SLIC   HPQOEM  SLIC-CPC
    OEMB   HPQOEM  SLIC-CPC

  
   I've done the restoration "fix" twice before over the past 3 months. Last night, I restored to Monday last week  and I'm "Genuine" now but I'm missing 42 updates and counting. The last time I restored (early Jan) I turned off auto updates and have declined update downloads since then. Not a good thing, I know. Last week I thought maybe it was safe to get current on Updates, but no dice. Looking at the current Dx the product code is still not the code on the sticker on the side of the box?! Is this common? And there was a "tamper" error dating back to Oct 15, 2008 (if I dechiper the code correctly) but checking installed apps shows only Adobe Flash Player Plugin installed on 10/13/08. Nothing else days before or after. If I download updates now, will I get "invalidated" again? I may have to try it to get an answer...Are there updates I should avoid?

  Tuesday, March 17, 2009 4:27 AM
• 

  

  0

  Sign in to vote

  Hi thaugh,
  
    First off, it is normal for the key being used in Vista to be different then the one listed on the sticker on the computer. This is because computers, that are built by large manufactures that come with Vista Pre-Installed, come with two (2) Product Keys:

  A)   OEM SLP: This key comes pre-installed in Vista, when it comes from the Factory. This key is geared to work with the special instructions found only on that Manufacturer's computer hardware. So when Vista was installed using the OEM SLP key (at the factory) Vista looks at the motherboard and sees the special instructions and Self-Activates. (that's why you did not need to Activate your computer after you brought it home)

   

  B)    COA SLP: This is the Product key that you see on the sticker on the side (or bottom) of your computer. It is a valid product key, but should only be used in limited situations. The key must be Activated by Phone. (Note: All manufacturers that use the OEM SLP system are required by contract to include a Certificate of Authenticity (COA) sticker, that has a COA SLP key, on the computer)
  

  
  Your Vista is currently using the OEM SLP key.
  
    As for the On Disk tamper, it can be caused by a number of issue (hard drive sector error, virus, random corruption,  to name a few), but if it is occuring right after installing an Update, the update could be the cause. What happens is that when an Update adds updated versions of files, two things must happen 1) the file is replaced 2) Vista's System Catalog is updated to reflect the new file's signature hash (think fingerprint). If one or the other doesn't occur, there is a 'Mismatch' (meaning the signature hash listed in the system catalog doesn't match the actual file's hash) and a On Disk Mod-Auth event is triggered.  Updates have a recovery process that if anything goes wrong with the Update, it should roll back any changes it had already made.  So an Update has to have a catastrophic failure, for it to trigger a On Disk Mod-Auth.  I don't know enough about the inner working of Windows Update to know all the reasons an Update would fail in that way, but I do know that one of them would be if the computer is interupted, in some way, during install of the update or during the next reboot.
  
    My suggestion is to install only the updates you need  to be able to install Service Pack 1 and the install any additional updates, after. If you see this issue again, I suggest that you try doing the System Scan (the 2nd set of steps that I provided above) and if that doesn't work, then use the system restore.
  
    If this is happening consistently, I suggest going to the Windows Update solution center for additional assistance.
  
  Thank you,
  Darin MS

    

  ---

  Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please click the "Post was Helpful" button for that post. This will help us showcase the threads that best help our customers.

  Tuesday, March 17, 2009 5:43 PM