Windows 10: "StartDocPrinter Call was not issued" after KB4598242

Last night my PC installed one single update: KB4598242

Today none of my printers work.


Tried the printer troubleshooter. Tried reinstalling printers. Tried restarting the spooler. Tried cacls utility on PRINTERS in system32\spool.


In the end I finally realized KB4598242 had been installed at 3 o'clock in the morning. Removed it and the printers started working.


I realize this KB has several security improvements so I will have to get it installed sooner or later. I suppose for now postponing as much as possible and hope MS has a update/patch/hotfix down the line is my best option.

:)

 

StartDocPrinter Call was not issued

Hi,

Thank you for writing to Microsoft Community Forums.

We understand how difficult it is, when the device doesn't work in the way it should and in order to get clarity and to assist you accordingly, please reply with the answers to the questions below

• What is the KB number of the Windows update installed, prior to this issue?
  
• What is the make and model of the PC?
  
• What is the model number of the HP printer?
  
• What are the online diagnostics that you have tried?

In this scenario, we researched on this issue and we suggest you to perform and check the settings as mentioned below.

Disclaimer: Important this section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur
if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.

Follow the steps to take
backup of registry.


Clean Print Procedure

This is a method to completely reset the print environment so that a printer can be properly added/reinstalled.

1. Press WIN key and R together, then type services.msc
   
2. Open Services, find Print Spooler and then right click and select Restart.
   
3. Search for Print management(PMC) on your computer (not available on Home SKU) and go to
   Printers.
   
4. Select all printers (press Ctrl when selecting), then right click and select
   Cancel all jobs to delete stuck/pending print jobs
   
5. Navigate to Printers & scanners in Settings
   
6. Remove all third party printers. Select the printer(s) and select
   Remove
   
7. If this doesn't work, delete in Registry. To do this:
   

1. 1. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers
      
   2. Delete 3rd party print queue entries from this location. DO NOT delete any of the following Microsoft print queues:
      Fax, Microsoft Print to PDF, Microsoft XPS Documents Writer, OneNote
      & Send To OneNote2016.
      

8. Navigate to your computer's settings, select Devices
and then Printers & scanners

9.
Open print server properties
(PSP) (can use PMC if available) and select the Drivers
tab.

10. Select all third-party driver(s) and then Remove
(select the second option Remove driver and driver package)

• Note: Do not remove any Microsoft print driver.

11. Navigate to 'Add or remove programs'in Settings

12. Find and uninstall all printer related OEM software.

13. Verify that all third party print monitors have been successfully removed by checking the registry. To do this:

1. 1. Navigate to: KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitor
      
   2. Delete 3rd party print monitor entries from this location. DO NOT delete any of the following print monitors:
      

1. 1. • AppMon (released RS1/RS2 timeframe)\
        
      • Local Port, LPR Port, Microsoft Shared Fax Monitor, Standard TCP/IP Port, USB Monitor & WSD Port
        
        Note: If you delete any print monitors, these changes will only take effect once you reboot (since the spooler service is still on)
        

14. Ensure the Print Spooler Service's Startup Type is set to Automatic and then reboot the machine.

After performing these steps, you will need to re-install the printer that the customer was having problems with. As a reminder, any other printers that were previously installed will also need to be re-installed if the customer
would like to use them.

1. Navigate to the computer's settings and select
   Devices.
   
2. Open Printers & Scanners and then select
   Add Printer or Scanner to re-add the device.
   
3. After the device is re-added, attempt to print the document.

However, you can also perform the below steps and check if that helps to fix the issue.

1. Click Start Menu and type
   CMD.
   
2. Right click on CMD and click on
   Run as Administrator.
   
3. Type C:\ and press Enter.
   
4. Type CD\Windows\System32\Spool and press
   Enter.
   
5. Type Cacls.exe PRINTERS /e /g users:C and press
   Enter. Restart the computer and check.
   

Also as an additional troubleshoot follow the steps as mentioned in this article:

Fix printer problems

We await your response.

Aditya Roy

Microsoft Community – Moderator

 

Cannot print to an HP M452nw over the network - StartDocPrinter Call was not issued

I have a workstation that will not print to an HP M452nw over the network. If I try and print a test page, it errors. If I try and print from notepad, I get an error that says: StartDocPrinter Call was not issued.

I have tried what was suggested in this article:

StartDocPrinter Call was not issued

I've tried using the solution here: printing failure

I've tried manually deleting drivers, printers, and ports, in device manager, the registry, print managment, and print server properties in in Devices and Printers in control panel.

I've tried setting the printer up as a TCP/IP device. I've tried using the HP install suite to install it. None of this worked. Restarting the print spooler does nothing.

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.