Can't connect to remote printer

sagrant said:

I'm sorry but what is an 'admin' command window ?

Right click on the windows icon, in the bottom left hand corner, and you should see 'command prompt', and 'command prompt (admin)' (not sure on the exact wording, as i'm not in front of my win 10 machine).

Did that.
"The print spooler service is starting
"The print spooler service could not be started
"A system error has occurred
"System error 87 has occurred
"The parameter is incorrect.
That is all

sagrant said:

Did that.
"The print spooler service is starting
"The print spooler service could not be started
"A system error has occurred
"System error 87 has occurred
"The parameter is incorrect.
That is all

Hi sagrant, try running the Microsoft system file checker (SFC.exe)
Deatails here : https://support.microsoft.com/en-us/kb/929833

sagrant said:

Did that.
"The print spooler service is starting
"The print spooler service could not be started
"A system error has occurred
"System error 87 has occurred
"The parameter is incorrect.
That is all

Hi

If you type Services in the search command line and click on the app
Scroll down to Print Spooler and double click on it
Click on Dependencies tab
Check what dependencies the print spooler has, if any
you may need to click on "+" on those dependencies to more dependencies
Go back to the Services list
On each of the spooler dependencies, double click on it
Make sure it is set to Automatic in the Startup Type drop down menu
Now click on Start to start the service
Click OK

Let us know how you get on.

Regards
UKMedia

evansnp said:

Hi sagrant, try running the Microsoft system file checker (SFC.exe)
Deatails here : https://support.microsoft.com/en-us/kb/929833

Ran sfc /scannow . It took 45 minutes ! Result -
"Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.Log. Note that logging is currently not supported in offline servicing scenarios."
C:\Windows\Logs\CBS\CBS.Log doesn't work however. Not recognised.
What should I try now to see if it has been fixed.
Stuart

sagrant said:

Ran sfc /scannow . It took 45 minutes ! Result -
"Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.Log. Note that logging is currently not supported in offline servicing scenarios."
C:\Windows\Logs\CBS\CBS.Log doesn't work however. Not recognised.
What should I try now to see if it has been fixed.
Stuart

Try running SFC again.

UKMedia said:

Hi

If you type Services in the search command line and click on the app
Scroll down to Print Spooler and double click on it
Click on Dependencies tab
Check what dependencies the print spooler has, if any
you may need to click on "+" on those dependencies to more dependencies
Go back to the Services list
On each of the spooler dependencies, double click on it
Make sure it is set to Automatic in the Startup Type drop down menu
Now click on Start to start the service
Click OK

Let us know how you get on.

Regards
UKMedia

The spooler dependencies are HTTP and RPC with Dcom SPL as a subsidiary . All are running and on Automatic. But I still can't start the spooler.

sagrant said:

The spooler dependencies are HTTP and RPC with Dcom SPL as a subsidiary . All are running and on Automatic. But I still can't start the spooler.

If you search for the event log, can you see an error code for the time that it failed?

Type Fixit in the search and select the Fixit App, there should be an option to fix Print Spooler issues.

Windows 10 does not support Fixit or Fixit doesn't work with Windows 10