starred/pathcopycopy

Fork 0

mirror of https://github.com/clechasseur/pathcopycopy.git synced 2026-04-25 12:15:58 +03:00

[GH-ISSUE #36] Add Feature - Copy Network Printer UNC path context menu option #35

New issue

Open

opened 2026-02-25 21:32:30 +03:00 by kerem · 6 comments

kerem commented

2026-02-25 21:32:30 +03:00

Owner

Originally created by @ghost on GitHub (May 25, 2018).
Original GitHub issue: https://github.com/clechasseur/pathcopycopy/issues/36

In Windows, in the Devices and Printers window, one should be able to right-click a network printer hosted by a print server and copy its UNC path in the same way as with network folders. Sometimes network printer names are complex, and very long and difficult to type, and are not always listed in Active Directory so it would be beneficial to have the option to right-click a network printer on someone else's computer, then paste it into an email, then have them send it over to you so that you can easily add it yourself if you do not have it. Even if the printer name would be easy to type, it would be still be beneficial to have that feature added.

Originally created by @ghost on GitHub (May 25, 2018). Original GitHub issue: https://github.com/clechasseur/pathcopycopy/issues/36 In Windows, in the Devices and Printers window, one should be able to right-click a network printer hosted by a print server and copy its UNC path in the same way as with network folders. Sometimes network printer names are complex, and very long and difficult to type, and are not always listed in Active Directory so it would be beneficial to have the option to right-click a network printer on someone else's computer, then paste it into an email, then have them send it over to you so that you can easily add it yourself if you do not have it. Even if the printer name would be easy to type, it would be still be beneficial to have that feature added.

kerem added the

enhancement

help wanted

labels

2026-02-25 21:32:30 +03:00

kerem commented

2026-02-25 21:32:30 +03:00

Author

Owner

@clechasseur commented on GitHub (Jun 3, 2018):

This is an interesting idea, but I'm not sure it's easy to do. In Windows 10, the Devices and Printers dialog is no longer a Windows Explorer shell folder, it's a Control Panel dialog...

@clechasseur commented on GitHub (Jun 3, 2018): This is an interesting idea, but I'm not sure it's easy to do. In Windows 10, the Devices and Printers dialog is no longer a Windows Explorer shell folder, it's a Control Panel dialog...

kerem commented

2026-02-25 21:32:30 +03:00

Author

Owner

@ghost commented on GitHub (Jun 7, 2018):

Well perhaps WMI and/or the Registry can be used in this matter. Definitely feasable through the registry but I am sure its feasable through WMI as well, and if so, it is most likely much easier. It would have to work with Win 7, 8.1 and 10 of course.

@ghost commented on GitHub (Jun 7, 2018): Well perhaps WMI and/or the Registry can be used in this matter. Definitely feasable through the registry but I am sure its feasable through WMI as well, and if so, it is most likely much easier. It would have to work with Win 7, 8.1 and 10 of course.

kerem commented

2026-02-25 21:32:30 +03:00

Author

Owner

@ghost commented on GitHub (Jan 23, 2019):

Did you try working on this one? I think that would be a great enhancement.

@ghost commented on GitHub (Jan 23, 2019): Did you try working on this one? I think that would be a great enhancement.

kerem commented

2026-02-25 21:32:31 +03:00

Author

Owner

@clechasseur commented on GitHub (Jan 23, 2019):

No, I did not check yet. I just checked and it's still possible to view network printers in the same manner as before on Windows 10, so perhaps this is feasible after all...

@clechasseur commented on GitHub (Jan 23, 2019): No, I did not check yet. I just checked and it's still possible to view network printers in the same manner as before on Windows 10, so perhaps this is feasible after all...

kerem commented

2026-02-25 21:32:31 +03:00

Author

Owner

@clechasseur commented on GitHub (Sep 4, 2019):

I no longer have access to network printers to test this. If anyone wants to take a stab at this one, I'd accept a PR. 😄

@clechasseur commented on GitHub (Sep 4, 2019): I no longer have access to network printers to test this. If anyone wants to take a stab at this one, I'd accept a PR. 😄

kerem commented

2026-02-25 21:32:31 +03:00

Author

Owner

@ghost commented on GitHub (Sep 5, 2019):

Here is a suggestion in the hopes that it could make this easier. When a printer is network based, you always have it in the printer's name, such as "PRINTERNAME on SERVERNAME", perhaps you can just take that name in string form that is either stored in WMI or in the Registry, and then manipulate that string so as to make \SERVERNAME\PRINTERNAME

@ghost commented on GitHub (Sep 5, 2019): Here is a suggestion in the hopes that it could make this easier. When a printer is network based, you always have it in the printer's name, such as "PRINTERNAME on SERVERNAME", perhaps you can just take that name in string form that is either stored in WMI or in the Registry, and then manipulate that string so as to make \\SERVERNAME\PRINTERNAME