Windows 10: printmanagement and print spool on win 11

1. there is no printmanagement.msc on my device. why?2. Print spooler not working. sometimes need many taime to load and show the printer. sometimes eror. why?

:)

 

Print Spooling Issue

I did as suggested, however, it would not let me uncheck "Spool print doc ..." and the "Print directly to printer" was faded out and wouldn't let me check it.

Any suggestions.

Bmalone

 

Print Spooling Issue

Hi Beth,

An incompatible printer is one of the possible causes why it does not print with your Windows 10 device. We'll not include the steps you have done which are: Starting and stopping the spooling. Deleted items from print folder. Ran 3 different virus scans.
Reinstalled 4 times. Have updated drivers. I even set up printer as non wireless (with cable).

To troubleshoot your concern, kindly follow these steps:

• Use the Microsoft easy fix tool. Select Troubleshoot problems with devices and printers
  You may refer to this
  link. Simply run the file and follow the instructions in the Troubleshooting wizard.
• Download the latest driver directly from the OEM/manufacturer’s site.
• Clear print queue. Run an elevated command prompt and type the following commands in succeeding order:
  
  net stop spooler (press Enter)
  
  del %systemroot%\System32\spool\printers\* /Q (press Enter)
  
  net start spooler (press Enter)
  
• Roll back to a previous driver. Go to Device Manager> Print queues> Select your printer> Right click> Properties> Driver> Roll back.
• Edit registry. Note: You need to a backup file first before proceeding to the steps.
  Navigate to the ff. registry key:
  
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Print Processors

• Delete all the driver keys for existing printers, scanners, etc except for winprint.
• Restart your system. Proceed with the usual re-installation of latest printer drivers and see if it makes any difference.

If the issue still persists, please contact the printer manufacturer for better assistance.

Should you need further help, please let us know.

 

Print server instantly "prints" documents after they spooling but nothing actually prints.

We have a print server running on a Hyper-V Generation 2 Virtual Windows Server 2016 1607 hosted on a Windows Server 2016 1607. Up until a couple of days ago, things were printing fine,
now all of a sudden we are unable to print anything. Documents will briefly spool and then disappear from the queue. If a printer is set to keep printed documents in the queue they will show as printed immediately after they finish spooling no matter how many
pages are supposedly printed.

Here's the troubleshooting I've tried so far:

• Ensured Print Server has the latest Windows Update
• Uninstalled the most recent non-security updates since problems started (and shortly before)
• Restarted Server
• Restarted Print Spooler service, both using the restart option and simply stopping and starting it
• Ensured printers print on their own; both configuration pages and USB direct connect
• Tried printing from Multiple computers, including the print server itself
• Shut down print spooler and cleared everything out of System32\spool\PRINTERS
• For one of our multi-purpose printers I:
  • Created a new printer and port to it's IP address
  • Tried literally ever latest Windows 10 Driver available on the manufacturer's site.
  • Tried every Print Processor
  • Unchecked "Render print jobs on client computers"
  • Unchecked "SNMP Status Enabled" in the port configuration
  • Set it to print only after all pages are spooled
  • Unchecked "Print spooled documents first"
  • Checked "Hold mismatched documents"
  • Set a new IP Address

The only major change since this problem arose was a change to the permissions, but as far as I can tell the permissions are set up correctly and this doesn't sound like a permissions
issue because there's no permissions errors and documents are spooling correctly.

Any new suggestions are welcome because I've run out of ideas and at this point we are considering just rebuilding the thing on physical
hardware to see if Hyper-V is causing the issue.