Possible printer issue with KB5005565

Page 7 of 21 FirstFirst ... 5678917 ... LastLast

  1. Posts : 78
    Win 10 Pro Ver 21H2 OS Build 19044.1348
       #61

    ACDC said:
    Hi today update KB5005565 hes come thru even i blocked it 3 times. printer again is not working. i will look for theRpcAuthnLevelPrivacyEnabled on host pc tomorrow. on my pc there is no theRpcAuthnLevelPrivacyEnabled reg!?!? but it is not important for me because he is not sharing the printer!
    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. You do not need to add the registry key on the client PC.
      My Computers


  2. Posts : 21,421
    19044.1586 - 21H2 Pro x64
       #62

    smartcooky said:
    I am having this exact same problem.

    1. Printing to a network printer does not work - after a while, the print list window shows the job as "Access denied".

    2. I tried deleting and re-adding the printer... bad mistake, It would not even let me add the printer "Operation could not be completed error 0x0000011b".

    3. I came to this thread and found the information about KB5005565. I uninstalled the updates (had to do it on all the sending computers and the receiving computer).

    4. That seemed to fix it until the next day, when it happened again. Win 10 had updated and KB5005565 had been installed again. Grrrrr!

    5. Downloaded wushowhide.diagcab and hid KB5005565 from updates, but within a few days, it ignored my ignore and updated again!

    6. I have currently put all updates on pause until this issue is resolved.

    Do Microsoft ever bother to actually check if these updates are going to cause issues before unleashing them on the unsuspecting public. With several computers and network printers to manage, this has caused me a lot of extra work I could have done without.

    - - - Updated - - -



    Its the lesser of two evils. Choose between

    (a) Lose out on whatever KB5005565 has to offer.

    (b) Spend all day running around several computers (all of which are used full time, 8am to 6pm six days a week) trying to get their operators to give me an hour to fix it. This involves the operator saving all their work, closing off their job cards and logging out of their computer. Then I have to login, uninstall KB5005565 and restart. Once that is done, and I confirm its all working, I can hand the computer back to the user, and go to the next user and repeat the process. I have to do that another five times


    I choose (a)
    How many printer servers do you have? The registry fix only needs to be applied to the printer server PC, not the clients - based on my understanding - but I haven't experienced the problem myself.
      My Computer


  3. Posts : 78
    Win 10 Pro Ver 21H2 OS Build 19044.1348
       #63

    steve108 said:
    How many printer servers do you have? The registry fix only needs to be applied to the printer server PC, not the clients - based on my understanding - but I haven't experienced the problem myself.
    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.
      My Computers


  4. Posts : 221
    Windows 10 Pro 64 bit (22H2)
       #64

    steve108 said:
    How many printer servers do you have? The registry fix only needs to be applied to the printer server PC, not the clients - based on my understanding - but I haven't experienced the problem myself.
    nikki605 said:
    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.
    We have only one computer that hosts shared printers on it. However, I have found that even if it does not have KB5005565 on it, if a client computer has that update, it will not print. I have therefore had to remove KB5005565 from all the computers on the network.

    Just for clarity, I have not yet tried the registry fix, but it looks promising, and I will try it later today.

    If I have understood correctly, On the printer host computer only, I go to...

    HKEY-LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print

    ...and look to see if the key RpcAuthnLevelPrivacyEnabled exists, and if does, set its DWORD value to 0, and if doesn't exist, create it, and set its DWORD value 0

    Then I can un-pause updates of all the computers to allow KB5005565 to install the next time updates are installed.

    Correct?
      My Computers


  5. Posts : 21,421
    19044.1586 - 21H2 Pro x64
       #65

    smartcooky said:
    We have only one computer that hosts shared printers on it. However, I have found that even if it does not have KB5005565 on it, if a client computer has that update, it will not print. I have therefore had to remove KB5005565 from all the computers on the network.

    Just for clarity, I have not yet tried the registry fix, but it looks promising, and I will try it later today.

    If I have understood correctly, On the printer host computer only, I go to...

    HKEY-LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print

    ...and look to see if the key RpcAuthnLevelPrivacyEnabled exists, and if does, set its DWORD value to 0, and if doesn't exist, create it, and set its DWORD value 0

    Then I can un-pause updates of all the computers to allow KB5005565 to install the next time updates are installed.

    Correct?
    Yes, that's my understanding, but I would install the KB5005565 on the printer server, reboot the printer server, make the registry change on the printer server, reboot the printer server, then confirm printing still works from a single test client. Then install KB5005565 on that client, reboot, and confirm printing still works. That should be a good test for you to see this workaround is working.

    Note you have a erroneous "-" vs "_" in the path above.
      My Computer


  6. Posts : 221
    Windows 10 Pro 64 bit (22H2)
       #66

    OK, so I have...

    1. Uninstalled KB5005565 on the host computer

    2. Made the necessary registry change as per Nikki605's post #41

    3. Restarted the host computer.

    4. On restart, I checked Settings > Update&Security and found that KB5005565 was Pending install, so I clicked Install

    5. When it finished installing, it prompted a restart so I did that (it restarted a couple of times as it does sometimes when doing updates)

    6. Tested both printers from client computers.

    FIXED - Thank you Nikki605

    So as I understand it, all the client computers have KB5005565 installed and they are fully protected against the vulnerability it addresses, but the host computer, while it also has KB5005565 installed, is not protected because of the registry hack.

    Do I have that right?
      My Computers


  7. Posts : 78
    Win 10 Pro Ver 21H2 OS Build 19044.1348
       #67

    smartcooky said:
    OK, so I have...

    1. Uninstalled KB5005565 on the host computer

    2. Made the necessary registry change as per Nikki605's post #41

    3. Restarted the host computer.

    4. On restart, I checked Settings > Update&Security and found that KB5005565 was Pending install, so I clicked Install

    5. When it finished installing, it prompted a restart so I did that (it restarted a couple of times as it does sometimes when doing updates)

    6. Tested both printers from client computers.

    FIXED - Thank you Nikki605

    So as I understand it, all the client computers have KB5005565 installed and they are fully protected against the vulnerability it addresses, but the host computer, while it also has KB5005565 installed, is not protected because of the registry hack.

    Do I have that right?
    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 KB5005565 installed:

    How to fix the Windows 0x0000011b network printing error
    Last edited by nikki605; 28 Sep 2021 at 08:05.
      My Computers


  8. TV2
    Posts : 2,221
    W10 Pro 22H2
    Thread Starter
       #68

    I believe that the Host PC will be vulnerable to an attack that utilizes the Point And Print vector as it's way in.
    The registry change does not enforce the security fix.
    The registry change allows us to print as we want to, but it is a workaround rather than a fix.
    We (I) are hoping for Microsoft to recognize this as a problem and devise a fix that allows both printing as we do and security.
    Hopefully in a future update.
      My Computers


  9. Posts : 2
    Windows
       #69

    What if you don't have RpcAuthnLevelPrivacyEnabled in the registery?
      My Computer


  10. Posts : 21,421
    19044.1586 - 21H2 Pro x64
       #70

    RCSCole said:
    What if you don't have RpcAuthnLevelPrivacyEnabled in the registery?
    Create it, as previously posted, and set it to 0.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:00.
Find Us




Windows 10 Forums