Thank you so very much. I got despondent after the registry changes had no effect. Then I restarted the spooler and everything fell into place. I am so relieved.
The recent October 2021 security updates patching the PrintNightmare vulnerability broke network printing. You have to uninstall the updates, or wait for MS to fix it.
On your permanent fix, I could not understand the IP address thing, not sure which address you were doing but followed and understood though the point "Create basic task" then could not read what you typed, so I had to stop. Did not hear any vocals, that would help a lot but thanks for trying, at least you're doing more then MS, they did this to help sell Windows 11.
update kb:5006670, creates this problem . copy before update and replace after update (stop print spooler, and become the owner win32spl.dll) c:\windows\system32\win32spl.dll
I am getting ready to try this out on a client's PC. This problem has been plaguing them/me for days, but it has nothing to do with selecting a default printer on any of the PCs (including the one acting as the server). I simply can't connect to the printer in order to map it without the 0x00000709 error. It started with network PCs getting a notification that the driver needed an update, then they'd get the dialog box asking if they could trust the host PC and if they wanted to install the driver. When they click OK nothing would actually happen. So then if we tried to delete the mapped printer to reinstall it, we could never reinstall it without being stopped by 0x00000709 or "Windows couldn't connect to the printer. Check the printer name and try again. If this is a network printer, make sure that the printer is turned on, and that the printer address is correct." So frustrating. Feel like I've tried EVERYTHING. But I might not have tried this fix on the host PC, so I'm waiting for the user to go idle and I'll see what happens. If this works, I OWE YOU ONE. Regardless, thanks for posting this video! I'll try to report back if it's successful!
Hey, sorry guys! This problem was such a pain that I forgot all about checking back in because I spent so much time on the issue before solving it my own way. This video didn't really solve my problem, but it was still helpful! I went through Regedit, but the name was already correct. Changing it had no effect. However, going through permissions on registry keys and on the printer share, I just went crazy, granting permission to "Everyone" for Full Access. I also had to grant full access for "Everyone" on the system folders that hold the print queue and the printer drivers. It did seem like I had an issue with a driver conflict too, so it was complicated. In the end, this worked for the machine I was trying to fix, but the next day, the same thing happened to another machine on the network. Repeating all the same steps didn't seem to fix the other machine's issue with that shared printer, so ultimately, we replaced the printer with a true network printer so it didn't have to be shared through a PC (it was a Zebra label printer that they needed for special Veterinary Practice Management software). While taking the old printer out of service, I noticed that one end of the USB cable was bent and really worn out, so I intend to test the printer with a new USB cable, because I suspect the USB cable might be going bad and failing intermittently, and that's why network machines can't detect that the shared printer is connected to the network. Although I will say that manually deleting all drivers and then manually installing drivers that exactly matched the servers, and then manually connecting to the printer using "net" through command line showed some success too. In the end, though, sharing a printer through a PC on the network just wasn't worth it.
Just to let you know, MS did a worse underhanded thing when Windows 10 came out. They created a virus that blue screened Windows 7 users, I lost 3 hard drives proving it was MS's little toy. Put it on wiki and the entire page conversation was wiped.
update kb:5006670, creates this problem . copy before update and replace after update (stop print spooler, and become the owner win32spl.dll) c:\windows\system32\win32spl.dll
Windows10 update kb:5006670, creates this problem . copy before update and replace after update (stop print spooler, and become the owner win32spl.dll) c:\windows\system32\win32spl.dll
![Noob To Max With DRAGON REWORK In Blox Fruits [FULL MOVIE]](http://i.ytimg.com/vi/LnBMOinoOvA/mqdefault.jpg)
If you get any benefit from my video then please subscribe
Thank you so very much. I got despondent after the registry changes had no effect. Then I restarted the spooler and everything fell into place. I am so relieved.
good luck
The recent October 2021 security updates patching the PrintNightmare vulnerability broke network printing. You have to uninstall the updates, or wait for MS to fix it.
On your permanent fix, I could not understand the IP address thing, not sure which address you were doing but followed and understood though the point "Create basic task" then could not read what you typed, so I had to stop. Did not hear any vocals, that would help a lot but thanks for trying, at least you're doing more then MS, they did this to help sell Windows 11.
not working for me 0x00000709 still showing up
You will try perfect way I thing solved your problem..! I will use smoothly.
update kb:5006670, creates this problem .
copy before update and replace after update (stop print spooler, and become the owner win32spl.dll)
c:\windows\system32\win32spl.dll
@@rufatbadalov1858 any channel or tutorial video please?
@@anasrasheed2941 copy this file win32spl.dll before updating kb:5006670, and replace it after updating
@@anasrasheed2941 this file win32spl.dll can be taken from another system that has not been updated
I am getting ready to try this out on a client's PC. This problem has been plaguing them/me for days, but it has nothing to do with selecting a default printer on any of the PCs (including the one acting as the server). I simply can't connect to the printer in order to map it without the 0x00000709 error. It started with network PCs getting a notification that the driver needed an update, then they'd get the dialog box asking if they could trust the host PC and if they wanted to install the driver. When they click OK nothing would actually happen.
So then if we tried to delete the mapped printer to reinstall it, we could never reinstall it without being stopped by 0x00000709 or "Windows couldn't connect to the printer. Check the printer name and try again. If this is a network printer, make sure that the printer is turned on, and that the printer address is correct." So frustrating. Feel like I've tried EVERYTHING. But I might not have tried this fix on the host PC, so I'm waiting for the user to go idle and I'll see what happens. If this works, I OWE YOU ONE. Regardless, thanks for posting this video! I'll try to report back if it's successful!
so tried it ?
Any sign of success sir?
@Kevin Frey Did it work for you?
Hey, sorry guys! This problem was such a pain that I forgot all about checking back in because I spent so much time on the issue before solving it my own way.
This video didn't really solve my problem, but it was still helpful! I went through Regedit, but the name was already correct. Changing it had no effect. However, going through permissions on registry keys and on the printer share, I just went crazy, granting permission to "Everyone" for Full Access. I also had to grant full access for "Everyone" on the system folders that hold the print queue and the printer drivers. It did seem like I had an issue with a driver conflict too, so it was complicated. In the end, this worked for the machine I was trying to fix, but the next day, the same thing happened to another machine on the network.
Repeating all the same steps didn't seem to fix the other machine's issue with that shared printer, so ultimately, we replaced the printer with a true network printer so it didn't have to be shared through a PC (it was a Zebra label printer that they needed for special Veterinary Practice Management software).
While taking the old printer out of service, I noticed that one end of the USB cable was bent and really worn out, so I intend to test the printer with a new USB cable, because I suspect the USB cable might be going bad and failing intermittently, and that's why network machines can't detect that the shared printer is connected to the network.
Although I will say that manually deleting all drivers and then manually installing drivers that exactly matched the servers, and then manually connecting to the printer using "net" through command line showed some success too. In the end, though, sharing a printer through a PC on the network just wasn't worth it.
Not working
업데이트기록보기엔 있고
업데이트 설치제거에는 없으니 삭제할수가 없네요.
Just to let you know, MS did a worse underhanded thing when Windows 10 came out. They created a virus that blue screened Windows 7 users, I lost 3 hard drives proving it was MS's little toy. Put it on wiki and the entire page conversation was wiped.
still not working after doing 3 method
I will work properly..!
change the registry and reboot the printer name changes again
You will do delete all printer and driver then again install
not working sary method try krliye
Please try properly.
Thank you so much for this. You saved me
Good Luck...!
ready priner
not working why?
Please check your Task Schedule Script. That's 100% working. I will use properly.
update kb:5006670, creates this problem .
copy before update and replace after update (stop print spooler, and become the owner win32spl.dll)
c:\windows\system32\win32spl.dll
@@rufatbadalov1858
, Cc 1 by mistake
Xh cd free Ty
@@t.gdarbar1598 I did not understand you
@@rufatbadalov1858 Hey man, how do you do that exactly. Could you please make a step-by-step guide in the comment?
Method 1 Fail
You will try another Method
Windows10 update kb:5006670, creates this problem .
copy before update and replace after update (stop print spooler, and become the owner win32spl.dll)
c:\windows\system32\win32spl.dll
बेकार है तरीका
Audio ke sath bolo bhai
Thanks Next Video