Forum Discussion

thekidla's avatar
thekidla
Copper Contributor
Apr 14, 2025

KB5055528 Breaks RDP

Hello All,

Looks like there is a bug with KB5055528. Once applied it break inbound RDP. Session prompts for user/pass then immediately disconnects. Once uninstalling the KB, RDP connections work fine. Anyone have a workaround or a new setting that I should be aware of?

Other notes:
- I see the Audit Success in Event Viewer
- I see Session 2 has been disconnected, reason code 17 in TS logs

11 Replies

  • Csand's avatar
    Csand
    Copper Contributor

    I can barely believe it, but it seems as of cumulative update KB5060999 (June 10) they have fixed this issue. Anyone else have a similar result?

    • rhizoid's avatar
      rhizoid
      Copper Contributor

      Currently logged in remotely with KB5060999 installed, appears to have fixed my problem above.  I was on my way to the office specifically to switch updates back on to test a potential fix (in place upgrade/repair) so very glad I didn't need to.  Thanks for the update!

      • DutchD's avatar
        DutchD
        Copper Contributor

        Thanks, after i got a notification this thread had updates I re-enabled updates and got KB5060999 installed. RDP is indeed no longer broken :-)

  • dz890's avatar
    dz890
    Brass Contributor

    Is Microsoft going to admit this is a problem?  It still isn't listed in the KB's "Known Issues".

    Acknowledge this is a problem Microsoft and FIX IT.

    • Csand's avatar
      Csand
      Copper Contributor

      Same issue here, exactly down to the reason code 17. 0x3 and 0x11 on the client side. There is no fix currently and all you will find on the internet is the same old generic answers. I work with M$ at an enterprise level, and the senir techs I have asked there had no idea what I was talking about.

      You can remove KB5055528. But guess what! The issue comes back with Cumulative update KB5058405, and will continue to come back in every subsequent cumulative update until they acknowledge and fix this issue.

      So yea. We are stuck at "simply don't do updates" for the foreseeable future.

       

      GOOD TIMES.

       

      Linux looking nicer and nicer every year, ffs.

  • rhizoid's avatar
    rhizoid
    Copper Contributor

    I've seen the same behaviour, with the update installed RDP connections are created as normal and immediately terminated with a logoff entry in the security event log.

    Attempts to work around this by reinstating Remote Desktop connection settings failed, a last resort of uninstalling KB5055528 has restored RDP functionality.

    I checked the list of files in the update and note that MSTSC is mentioned several times, the version number given already matches the installed version on my system before the update.

    • thekidla's avatar
      thekidla
      Copper Contributor

      Glad I am not the only one. I was racking my brain over here.

      I really don't want ot have to pause updates to get this working, but I guess that's what I'll do until MS patches it.

  • DutchD's avatar
    DutchD
    Copper Contributor

    Seen the same issue after installing this kb. Under settings allow remote connections is checked and NLA is enabled. After rollback all works ok again as TS mentioned.  Any other things i can try/check?

  • DutchD's avatar
    DutchD
    Copper Contributor

    Hi encountered the same issue after installing this kb. Under settings Remote connections are allowed and NLA is enabled.

    After roll back all works fine as TS mentioned. Someone has any other idea to try/check?

    Thanks.

  • DeclanGray's avatar
    DeclanGray
    Iron Contributor

    Ensure that the option Allow remote connections to this computer is checked, and under the Advanced tab, verify that Network Level Authentication is enabled or disabled based on your setup.

    • Csand's avatar
      Csand
      Copper Contributor

      This is a non answer, if you don't know about this specific error, please don't muddy the waters with generic answers

Resources