Exactly! I have 1 PC that is compatible and 1 that is not. I've skipped new releases before - Vista & Win8. I can do it again.
Type: Posts; User: nikki605
Exactly! I have 1 PC that is compatible and 1 that is not. I've skipped new releases before - Vista & Win8. I can do it again.
I took a similar path. As a home user with 2 PCs and 2 printers, I just replaced my old printers with new wireless models. I can access them from either PC without a problem through my router. No...
After reading this topic, I used show or hide updates - wushowhide.diagcab to hide KB5006670 until a resolution is found.
KB5005565 has several security patches and the majority are still in effect even with the Rpc registry patch added. Here is a good explanation of the effect this Rpc registry patch has with...
You are exactly correct. After adding the Rpc registry patch to my one PC (desktop) with the printers attached, I was able to print to them from my one client (laptop) PC.
The Rpc registry key did not previously exist at all. You won't find it. You have to manually add it, but it is only needed on the print server/host PC where the printer(s) are physically connected....
Exactly. Originally, I had uninstalled and hid KB5005565 so I could remote print. Because of the other security fixes in the update, I wanted it installed so that's why I went with the registry...
:thumbsup:
My concern is that the next cumulative update will remove this manual registry patch and we'll have to re-enter it.
Yup, I did the same thing. It's great to be able to print again.
You and I took exactly the same steps with exactly the same result. Glad it worked for you. :thumbsup:
Did the registry patch work for you TV2?
Yup, you will. Remember to restart the PC after adding the registry key, then test printing.
I found a registry patch that worked for me on my Windows 10 Pro PC.
Patch Tuesday was a bit rough this week : sysadmin
If you haven't rolled back the server update, try setting:
...
When I first noticed the print problem, I had KB5005565 installed on both the host and client PCs. I uninstalled the update from only the host PC and I was then able to print as before leaving the...
Sounds to me that they are not going to fix this problem. Both of my PCs were set up and the printers installed with administrator level user. In fact, both PCs only have one user and it is a local...
Long winded for sure. :chuckle: He basically said what we already know - uninstall it.
I watched the whole 27 minute video. He's got a real can of worms on his hands.
But we're still at the same place - uninstall the update from the print server machine and wait for Microsoft.
Both of mine are HP printers USB cabled to a desktop, networked to a laptop. With the update installed, I could print fine from the desktop where they are cabled, but I could no longer print to them...
Totally agree.
I downloaded the wushowhide.diagcab file and had it ready to go --> https://download.microsoft.com/download/f/2/2/f22d5fdb-59cd-4275-8c95-1be17bf70b21/wushowhide.diagcab
Uninstalled KB5005565 and...
I ran into the same problem after installing this update. I uninstalled it on the desktop PC where my printers are connected via USB cables. I was once again able to print over the network from my...
I kind of suspected that's what it was. ;)
For right now I'll go with option a) since the SFC found and corrected errors and see what happens. Thanks for your help and have a Merry Christmas.
Correct. This was the one and only BSOD I've had on this laptop in the 11 months that I've owned it.
- - - Updated - - -
The depot warranty runs to Jan 2023.
I changed the CCleaner...
Easy does it there.
1. You are firing instructions at me so quickly (which I appreciate) I'm having trouble keeping up.
2. I just figured out this morning how to make the .bat files run when...