Share via

Remote desktop licencing has failed with Event 37

Anonymous
2024-05-01T13:17:57+00:00

Remote desktop licensing has failed with Event 37. I have tried many fixes already described. Changed the permissions for the terminal services licencing in the registry and also on the windows Lserver directory. I have checked the event log and the first error appeared on 14/4 just after a microsoft update. Tried uninstalling the update which didnt seem to solve the problem.

We have Windows Server 2016.

The RDS is still working. Will it keep working or do I have to solve the problem. Will it be solved with a future microsoft update?

Windows for business | Windows Server | User experience | Licensing for Azure Virtual Desktop

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-05-02T00:14:08+00:00

    Hello,

    It's positive that your RDS environment is still operational. If this issue is indeed linked to the latest update, consider submitting feedback about it. Checking if others have experienced similar issues in the Feedback Hub. With the increase in reported issues, this could grab the attention of engineers.

    Image

    Microsoft regularly releases updates and patches to address known issues and improve the functionality of their products. So, it's possible that a future update may resolve the issue.

    Regards,

    Karlie

    0 comments
  2. Anonymous
    2024-11-18T07:21:09+00:00

    Have you found out the cause of the problem and how to solve it?
    I am facing the same problem now - after the Windows Updates November.

    0 comments
  3. Anonymous
    2024-11-18T07:29:24+00:00

    NO. Just keep getting the same message but RDS is still working so I havent wasted any more time trying to sort out why it is happening.

    0 comments