locked
print spooler & RPC locator services won't run (error 2) RRS feed

  • Question

  • OK, I'm back with some additional items that don't seem to work. After fixing the last problem that was caused by the registry cleaner (software license server won't start), I've run across some additional problems. Here are a couple more that I've found:

    Print spooler service
    RPC Locator service

    In both cases, I get an error 2 (file not found) message. I would go into the registry and fix them if I knew the name of the service. If this problem has been encountered before, and the fix exists, could someone please point me to it? Thanks.

    BTW, I found this because all of my printers were gone and when I attempted to add one I would get an error saying the spooler wasn't running. And, my wireless network adapter still won't start and I think it is related to the RPC locator service.
    Tuesday, March 24, 2009 12:35 AM

Answers

  • Hey davelw,

      Unfortunatly, I try to stay away from the Registry and so I don't know where things are loacted.  I suggest going to one of the Vista Newsgroups at http://go.microsoft.com/fwlink/?linkid=42486.  All you need is their registrty location.  

    Once you find out their registry locations, I think the easiest way to fix it would be to find a 64bit Vista that doesn't have the issue, navigate to the registry location for the Printer Spool service, right-click on the Service's Registry folder and select 'Export'.  Save it with a name something like 'SpoolServReg'.  Do the same thing for the RPC Locator Service.

    Once you have those two Reg Export files, move them to your computer and then double click on each. The Registry Folders for those two services, on your computer, should then be mirror copy of the computer that didn't have the problem.

    I hope that makes sense.


    By the way, what was the name and version of the Registry Cleaner that did this to you? 

    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 24, 2009 1:03 AM
  • OK Davelw, I think we are cooking with fire, now.

    It appears that fixing the services is going to be relatively easy.

    From experiance with your issue and my Engineer's experiance with a simillare issue, this is what we know:  You ran that Registry Cleaner, it deleted the 'ImagePath' entry in the Registry Key of each of those Services.  If you had tried to restart the Service using the Net Start Slsvc command, you would have received a "System error 3" message.  Instead, you had the Registry Cleaner restore from it's backup, so it undeleted all the 'ImagePath' entries.  These newly undeleted 'ImagePath' entries look perfect, they have the correct 'Type', they have the correct Path data... but for some reason (that no one I have talked to can figure out) {I just figured it out! If you care to know, I have include a description of why, at the bottom of this post} the services will not run and when you try to restart them, you now get the 'System Error 2' message.

    So all we need to do is delete each of the current 'ImagePath' entries and remake them.  I think I've come up with a good set of generic steps to do that.

    1) Back up the Registry! 
    2) Find (and go to) the location of the Registry Key that controles the Service that you want to fix (example: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Spooler)
    3) Record the path listed for the 'ImagePath' entry  (example: ImagePath"="%SystemRoot%\\System32\\spoolsv.exe)
    4) Delete the 'ImagePath' entry
    5) Click the'Edit' dropdown menu, hover over 'New' then select 'Expandable String Value'
    6) Name the new entry 'ImagePath'
    7) Right-click the new 'ImagePath' entry and select 'Modify'
    8) Type in the path you recorder in step 3

    9) Click 'Ok' and you are done...go back to step 1... rinse and repeat




    Thank you,
    Darin MS

    P.S.  Here is why the Undeleted 'ImagePath' entries don't work. It doesn't help you, but it's a good thing for us to know so that when we contact the maker of the Cleaner we can explain what is happening.

    If you look at the Registry Editor window and compare the undeleted 'ImagePath" entry with a good one, they look the same.  But if you export the Registry Key and open it in not pad, here is what you see:

    The 'ImagePath' entry from the Registry Key "Spooler" from my computer:

    "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,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,73,\
      00,70,00,6f,00,6f,00,6c,00,73,00,76,00,2e,00,65,00,78,00,65,00,00,00



    The 'ImagePath' entry from  the Registry Key "Spooler" from your computer:

    "ImagePath"="%SystemRoot%\\System32\\spoolsv.exe"


    It would appear that when you look at 'ImagePath' entries in the Registry Editor, it only shows you the plain text path, but it actually stores the path as a hex. So when the Registry Cleaner undeleted the Entry, it just included the plain text path instead of the hex of the path and Vista couldn't understand it.


    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 24, 2009 10:55 PM
  • I've gone through and fixed all of the registry entries that I identified yesterday. It looks like everything is now working correctly. Thank you very much for all of your help on this. I've learned a lot about my services and I'm just happy to have things back to 'normal'.

    Now, it wasn't without its problems. When I did the first couple of [ImagePath] entries, I used a double slash ("\\") in the path. Boy, was that a mistake. When I tried to start one of the services to see if it was now working, my PC rebooted and continued rebooting. I tried to start up in safe mode and even that would just reboot. I finally rebooted using the last known good boot and that solved the problem. I was then able to fix the entries in the registry and now it's all good.

    Thanks again.
    dave
    • Marked as answer by Darin Smith MS Wednesday, March 25, 2009 5:20 PM
    Wednesday, March 25, 2009 3:42 PM

All replies

  • Just so you have the latest, here are the results of the MGAD tool:

    Diagnostic Report (1.9.0006.1):
    -----------------------------------------
    WGA Data-->
    Validation Status: Genuine
    Validation Code: 0
    Online Validation Code: 0x0
    Cached Validation Code: 0x0
    Windows Product Key: *****-*****-27HYQ-XTKW2-WQD8Q
    Windows Product Key Hash: U8YEZzymoD4DMyaMb32rPrNIS90=
    Windows Product ID: 89583-OEM-7332157-00061
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6001.2.00010300.1.0.003
    ID: {2EE107BE-C004-4237-AC91-4E490C947D5B}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000009
    Build lab: 6001.vistasp1_gdr.080917-1612
    TTS Error:
    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: 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 7.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>{2EE107BE-C004-4237-AC91-4E490C947D5B}</UGUID><Version>1.9.0006.1</Version><OS>6.0.6001.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-WQD8Q</PKey><PID>89583-OEM-7332157-00061</PID><PIDType>2</PIDType><SID>S-1-5-21-342609163-3139870115-61042858</SID><SYSTEM><Manufacturer>HP-Pavilion</Manufacturer><Model>KQ497AA-ABA m9340f</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>5.23   </Version><SMBIOSVersion major="2" minor="5"/><Date>20080421000000.000000+000</Date></BIOS><HWID>E1333507018400FA</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>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_SLP channel
    Activation ID: bffdc375-bbd5-499d-8ef1-4f37b61c895f
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 89583-00146-321-500061-02-1033-6001.0000-1892008
    Installation ID: 014604251316682394458552180660033874141441588760160780
    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: WQD8Q
    License Status: Licensed

    HWID Data-->
    HWID Hash Current: MgAAAAEAAAABAAEAAgABAAAABAABAAEAonZSZbhWvDqw9OJs8vQIysFn/FSiwqxWzDE=

    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
      OEMB            HPQOEM        SLIC-CPC
      GSCI            HPQOEM        SLIC-CPC
      SLIC            HPQOEM        SLIC-CPC
      SSDT            HPQOEM        SLIC-CPC



    Tuesday, March 24, 2009 12:47 AM
  • Hey davelw,

      Unfortunatly, I try to stay away from the Registry and so I don't know where things are loacted.  I suggest going to one of the Vista Newsgroups at http://go.microsoft.com/fwlink/?linkid=42486.  All you need is their registrty location.  

    Once you find out their registry locations, I think the easiest way to fix it would be to find a 64bit Vista that doesn't have the issue, navigate to the registry location for the Printer Spool service, right-click on the Service's Registry folder and select 'Export'.  Save it with a name something like 'SpoolServReg'.  Do the same thing for the RPC Locator Service.

    Once you have those two Reg Export files, move them to your computer and then double click on each. The Registry Folders for those two services, on your computer, should then be mirror copy of the computer that didn't have the problem.

    I hope that makes sense.


    By the way, what was the name and version of the Registry Cleaner that did this to you? 

    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 24, 2009 1:03 AM
  • I believe the program I used that caused all of these problems was 'PC Checkup 4.03' (I downloaded it from Softpedia). It would great if you guys could check it out and see if you encounter the same kinds of issues that I have.

    With regards to exporting registry entries from Vista, I have the only Vista based PC in our office. So unfortunately, I don't have the option of exporting something from another Vista PC's registry. I was thinking of (and already started) simply exporting each of the keys [for the services that I've found give me an error 2] from the registry and then reimporting them. I don't know if that will help but it's pretty much all I have available to me here.

    I'm sure you're busy but if you could help me out on this it would be greatly appreciated. I could post the text from the exported keys in a message (reply) and then when you have time, you could compare it to what you have. If it's the same, then I'd just import the file back into the registry and hopefully it would resolve the issues. If you don't have the time, that's completely understandable and I'll find some other way to fix the problems.

    Thanks for all of your help so far Darin. It is appreciated.
    Tuesday, March 24, 2009 2:29 PM
  • Hi Davelw,

      It's outside my 'offical' support boundaries, but I will try to help, as best as I can. 

    (Disclaimer: since this is outside my area of training and outside my support boundaries, any support I provide, for this issue, going forward, should be followed, at your own risk. Microsoft can not be held responsible for any damage (or any other negative outcome) that results from this support)

      I think we should take a 2 pronged approch.  

    First: post the Registry Entry locations, so I can see how they look on my system (and develop steps to recreate the entries, if needed).
    In the mean time: you try reimporting the entries and see if that resolves the issue.

    If your reimporting idea doesn't pan out, I will try to give you steps on how to manually recreate the entries, from scratch.

    Darin
    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 24, 2009 6:04 PM
  • No problem Darin. I have no issues with doing this through the improper channels and not holding MS accountable. I did export the printer service from the registry and then ran the file but it didn't change anything. My print spooler still gives me an error 2 when I try to start it.

    So with that in mind, here are a couple of the entries that I know do not work:
    Print spooler:
    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Spooler]
    "DisplayName"="@%systemroot%\\system32\\spoolsv.exe,-1"
    "Group"="SpoolerGroup"
    "Description"="@%systemroot%\\system32\\spoolsv.exe,-2"
    "ObjectName"="LocalSystem"
    "ErrorControl"=dword:00000001
    "Start"=dword:00000002
    "Type"=dword:00000110
    "DependOnService"=hex(7):52,00,50,00,43,00,53,00,53,00,00,00,68,00,74,00,74,00,\
      70,00,00,00,00,00
    "ServiceSidType"=dword:00000001
    "RequiredPrivileges"=hex(7):53,00,65,00,54,00,63,00,62,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,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,4c,00,6f,00,61,\
      00,64,00,44,00,72,00,69,00,76,00,65,00,72,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,41,00,73,00,73,00,69,00,67,00,6e,\
      00,50,00,72,00,69,00,6d,00,61,00,72,00,79,00,54,00,6f,00,6b,00,65,00,6e,00,\
      50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,00,00
    "FailureActions"=hex:80,51,01,00,00,00,00,00,00,00,00,00,03,00,00,00,14,00,00,\
      00,01,00,00,00,60,ea,00,00,01,00,00,00,60,ea,00,00,00,00,00,00,00,00,00,00
    "ImagePath"="%SystemRoot%\\System32\\spoolsv.exe"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Spooler\Performance]
    "Close"="PerfClose"
    "Collect"="PerfCollect"
    "Collect Timeout"=dword:000007d0
    "Library"="winspool.drv"
    "Object List"="1450"
    "Open"="PerfOpen"
    "Open Timeout"=dword:00000fa0

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Spooler\Security]
    "Security"=hex:01,00,14,80,78,00,00,00,84,00,00,00,14,00,00,00,30,00,00,00,02,\
      00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\
      00,00,02,00,48,00,03,00,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,\
      05,0b,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,\
      20,02,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,05,12,00,00,00,01,\
      01,00,00,00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Spooler\Enum]
    "0"="Root\\LEGACY_SPOOLER\\0000"
    "Count"=dword:00000001
    "NextInstance"=dword:00000001

    CNG Key Isolation:
    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\KeyIso]
    "DisplayName"="@keyiso.dll,-100"
    "Description"="@keyiso.dll,-101"
    "ObjectName"="LocalSystem"
    "ErrorControl"=dword:00000001
    "Start"=dword:00000003
    "Type"=dword:00000020
    "DependOnService"=hex(7):52,00,70,00,63,00,53,00,73,00,00,00,00,00
    "ImagePath"="%SystemRoot%\\system32\\lsass.exe"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\KeyIso\Security]
    "Security"=hex:01,00,14,80,b4,00,00,00,c0,00,00,00,14,00,00,00,30,00,00,00,02,\
      00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\
      00,00,02,00,84,00,06,00,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,\
      05,12,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,\
      20,02,00,00,00,00,14,00,9d,01,02,00,01,01,00,00,00,00,00,05,04,00,00,00,00,\
      00,14,00,9d,01,02,00,01,01,00,00,00,00,00,05,06,00,00,00,00,00,14,00,8d,01,\
      02,00,01,01,00,00,00,00,00,05,06,00,00,00,00,00,14,00,00,01,00,00,01,01,00,\
      00,00,00,00,05,0b,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00,01,01,00,00,\
      00,00,00,05,12,00,00,00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\KeyIso\Enum]
    "0"="Root\\LEGACY_KEYISO\\0000"
    "Count"=dword:00000001
    "NextInstance"=dword:00000001


    RPC Locator Service:
    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RpcLocator]
    "DisplayName"="@%systemroot%\\system32\\Locator.exe,-2"
    "Description"="@%systemroot%\\system32\\Locator.exe,-3"
    "ObjectName"="NT AUTHORITY\\NetworkService"
    "ErrorControl"=dword:00000001
    "Start"=dword:00000003
    "Type"=dword:00000010
    "FailureActions"=hex:84,03,00,00,00,00,00,00,00,00,00,00,03,00,00,00,14,00,00,\
      00,01,00,00,00,c0,d4,01,00,01,00,00,00,e0,93,04,00,00,00,00,00,00,00,00,00
    "ImagePath"="%SystemRoot%\\system32\\locator.exe"


    Again, any help or insight that you can provide is greatly appreciated.
    Tuesday, March 24, 2009 8:58 PM
  • OK, I just went through every service on my PC and tried to start and stop them (if it wasn't already started). Here is the list of all of the services that gave me an error 2 when I tried to start them:
    CNG Key Isolation
    Print spooler
    RPC locator
    Interactive Service detection
    NVIDIA display driver service
    SNMP trap
    Volume shadow copy
    WMI performance adapter
    Application Layer gateway
    DFS replication
    Distributed transaction coordinator
    Netlogon
    Protected storage
    Virtual disk
    Windows media player network sharing service

    Obviously, some of the services I tried were dependent on other services so those aren't included (if it didn't give me an error 2, then I assumed that at least it could find the service). Some of these services are not that important but others are. I'd like to fix as many of them as I can so hopefully we'll be able to get this mess cleaned up.

    Thanks a lot Darin. Please don't do anything the will get you in trouble but any help you can provide, official or otherwise, is highly appreciated.
    Tuesday, March 24, 2009 9:26 PM
  • OK Davelw, I think we are cooking with fire, now.

    It appears that fixing the services is going to be relatively easy.

    From experiance with your issue and my Engineer's experiance with a simillare issue, this is what we know:  You ran that Registry Cleaner, it deleted the 'ImagePath' entry in the Registry Key of each of those Services.  If you had tried to restart the Service using the Net Start Slsvc command, you would have received a "System error 3" message.  Instead, you had the Registry Cleaner restore from it's backup, so it undeleted all the 'ImagePath' entries.  These newly undeleted 'ImagePath' entries look perfect, they have the correct 'Type', they have the correct Path data... but for some reason (that no one I have talked to can figure out) {I just figured it out! If you care to know, I have include a description of why, at the bottom of this post} the services will not run and when you try to restart them, you now get the 'System Error 2' message.

    So all we need to do is delete each of the current 'ImagePath' entries and remake them.  I think I've come up with a good set of generic steps to do that.

    1) Back up the Registry! 
    2) Find (and go to) the location of the Registry Key that controles the Service that you want to fix (example: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Spooler)
    3) Record the path listed for the 'ImagePath' entry  (example: ImagePath"="%SystemRoot%\\System32\\spoolsv.exe)
    4) Delete the 'ImagePath' entry
    5) Click the'Edit' dropdown menu, hover over 'New' then select 'Expandable String Value'
    6) Name the new entry 'ImagePath'
    7) Right-click the new 'ImagePath' entry and select 'Modify'
    8) Type in the path you recorder in step 3

    9) Click 'Ok' and you are done...go back to step 1... rinse and repeat




    Thank you,
    Darin MS

    P.S.  Here is why the Undeleted 'ImagePath' entries don't work. It doesn't help you, but it's a good thing for us to know so that when we contact the maker of the Cleaner we can explain what is happening.

    If you look at the Registry Editor window and compare the undeleted 'ImagePath" entry with a good one, they look the same.  But if you export the Registry Key and open it in not pad, here is what you see:

    The 'ImagePath' entry from the Registry Key "Spooler" from my computer:

    "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,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,73,\
      00,70,00,6f,00,6f,00,6c,00,73,00,76,00,2e,00,65,00,78,00,65,00,00,00



    The 'ImagePath' entry from  the Registry Key "Spooler" from your computer:

    "ImagePath"="%SystemRoot%\\System32\\spoolsv.exe"


    It would appear that when you look at 'ImagePath' entries in the Registry Editor, it only shows you the plain text path, but it actually stores the path as a hex. So when the Registry Cleaner undeleted the Entry, it just included the plain text path instead of the hex of the path and Vista couldn't understand it.


    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 24, 2009 10:55 PM
  • Thanks Darin. I will try to get all of these fixed tomorrow. And I am glad to see your explanation as to what happened. It makes a lot of sense. As a software engineer, I'm always interested to know what it was that went wrong. I'll update you tomorrow on whether I was able to get everything fixed. 
    Tuesday, March 24, 2009 11:30 PM
  • I've gone through and fixed all of the registry entries that I identified yesterday. It looks like everything is now working correctly. Thank you very much for all of your help on this. I've learned a lot about my services and I'm just happy to have things back to 'normal'.

    Now, it wasn't without its problems. When I did the first couple of [ImagePath] entries, I used a double slash ("\\") in the path. Boy, was that a mistake. When I tried to start one of the services to see if it was now working, my PC rebooted and continued rebooting. I tried to start up in safe mode and even that would just reboot. I finally rebooted using the last known good boot and that solved the problem. I was then able to fix the entries in the registry and now it's all good.

    Thanks again.
    dave
    • Marked as answer by Darin Smith MS Wednesday, March 25, 2009 5:20 PM
    Wednesday, March 25, 2009 3:42 PM
  • Hi davelw,

      Yep, that's my fault.  I had just copied the path from my exported Reg File and didn't even think about the double slashs. Very sorry for that.

      But  I am happy to hear you are up and running. No thanks are necessary, I had the time and I got to dive into and learn more about the Registry, which is something I had shied away from, in the past. 

    Have a good day,
    Darin
    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.
    Wednesday, March 25, 2009 5:20 PM
  • Thank you for this, Darin! (yee-hah!) Everything I was reading about this error kept talking about missing files - well, my files weren't missing. This registry fix was the crucial bit of information that I needed.

     

    rts

    Tuesday, September 21, 2010 4:36 PM