Home > Computers > 0x00000006 Error Adding Printer

0x00000006 Error Adding Printer

Warning: This post deals with editing the registry. If you don’t know what that is stop right here & ask someone else to help you. Using the registry incorrectly can cause serious problems that may require you to reinstall Windows. Use the registry at your own risk.

When adding a network printer you may receive an error that says, “Windows cannot connect to the printer. Operation failed with error 0x00000006.”


If you try again you may get an error that says, “Windows cannot connect to the printer. no printers were found.”

no printers

To resolve this issue open regedit & browse to HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers. Just to be safe make a backup of the Client Side Rendering Print Providers key. Then delete the Client Side Rendering Print Providers key. Close regedit. Restart the Print Spooler service. Now try adding the printer again & you should not get an error.


Categories: Computers Tags: ,
  1. null
    February 18, 2014 at 10:24 am

    Thank you, this resolved my issue.

  2. Yassine Souabni
    October 21, 2014 at 11:21 am

    Hi – encountred same error both on client & on Remote Desktop Services Servers…
    I first fixed it using the same process (delete all the key…)

    I noticed then that I had two registry different entries that pointed to the same print server.
    >the first was like serverName.domain…. (FQDN name)
    >the second was like servername (NetBIOS name)

    Key under
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider\Servers

    I just deleted the one with the NetBios short Name and accessed the print sevrer
    using the FQDN name then driver installation went correctly

    Thanks Patrick
    I wouldn’t have fixed this if I didn’t found your post

  3. Rick
    December 10, 2014 at 1:36 pm

    Any guesses what can cause this? I have one user who this happens to repeatedly. I’m getting tired of deleting the key…I could slap it all into a batch file and have her click it to fix, but I’d rather fix the root cause.

    • patrickhoban
      December 19, 2014 at 12:05 pm

      I’m not really sure. In my case I just purge that registry key every once in a while.

  4. Dude named Ben
    March 2, 2015 at 8:45 pm

    Good post fix worked for me.

  5. May 27, 2015 at 5:21 pm

    Awesome. this worked!

  6. Daniel Lewis
    January 20, 2016 at 9:58 pm

    Thank you so much! This was exactly what I was looking for.

  7. Chris Roberts
    February 5, 2016 at 2:03 pm

    This worked for us as well. We were having trouble in our computer labs, and after applying this on a few computers manually I ran across what looks like a hotfix:


    We’re working on applying this, but I though I’d mention it since it looks like that certainly applies to our situation and may apply to others as well.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: