Windows 10: Printer Error 740

Hello,I work in a domain environment and am having users with both Win10 and Win11 devices reporting issues adding printers, with an error kicking out #740- Contact your administrator for assistance. I've done research on this, and from what I can tell this is a privilege issue. I have discovered a workaround using the add a printer wizard ran with administrator privileges. You can either do this via control panel or the following command. This works on both Win10 and Win11.rundll32 printui.dll,PrintUIEntry /ilUsers used to be able to add new printers by going to Settings>Devices>Printer

:)

 

Can't share printer—getting error message

Step 1: Go to store.
Step 2: Buy a less shitty printer.
Step 3: Pick up some beer while you are there.
Step 4: Enjoy both your new printer and your beer.

In all seriousness, I have had more issues with Lexmark printers and their shitty drivers then any other manufacturer, HP is a close second though.

However, if you don't want to get a new printer*Laugh :laugh:, and I can understand that, when my Lexmark was giving me the same troubles in Win7(and Vista) I had to make sure the Windows firewall was ON and the firewall service was enabled and running. After I shared it I could re-disable the firewall and firewall services.

 

740 error loop

How can you fix a 740 error when the 740 error has to be fixed before you fix it?

 

Root cause of, We can't install this printer right now. Error: #740

Dear all,

* This year, after re-installing Windows 10 PCs as part of routine break/fix, we have started to receive this error message:

"We can't install this printer right now. Error: #740. Try again later or contact your network administrator for help"

* There are plenty of posts on the internet advising that the workaround is

a) Open a Windows command prompt window as Administrator

b) Then, run the following at the command prompt


rundll32 printui.dll,PrintUIEntry /il

* While we have added this to our Known Error database, and the workaround has restored service in all situations when needed, can anyone advise:

1) Is a fix available for the root cause of this issue?

2) If the answer to question 1) is 'yes', what is that fix please?

3) If the answer to question 1) is anyone connected with the tech geniuses in Microsoft to make a fix available please?

My manager has suggested that the root cause may have been introduced as an intended fix to the Microsoft printing issues that gained widespread coverage last year. This though is a speculative suggestion.

Any help is always appreciated *Smile

Regards,

Steve