![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 78%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHS%3C/text%3E%3C/svg%3E)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(172.8, 86%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJT%3C/text%3E%3C/svg%3E)
Hi Harjeet Sandhu,
Several users have reported similar issues with Windows Server 2025 following the September and October security patches. Specifically, the updates appear to disrupt authentication to remote file shares and trigger LSA (Local Security Authority) errors. Microsoft has acknowledged these as known issues and is actively investigating them.
In the meantime, some administrators have found temporary relief by rolling back the affected updates or disabling certain security hardening features introduced in the patches. However, these steps should be evaluated carefully in the context of your environment’s security posture. I recommend checking the official Windows Server 2025 Known Issues and Workarounds page for the latest guidance and mitigation steps.
If this response helps clarify the situation, feel free to hit “Accept Answer” so others can benefit too 😊. And of course, let me know if you'd like help implementing any of the workarounds or exploring alternative solutions.
Jason,