grumpyolddude

The system automerged a few of my posts above, but remote procedure call failed and RPC unavailable have been in the mix, along with print spooler errors.
Before I tried last night, I went into Administrative Services and set the Remote Procedure Call and Remote procedure Call Locator to automatic, and restarted both of those and made sure the print spooler was started.
After a failed installation, if I check the event log, there's notification that the spooler stopped unexpectedly, then another stating that it was started again, as if it shuts down long enough to screw with me, the restarts and pretends nothing happened.

I just had the services list open, and the spooler was started. Without closing that window, I opened Printers and scanners and tried to add a printer. I was blessed with an error message that the print spooler is not running. I refreshed the services list, and the spooler was stopped.

Obviously, the action of trying to initialize a printer is stopping the spooler. Why would it do this, and how do I make it behave?

This is beyond annoying. I am deep into a project, a memorial for my deceased brother, and need every function this machine has to offer. Two weeks ago, it worked perfectly!