BillInAustin's avatar
BillInAustin
Brass Contributor
Oct 09, 2024
Status:
Closed

Windows App drops connection with 407 Encryption error

This has been a recurring problem since updating to macOS 15.0.1. Running Windows App to connect to a Windows 11 laptop on the same local network I'm seeing repeated connection drops with the same popup: "Your session was disconnected - Your session ended because of a data encryption error. If this keeps happening, contact your network administrator for assistance. Error code: 0x407.

 

This is continuing with the latest Windows App update (11.0.5 Build 2401). It also happens with the release level of Windows App. This makes Windows App barely usable since connections are constantly being dropped every few minutes.

5 Comments

  • Status changed:
    New
    to
    Closed

    This forum is focused on Azure Virtual Desktop Feedback. The Windows App feedback has transitioned to https://aka.ms/app_WindowsAppFeedback. If you are running into issues, we recommend to share your problem on our Tech Community forum (https://aka.ms/wvdtc) or open a support ticket after you have reviewed the troubleshooting options in our documentation (Windows Virtual Desktop troubleshooting overview - Azure | Microsoft Docs)

  • BillInAustin's avatar
    BillInAustin
    Brass Contributor

    Looks like this is fixed in macOS 15.1. I installed it this morning, turned the macOS firewall back on and so far Windows App has been solid as usual.

  • BillInAustin's avatar
    BillInAustin
    Brass Contributor

    Thank you! I've tried this and so far so good. Related to this I noticed that Time Machine failed when trying to back up to a time machine share located on my local NAS and have an issue open with Apple about this. This is excellent information that I'll pass along to them. Sounds like they tweaked the firewall in 15.0.1 and that has inadvertently affected some network-sensitive applications.

  • MatthewP1605's avatar
    MatthewP1605
    Copper Contributor

    I am seeing the same thing.  The only fix I've had work is to disable the MacOS firewall.  Even though the application itself is in the allowed Inbound rules.  This is not something we want to do with our users.