This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi
We have 4 Domain controllers upgraded to server 2025 and about 30+ still on 2022. The newly upgraded servers appear to have a bug where by any workstations going through them are unable to update their "pwdLastSet" value and so after the 30 day limit on that field is hit they then fall into a trust relationship issue with the domain. Is this a known bug of server 2025? Are there any known fixes for this issue?
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.
Hello,
I am having the same issue with a newly installed 2025 Server.
Additionally, I'm now having an issue when a new user account is created with the option "User must change password at next login" selected it just endlessly loops asking for a new password to be entered when the user attempts to log in for the first time.
Has anyone else come across this with Server 2025?
Thanks,
I had it. Time was not sync in the domain
We are experiencing exactly the same issue. Currently, we are managing by manually resetting the machine passwords. In parallel, we have removed the 2025 domain controllers from the domain. We cannot yet confirm whether this has resolved the problem.
The same behaviour continues on our environment where on my 2 test machines 23H2 breaks every 24/48 hours but 24H2 continues to work. My colleagues Test environment also behaves in the same way where 23H2 breaks but 24H2 (upgraded from 23H2) and 24H2 direct builds work correctly. Also within our production environment i have seen Windows 10 and iMacs embedded into windows continue to work as expected so I'm fairly confident its a 23H2 bug. I cant be 100% sure that there aren't other bugs that then also effect other operating systems but to me 23H2 is the most affected in our instance.
Unfortunately the sites where I moved our DC's onto 2025 were primarily 23H2 because i had been delaying 24H2 due to all the bugs that Microsoft were fixing which is ironic (though from what i have read of the bugs i don't think they will effect us greatly). I am moving all of our 23H2 clients up to 24H2 now as i think this is likely to help at the very least as 24H2 and 2025 are based upon the same underlying operating system build.
I can only confirm this behavior. Windows 10 machines are fine, Windows 11 24H2 is also fine. Only Windows 11 23H2 is affected by this. Forest and Domain level are not affecting this. One Domain is upgraded to 2025 level, the other one is still on 2016 level and both have the Problem, so its purely Server 2025 and Windows 11 23H2 in conjuction.
