Vista - HP Officejet works intermittently

Occasionally, documents sent to print will queue, but will
not print.
Device manager says all is well and I have installed the
latest drivers.
This always corrects itself with a reboot, but that is not
altogether satisfactory.
Any help would be greatly appreciated.

Try this. It removes all Print Spooler service dependencies other than
the Remote Procedure Call service.

Click Start, Run and enter

sc config spooler depend= RPCSS Note the space after "=" but not
before it.

The Print Spooler service should now be able to run. Printer
functionality may be affected. It is best to delete, clean up and then
reinstall the printer drivers.


Now go back to services.msc

Right-click Print Spooler, and then click Properties.

Make sure that the startup type is set to Automatic. If it is not, click
Automatic in the Startup type list, and then click Apply.

Under Service status, click Start.

Click OK to close the Print Spooler Properties dialog box.

Let us know.

Tom
MS MVP
Windows shell/User


"GO" <theotts@sbcglobal.net> wrote in message
news:70145A66-D6E7-4246-A3BA-CA5E6BD653E1@microsoft.com...
> Occasionally, documents sent to print will queue, but will not print.
> Device manager says all is well and I have installed the latest
> drivers.
> This always corrects itself with a reboot, but that is not altogether
> satisfactory.
> Any help would be greatly appreciated.

"Tom Ferguson" <tom.msmvp@gmail.com> wrote in message
news:OE$2wgChHHA.4844@TK2MSFTNGP02.phx.gbl...
> Try this. It removes all Print Spooler service
> dependencies other than the Remote Procedure Call service.
>
> Click Start, Run and enter
>
> sc config spooler depend= RPCSS Note the space after
> "=" but not before it.
>
> The Print Spooler service should now be able to run.
> Printer functionality may be affected. It is best to
> delete, clean up and then reinstall the printer drivers.
>
>
> Now go back to services.msc
>
> Right-click Print Spooler, and then click Properties.
>
> Make sure that the startup type is set to Automatic. If it
> is not, click Automatic in the Startup type list, and then
> click Apply.
>
> Under Service status, click Start.
>
> Click OK to close the Print Spooler Properties dialog box.
>
> Let us know.
>
> Tom
> MS MVP
> Windows shell/User
>
>
> "GO" <theotts@sbcglobal.net> wrote in message
> news:70145A66-D6E7-4246-A3BA-CA5E6BD653E1@microsoft.com...
>> Occasionally, documents sent to print will queue, but
>> will not print.
>> Device manager says all is well and I have installed the
>> latest drivers.
>> This always corrects itself with a reboot, but that is
>> not altogether satisfactory.
>> Any help would be greatly appreciated.
>

Problem solved. Thank you very much!

I'm glad it is now working. All the best.

Tom
MSMVP
Windows Shell/User

"GO" <theotts@sbcglobal.net> wrote in message
news:00122237-0DDC-460A-9CB9-ECDDF502D1D8@microsoft.com...
> "Tom Ferguson" <tom.msmvp@gmail.com> wrote in message
> news:OE$2wgChHHA.4844@TK2MSFTNGP02.phx.gbl...
>> Try this. It removes all Print Spooler service dependencies other
>> than the Remote Procedure Call service.
>>
>> Click Start, Run and enter
>>
>> sc config spooler depend= RPCSS Note the space after "=" but
>> not before it.
>>
>> The Print Spooler service should now be able to run. Printer
>> functionality may be affected. It is best to delete, clean up and
>> then reinstall the printer drivers.
>>
>>
>> Now go back to services.msc
>>
>> Right-click Print Spooler, and then click Properties.
>>
>> Make sure that the startup type is set to Automatic. If it is not,
>> click Automatic in the Startup type list, and then click Apply.
>>
>> Under Service status, click Start.
>>
>> Click OK to close the Print Spooler Properties dialog box.
>>
>> Let us know.
>>
>> Tom
>> MS MVP
>> Windows shell/User
>>
>>
>> "GO" <theotts@sbcglobal.net> wrote in message
>> news:70145A66-D6E7-4246-A3BA-CA5E6BD653E1@microsoft.com...
>>> Occasionally, documents sent to print will queue, but will not
>>> print.
>>> Device manager says all is well and I have installed the latest
>>> drivers.
>>> This always corrects itself with a reboot, but that is not
>>> altogether satisfactory.
>>> Any help would be greatly appreciated.
>>
>
> Problem solved. Thank you very much!