crwdns2933423:0crwdne2933423:0
crwdns2918538:0crwdne2918538:0

crwdns2934243:0crwdne2934243:0 Nick

crwdns2934249:0crwdne2934249:0:

-I have encountered this with HP printers that refuse to install correctly, notably the newer 2016+ HP DS models. It's really bad on the newer HP DS firmware, to the point I have had to reset one so many times that I check the behavior for a match, do a network reset, issue a new static IP, and then edit the port on the PC. The HP DS firmware has an awful network/print layer stack because HP focuses its energy on blocking third-party toner/ink, not on making the network stack reliable. AND IF the port edit doesn't fix it, I need to delete and re-add it, and after so many, clear the registry of any printer queue pileup.
+I have encountered this with HP printers that refuse to install correctly, notably the newer 2016+ HP DS models. It's really bad on the newer HP DS firmware in general compared to the legacy HP firmware which didn't have DS, to the point I have had to reset one I picked (before I realized how bad HP DS firmware is, HP sold me on it because of how good the M401/M425 was) so many times that I check the behavior for a match, do a network reset, issue a new static IP, and then edit the port on the PC. The HP DS firmware has an awful network/print layer stack because HP focuses its energy on blocking third-party toner/ink, not on making the network stack reliable. AND IF the port edit doesn't fix it, I need to delete and re-add it, and after so many, clear the registry of any printer queue pileup.
First, go into the device manager, ***look for Printers and Print queues, and purge all but Microsoft Print to PDF.*** Once you do that, restart the PC and reinstall it. If the problem persists, you have to do it in the registry.
[image|3621290]
If it comes to a point where there is some printer pileup in the registry, you may have to uninstall the Epson driver, then delete every Epson printer from the registry. Leave Microsoft Print to PDF be, but anything Epson related for printers has to go. This does work, as it is how I have had to fix the connection issue on the HP DS machines one too many times. After removal, restart the PC and re-add the printers from scratch. ***You need to reboot the system before reinstalling it, as this is the only way to clear the problematic queue "memory. This fix is only needed with serious backups, so you should not have to do this regularly. If you do, your OS is partially broken, or the printer has hot garbage firmware. This is a "all else fails" solution - not a first line solution*.***[br]
*Yes, I use this as a first-line fix once I know I've re-added the HP M426 I use this workaround on, but that printer has horrible firmware, and I sometimes have had to do it 2-3 times, and it likes to hang on bad queues after that.
[quote|format=featured]
Here is the registry set where the printers are in Windows: ***Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers - once you find it, delete everything but Microsoft Print to PDF.***
[/quote]
It will be located here in the registry. Just delete the entry, not the entire folder:
[image|3620845]

crwdns2915684:0crwdne2915684:0:

open

crwdns2934245:0crwdne2934245:0 Nick

crwdns2934249:0crwdne2934249:0:

-I have encountered this with HP printers that refuse to install correctly, notably the newer 2016+ HP DS models. It's really bad on the newer HP DS firmware, to the point I have had to reset one so many times that I check the behavior for a match, do a network reset, then issue it a new static IP, and then edit the port. The HP DS firmware has an awful network/print layer stack because HP focuses its energy on blocking third-party toner/ink, not a good network stack. AND IF the port edit doesn't fix it, I need to delete and re-add it, and after so many, clear the registry of any printer queue pileup.
+I have encountered this with HP printers that refuse to install correctly, notably the newer 2016+ HP DS models. It's really bad on the newer HP DS firmware, to the point I have had to reset one so many times that I check the behavior for a match, do a network reset, issue a new static IP, and then edit the port on the PC. The HP DS firmware has an awful network/print layer stack because HP focuses its energy on blocking third-party toner/ink, not on making the network stack reliable. AND IF the port edit doesn't fix it, I need to delete and re-add it, and after so many, clear the registry of any printer queue pileup.
First, go into the device manager, ***look for Printers and Print queues, and purge all but Microsoft Print to PDF.*** Once you do that, restart the PC and reinstall it. If the problem persists, you have to do it in the registry.
[image|3621290]
-If it comes to a point where the pileup is bad enough, UNINSTALLING THE EPSON DRIVER FIRST AND THEN deleting all of the printers except Microsoft Print to PDF is often how I have had to fix the fault one too many times. You need to purge the printers from the list, then re-add them from scratch. ***You need to reboot the system beforehand, which is a requirement because it's the only way to eliminate the mess. You should not have to do this regularly - if you do, your OS is partially broken, or the printer has hot garbage firmware. This is a "all else fails" solution - not a first line solution*.***[br]
-* Yes, I use this as a first-line fix once I know I've re-added the HP M426 I use this workaround on, but that printer has horrible firmware.
+If it comes to a point where there is some printer pileup in the registry, you may have to uninstall the Epson driver, then delete every Epson printer from the registry. Leave Microsoft Print to PDF be, but anything Epson related for printers has to go. This does work, as it is how I have had to fix the connection issue on the HP DS machines one too many times. After removal, restart the PC and re-add the printers from scratch. ***You need to reboot the system before reinstalling it, as this is the only way to clear the problematic queue "memory. This fix is only needed with serious backups, so you should not have to do this regularly. If you do, your OS is partially broken, or the printer has hot garbage firmware. This is a "all else fails" solution - not a first line solution*.***[br]
+*Yes, I use this as a first-line fix once I know I've re-added the HP M426 I use this workaround on, but that printer has horrible firmware, and I sometimes have had to do it 2-3 times, and it likes to hang on bad queues after that.
[quote|format=featured]
Here is the registry set where the printers are in Windows: ***Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers - once you find it, delete everything but Microsoft Print to PDF.***
[/quote]
It will be located here in the registry. Just delete the entry, not the entire folder:
[image|3620845]

crwdns2915684:0crwdne2915684:0:

open

crwdns2934245:0crwdne2934245:0 Nick

crwdns2934249:0crwdne2934249:0:

I have encountered this with HP printers that refuse to install correctly, notably the newer 2016+ HP DS models. It's really bad on the newer HP DS firmware, to the point I have had to reset one so many times that I check the behavior for a match, do a network reset, then issue it a new static IP, and then edit the port. The HP DS firmware has an awful network/print layer stack because HP focuses its energy on blocking third-party toner/ink, not a good network stack. AND IF the port edit doesn't fix it, I need to delete and re-add it, and after so many, clear the registry of any printer queue pileup.
First, go into the device manager, ***look for Printers and Print queues, and purge all but Microsoft Print to PDF.*** Once you do that, restart the PC and reinstall it. If the problem persists, you have to do it in the registry.
-[image|3621288]
+[image|3621290]
If it comes to a point where the pileup is bad enough, UNINSTALLING THE EPSON DRIVER FIRST AND THEN deleting all of the printers except Microsoft Print to PDF is often how I have had to fix the fault one too many times. You need to purge the printers from the list, then re-add them from scratch. ***You need to reboot the system beforehand, which is a requirement because it's the only way to eliminate the mess. You should not have to do this regularly - if you do, your OS is partially broken, or the printer has hot garbage firmware. This is a "all else fails" solution - not a first line solution*.***[br]
* Yes, I use this as a first-line fix once I know I've re-added the HP M426 I use this workaround on, but that printer has horrible firmware.
[quote|format=featured]
Here is the registry set where the printers are in Windows: ***Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers - once you find it, delete everything but Microsoft Print to PDF.***
[/quote]
It will be located here in the registry. Just delete the entry, not the entire folder:
[image|3620845]

crwdns2915684:0crwdne2915684:0:

open

crwdns2934245:0crwdne2934245:0 Nick

crwdns2934249:0crwdne2934249:0:

I have encountered this with HP printers that refuse to install correctly, notably the newer 2016+ HP DS models. It's really bad on the newer HP DS firmware, to the point I have had to reset one so many times that I check the behavior for a match, do a network reset, then issue it a new static IP, and then edit the port. The HP DS firmware has an awful network/print layer stack because HP focuses its energy on blocking third-party toner/ink, not a good network stack. AND IF the port edit doesn't fix it, I need to delete and re-add it, and after so many, clear the registry of any printer queue pileup.
First, go into the device manager, ***look for Printers and Print queues, and purge all but Microsoft Print to PDF.*** Once you do that, restart the PC and reinstall it. If the problem persists, you have to do it in the registry.
+
+[image|3621288]
If it comes to a point where the pileup is bad enough, UNINSTALLING THE EPSON DRIVER FIRST AND THEN deleting all of the printers except Microsoft Print to PDF is often how I have had to fix the fault one too many times. You need to purge the printers from the list, then re-add them from scratch. ***You need to reboot the system beforehand, which is a requirement because it's the only way to eliminate the mess. You should not have to do this regularly - if you do, your OS is partially broken, or the printer has hot garbage firmware. This is a "all else fails" solution - not a first line solution*.***[br]
* Yes, I use this as a first-line fix once I know I've re-added the HP M426 I use this workaround on, but that printer has horrible firmware.
[quote|format=featured]
Here is the registry set where the printers are in Windows: ***Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers - once you find it, delete everything but Microsoft Print to PDF.***
[/quote]
It will be located here in the registry. Just delete the entry, not the entire folder:
[image|3620845]

crwdns2915684:0crwdne2915684:0:

open

crwdns2934245:0crwdne2934245:0 Nick

crwdns2934249:0crwdne2934249:0:

I have encountered this with HP printers that refuse to install correctly, notably the newer 2016+ HP DS models. It's really bad on the newer HP DS firmware, to the point I have had to reset one so many times that I check the behavior for a match, do a network reset, then issue it a new static IP, and then edit the port. The HP DS firmware has an awful network/print layer stack because HP focuses its energy on blocking third-party toner/ink, not a good network stack. AND IF the port edit doesn't fix it, I need to delete and re-add it, and after so many, clear the registry of any printer queue pileup.
+First, go into the device manager, ***look for Printers and Print queues, and purge all but Microsoft Print to PDF.*** Once you do that, restart the PC and reinstall it. If the problem persists, you have to do it in the registry.
+
If it comes to a point where the pileup is bad enough, UNINSTALLING THE EPSON DRIVER FIRST AND THEN deleting all of the printers except Microsoft Print to PDF is often how I have had to fix the fault one too many times. You need to purge the printers from the list, then re-add them from scratch. ***You need to reboot the system beforehand, which is a requirement because it's the only way to eliminate the mess. You should not have to do this regularly - if you do, your OS is partially broken, or the printer has hot garbage firmware. This is a "all else fails" solution - not a first line solution*.***[br]
-****Yes, I use this as a first-line fix once I know I've re-added the HP M426 I use this workaround on, but that printer has horrible firmware.***
+* Yes, I use this as a first-line fix once I know I've re-added the HP M426 I use this workaround on, but that printer has horrible firmware.
[quote|format=featured]
Here is the registry set where the printers are in Windows: ***Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers - once you find it, delete everything but Microsoft Print to PDF.***
[/quote]
It will be located here in the registry. Just delete the entry, not the entire folder:
[image|3620845]

crwdns2915684:0crwdne2915684:0:

open

crwdns2934245:0crwdne2934245:0 Nick

crwdns2934249:0crwdne2934249:0:

I have encountered this with HP printers that refuse to install correctly, notably the newer 2016+ HP DS models. It's really bad on the newer HP DS firmware, to the point I have had to reset one so many times that I check the behavior for a match, do a network reset, then issue it a new static IP, and then edit the port. The HP DS firmware has an awful network/print layer stack because HP focuses its energy on blocking third-party toner/ink, not a good network stack. AND IF the port edit doesn't fix it, I need to delete and re-add it, and after so many, clear the registry of any printer queue pileup.
-If it comes to a point where the pileup is bad enough, UNINSTALLING THE EPSON DRIVER FIRST AND THEN deleting all of the printers except Microsoft Print to PDF is often how I have had to fix the fault one too many times. You need to purge the printers from the list, then re-add them from scratch. Y***ou need to reboot the system beforehand, which is a requirement because it's the only way to eliminate the mess. You should not have to do this regularly - if you do, your OS is partially broken, or the printer has hot garbage firmware.***
+If it comes to a point where the pileup is bad enough, UNINSTALLING THE EPSON DRIVER FIRST AND THEN deleting all of the printers except Microsoft Print to PDF is often how I have had to fix the fault one too many times. You need to purge the printers from the list, then re-add them from scratch. ***You need to reboot the system beforehand, which is a requirement because it's the only way to eliminate the mess. You should not have to do this regularly - if you do, your OS is partially broken, or the printer has hot garbage firmware. This is a "all else fails" solution - not a first line solution*.***[br]
+****Yes, I use this as a first-line fix once I know I've re-added the HP M426 I use this workaround on, but that printer has horrible firmware.***
[quote|format=featured]
Here is the registry set where the printers are in Windows: ***Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers - once you find it, delete everything but Microsoft Print to PDF.***
[/quote]
It will be located here in the registry. Just delete the entry, not the entire folder:
[image|3620845]

crwdns2915684:0crwdne2915684:0:

open

crwdns2934245:0crwdne2934245:0 Nick

crwdns2934249:0crwdne2934249:0:

-I have encountered this with HP printers that refuse to install correctly, notably the newer 2016+ HP DS models. It's really bad on the newer HP DS firmware, to the point I have had to reset one so many times that I check the behavior for a match, do a network reset, then issue it a new static IP, and then edit the port. The HP DS firmware has an awful network/print layer stack because HP focuses its energy on blocking third-party toner/ink, not a good network stack. AND IF the port edit doesn't fix it, I need to delete and re-add, and after so many, clear the registry of printer pileup.
+I have encountered this with HP printers that refuse to install correctly, notably the newer 2016+ HP DS models. It's really bad on the newer HP DS firmware, to the point I have had to reset one so many times that I check the behavior for a match, do a network reset, then issue it a new static IP, and then edit the port. The HP DS firmware has an awful network/print layer stack because HP focuses its energy on blocking third-party toner/ink, not a good network stack. AND IF the port edit doesn't fix it, I need to delete and re-add it, and after so many, clear the registry of any printer queue pileup.
-If it comes to a point the pileup is bad enough, deleting all of the printers except Microsoft Print to PDF is often how I have had to fix the fault one too many times. You need to purge the printers from the list, then re-add them from scratch. Y***ou need to reboot the system beforehand, which is a requirement because it's the only way to eliminate the mess. You should not have to do this regularly - if you do, your OS is partially broken, or the printer has hot garbage firmware.***
+If it comes to a point where the pileup is bad enough, UNINSTALLING THE EPSON DRIVER FIRST AND THEN deleting all of the printers except Microsoft Print to PDF is often how I have had to fix the fault one too many times. You need to purge the printers from the list, then re-add them from scratch. Y***ou need to reboot the system beforehand, which is a requirement because it's the only way to eliminate the mess. You should not have to do this regularly - if you do, your OS is partially broken, or the printer has hot garbage firmware.***
[quote|format=featured]
Here is the registry set where the printers are in Windows: ***Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers - once you find it, delete everything but Microsoft Print to PDF.***
[/quote]
It will be located here in the registry. Just delete the entry, not the entire folder:
[image|3620845]

crwdns2915684:0crwdne2915684:0:

open

crwdns2934245:0crwdne2934245:0 Nick

crwdns2934249:0crwdne2934249:0:

-I have run into this with HP printers, notably the newer 2016+ HP DS models which are infamously known for an unstable network stack where the only way to fix it is to reset the network config, get a new static IP and then delete the port (or rename it) and pray it works. And if it has issues you need to delete the printer and re-add it, possibly even the port if something goes wrong. The issue is when you do it enough, they do not clear out from the registry, so you need to force it out by deleting all printers from the registry, rebooting and then redo the installation process as if they were never on the system. ***You usually do not need this fix most of the time but sometimes you just need to force a rogue print queue out which breaks things.***
+I have encountered this with HP printers that refuse to install correctly, notably the newer 2016+ HP DS models. It's really bad on the newer HP DS firmware, to the point I have had to reset one so many times that I check the behavior for a match, do a network reset, then issue it a new static IP, and then edit the port. The HP DS firmware has an awful network/print layer stack because HP focuses its energy on blocking third-party toner/ink, not a good network stack. AND IF the port edit doesn't fix it, I need to delete and re-add, and after so many, clear the registry of printer pileup.
+
+If it comes to a point the pileup is bad enough, deleting all of the printers except Microsoft Print to PDF is often how I have had to fix the fault one too many times. You need to purge the printers from the list, then re-add them from scratch. Y***ou need to reboot the system beforehand, which is a requirement because it's the only way to eliminate the mess. You should not have to do this regularly - if you do, your OS is partially broken, or the printer has hot garbage firmware.***
[quote|format=featured]
Here is the registry set where the printers are in Windows: ***Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers - once you find it, delete everything but Microsoft Print to PDF.***
[/quote]
It will be located here in the registry. Just delete the entry, not the entire folder:
[image|3620845]

crwdns2915684:0crwdne2915684:0:

open

crwdns2934245:0crwdne2934245:0 Nick

crwdns2934249:0crwdne2934249:0:

I have run into this with HP printers, notably the newer 2016+ HP DS models which are infamously known for an unstable network stack where the only way to fix it is to reset the network config, get a new static IP and then delete the port (or rename it) and pray it works. And if it has issues you need to delete the printer and re-add it, possibly even the port if something goes wrong. The issue is when you do it enough, they do not clear out from the registry, so you need to force it out by deleting all printers from the registry, rebooting and then redo the installation process as if they were never on the system. ***You usually do not need this fix most of the time but sometimes you just need to force a rogue print queue out which breaks things.***
[quote|format=featured]
Here is the registry set where the printers are in Windows: ***Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers - once you find it, delete everything but Microsoft Print to PDF.***
[/quote]
-It will be located here in the registry:
+It will be located here in the registry. Just delete the entry, not the entire folder:
[image|3620845]

crwdns2915684:0crwdne2915684:0:

open

crwdns2934245:0crwdne2934245:0 Nick

crwdns2934249:0crwdne2934249:0:

-I have run into this with HP printers, notably the newer 2016+ HP DS models which are infamously known for an unstable network stack where the only way to fix it is to reset the network config, get a new static IP and then delete the port (or rename it) and pray it works. And if it has issues you need to delete the printer and re-add it, possibly even the port if something goes wrong. The issue is when you do it enough, they do not clear out from the registry, so you need to force it out by deleting all printers from the registry, rebooting and then redo the installation process as if they were never on the system.
+I have run into this with HP printers, notably the newer 2016+ HP DS models which are infamously known for an unstable network stack where the only way to fix it is to reset the network config, get a new static IP and then delete the port (or rename it) and pray it works. And if it has issues you need to delete the printer and re-add it, possibly even the port if something goes wrong. The issue is when you do it enough, they do not clear out from the registry, so you need to force it out by deleting all printers from the registry, rebooting and then redo the installation process as if they were never on the system. ***You usually do not need this fix most of the time but sometimes you just need to force a rogue print queue out which breaks things.***
-[quote|format=featured]Here is the registry set where the printers are in Windows: ***Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers - once you find it, delete everything but Microsoft Print to PDF.***[/quote]
+[quote|format=featured]
+Here is the registry set where the printers are in Windows: ***Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers - once you find it, delete everything but Microsoft Print to PDF.***
+[/quote]
It will be located here in the registry:
[image|3620845]

crwdns2915684:0crwdne2915684:0:

open

crwdns2934241:0crwdne2934241:0 Nick

crwdns2934249:0crwdne2934249:0:

I have run into this with HP printers, notably the newer 2016+ HP DS models which are infamously known for an unstable network stack where the only way to fix it is to reset the network config, get a new static IP and then delete the port (or rename it) and pray it works. And if it has issues you need to delete the printer and re-add it, possibly even the port if something goes wrong. The issue is when you do it enough, they do not clear out from the registry, so you need to force it out by deleting all printers from the registry, rebooting and then redo the installation process as if they were never on the system.

[quote|format=featured]Here is the registry set where the printers are in Windows: ***Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers - once you find it, delete everything but Microsoft Print to PDF.***[/quote]

It will be located here in the registry:

[image|3620845]

crwdns2915684:0crwdne2915684:0:

open