I cannot add a printer using an existing port and driver in Print Management. I get "Access is denied". This is a recent issue. That print servers has dozens of print queues.
Event log shows
"The print spooler failed to share printer RICOH Aficio SP C830DN PCL 6 with shared resource name RICOH Aficio SP C830DN PCL 6. Error 5. The printer cannot be used by others on the network."
I have looked that up but the posts are extremely old and do not offer much.z
Any assistance is appreciated.
It turned out to be a quick fix for a new printer exploit that locks one of the printer system files via GPO. It was intentional. I should read the bulletins more thoroughly.
II ran a command to undo the fix, added the printer, and the then reapplied it.
We're in a similar situation (I'm assuming its related to the PrintNightmare exploit) do you have a reference for the command you ran?
Or what it was in the bulletin that tipped you off? Thanks!
Just, the ACL hack was more knee jerk reaction but MS came up with the first changes to mitigate the issue in 5 days. Once the exploit was pointed out publicly, they had a quick turn around on the issue.
HI TJCooper-4250.
0.Could you please enter winver in command prompt on client win10 computer and look the os version and os version number ?[for example windows 10 enterprise 1809 (os build 17763.316)]
1.Please recall when your current issue first happen？
Do current issue happen after we install any update patches?
Could you please run below command on both client computer and printer server respectively then check if update patches cause our issue?
get-hotfix
2.If we add other printers shared by this w2019 printer server on client computer, will the same issue happen?
Hi everyone,
I’m facing the same issue with a different printer since 2 days.
Server: Windows Server 2016 Standard
Printer: kyocera taskalfa 3252ci
When i try to add a new printer to printer management including printer sharing, I’m receiving the following error message
Moreover, when i try to install an Isolation compatible driver, I’m getting this error
Strange thing, our customer was able to install a few printers with same drivers and same printer already.
Troubleshooting steps so far:
- Reboot server
- Check Permission of C:\Windows\System32\DriverStore\FileRepository
- Try with multiple diffrent printers and drivers
- verify driver is packed
- deactivate point to print via gpedit.msc
Next thing i would like to try is to install the latest windows update. There is just one outstandig at the moment KB5003638
The failure dialog stating an interactive windows station is required is the out come of ACLing the system32\spool\drivers directory for the system account. It was never a Microsoft recommended method to mitigate the exploit. I hope you installed the MS patch for the issue.
HI
1.If we not select "share this printer" this option in printer installation wizard, will the printer installation issue happen?
2.Is there shared printer name the same as "test_printer" ?
3.Could you please go to security item in printer server properties on both issue server 2016 and normal server 2016 then check if there is difference permission?
4. When your issue first happen? Could you please enter below command to get update history?
Is our issue related to recent windows update patches?
if the issue is related to windows update, we can try to uninstall it/them temporarily.
get-hotfix
We are having exactly the same problem, but on Windows Server 2012. I can add printers but cannot share them, failing with the error message: "Unable to install printer. Access is denied."
If you turn off sharing (which I know is no good) then I am sure the printer will install. However, that is no good on a network printer!
Sharing fails whatever the share name is and permissions have not been changed - the printer can be added by the 2 or 3 admin accounts I have tried with.
This print server has 80+ printers on and the problem has only been noticed this week. I thought it might be the latest Windows Updates so uninstalled all of them but that has not helped.
Is there anyone who can help? Thanks.
After days of troubleshooting without finding any solution i was able to solve the issue with a veeam restore of the vm. We had to add a few new printers but now everything is working agian.
I couldn't find the solution and for me this procedure was more time efficient.
Not very satisfactory - but it works.
HI
We can enable SetupAPI log first, then install printer again, When the problem happened, are there any event logs in below location on session host w2012r2?
event viewer\windows logs\
application
security
system
event viewer\windows logs\applications and services logs\microsoft\windows\printservice
SetupAPI.dev.log
SetupAPI Logging Registry Settings
https://docs.microsoft.com/en-us/windows-hardware/drivers/install/setupapi-logging-registry-settings
I'm not sure about anyone else but on my server the network printers still worked for clients that had them installed. For those trying to install using \\servername there were no printers showing up. They could be added through the Add print wizard as they were showing in AD. For me the solution was permissions on the drivers folder in System32/spool the System account was set to Deny
Just want to re-iterate the point that the PrintNightmare fix causes this issue and it was fixed it by removing the DENY permission on C:\Windows\System32\spool\drivers
I don't know how many hours we spent trying to fix this issue before coming upon the Deny permission issue. Removing it fixed the issue straightaway. Thanks!
While I have this issue with these error codes, i don't appear to have any permissions set to deny on those directories. Server 2019
Just like Russell Hopkins, I also spent hours trying to figure out what the @$#!& was going on before stumbling upon this solution. Thanks!
18 people are following this question.
