Server 2025 Domain Controllers - Trust relationship issues on workstations after 30 days as "pwdLastSet" value unable to be updated

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.

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.

I had it. Time was not sync in the domain

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,

Hi Daisy

I'm sorry but are you telling me i have to use the consumer "Feedback Hub" to report this rather than you escalating it to the engineers to rectify with all the information from this thread?

We have done most of the legwork to find what is a very big issue and it sounds like you then also want us to then use a non escalated route to get it to the programmers at Microsoft who will need to rectify it? If so that's beyond ridiculous, you need to be escalating it at this point not us.

Best regards

Erin