Share via

Remote Desktop Connection stuck at "Local session manager" on OS windows Server 2012 R2

Anonymous
2023-09-19T01:36:29+00:00

Hi All,

After August 2023 updates I'm unable to launch file explore and said no permission granted.

after i uninstall august windows update i'm able to launch. just to check is there any hot fix for this?

Windows for business | Windows Server | Devices and deployment | Install Windows updates, features, or roles

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

9 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-09-28T07:25:57+00:00

    Hello

    Have you changed any security settings in the group policy hardening template?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2023-09-27T03:08:01+00:00

    Hi Xiuyun Lian,

    i tried to troubleshoot the following but unable to resolve the issue.

    however, I noticed if i removed the group policy hardening template and try performing the remote desktop is working well.

    any idea which is the policy cause it?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2023-09-27T02:50:33+00:00

    hi Xiuyun Lian,

    any updates?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2023-09-21T07:34:18+00:00

    Hello

    As you describe, the August update is the crux of the matter.

    Did you download the September update? The patch number is KB5030269. Later updates will fix some issues in previous updates, please try to install if you didn't download.

    Install the update manually under this link: Microsoft Update Catalog

    Enter the patch number in this box:

    Reference: September 12, 2023—KB5030269 (Monthly Rollup) - Microsoft Support

    Best regards,

    Hania Lian

    1 person found this answer helpful.
    0 comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more