Windows cannot connect to the printer 0x0000007e

You may also like...

20 Responses

  1. Tim says:

    Thank you sooooo much! I have been searching all over the web and I was unable to find any recent articles on my issue and everything else that I looked up didn’t work or did not fit our needs as we still wanted the print server to manage all of the printing of documents and settings. Other sites may have been close but this one resolved my problem. Have to make sure that you delete the BIDI registry hive (if that is the correct term) completely from the print server. After following your instructions precisely as stated, (making a backup of the registry first of course) everything installed perfectly for our XP x86 and W7 x64 edition clients.

    Thanks again!

  2. Steve says:

    Thanks for the terrific posting, your fix cleaned up the errors on our print server as well!

  3. Paul says:

    That did the trick! I had tried other “fixes” but this is the one that actually fixed it. Thanks!!

  4. Tim T. says:

    Many, many thanks for posting this solution! I was struggling for awhile with this problem.

  5. Cal says:

    Thanks, spent most of the day trying to sort this issue out after another team spent a day and gave up. This worked instantly! Absolute legend.

  6. andreas says:

    You are an unsong hero! however I did have to delete the [BIDI] key for each printer to get it to work. But finally it works.Thanks!

  7. russ says:

    Perfect….
    Only question I have, how does this affect existing computers that already have the printer installed from the print server?

  8. Lewis says:

    Have a read of the source and where I got the suggestion from. As far as I can tell from putting this in to an active environment, it will have no impact on existing installations.

    See here: http://social.technet.microsoft.com/Forums/en/winserverprint/thread/6c68f4d3-fa4c-4986-9567-bbe89551652f

  9. Bill says:

    It worked! I am running an HP laserjet P4014dn printer from Windows Server 2003 32 bit with 64 bit work stations. I got the 32 bit and 64 bit HP Universal drivers installed on the 32 bit server but got the 0x0000007e when adding the printer to 64 bit workstations. Deleted the bidi key and life is good! Thanks!

  10. Tim Nielsen says:

    Lewis! I cannot believe you figured this out! Thank you so much. You have saved me much time. Respect.

  11. Tom McGoldrick says:

    Lewis – great work! I’ve searched hi and low to no avail until your post. Kudos.

  12. Jim says:

    Wow Thank you SO much Lewis for bringing attention to it (and MS Alan too for the fix), this has resolved my finger nail biting exercise for the day with my end users! (re: HP 44″ designjet plotter)

  13. Snille says:

    Thank you! Worked like a charm! Been looking to solve this problem for quite some time for some of my clients! 🙂

  14. Gustaf says:

    Thank you very much!

  15. Josep says:

    WORKS! very fine thanks so much i’ven search the solution so time.

  16. Kiko Jimenez says:

    thank you for your post, it rally save my day. GREAT JOB!

  17. Mikhael lama says:

    Just delete the Key and save hours . Thanks

  18. Thanks Lewis, this is the real solusion…

    Just want to add here … that no need to delete this key, however under [BIDI] key try to correct the “Module” value. Try to match with working server.
    I just corrected it and it is working for me.

  19. Berend says:

    Thanks, after a long search this solution is working for us !

  20. Mike says:

    Thanks for the tip. It did the trick. I was having issues with an HP 4700n from a Windows Server 2003 32-bit with 64-bit Win 7 PCs. I installed the 32-bit & 64-bit HP Universal drivers on the server. From Win 7 PCs, we were unable to complete the printer install – received the pop-up error message “Windows cannot connect to the printer 0x0000007e”. Deleting this key eliminated the error.

Leave a Reply

Your email address will not be published. Required fields are marked *