aac

Hi there I am having the same issue here. We have set a test user to NOT ADULT but the issue remains. Any ideas?

Cool, let us know please if Microsoft get anywhere with it. They must have known this issue existed for a a long while now...

See the script below. I just added it in the software library/scripts section of SCCM then just run it on affected machines each month. Even if it says password rotation for machine failed after running on affected machine just reboot the affected machine and you will see it worked fine. I personally don't think 25h2 fixes anything but reimaging an affected machine does. Unfortunately in my scenario I just don't have time ATM to reimage the affected machines some of which have a few extra apps to install after reimaging so I will just run the script for now as I am building a new image and will reimage all machines later... try { Write-Host "Starting machine password rotation..." Write-Host "Running as: $(whoami)" # Define credentials (plain text password converted to SecureString) $Username = "domain\username" # Replace with your delegated account $Password = ConvertTo-SecureString "password" -AsPlainText -Force $Cred = New-Object System.Management.Automation.PSCredential ($Username, $Password) # Specify a domain controller explicitly $DomainController = "test.domain.internal" # Replace with your DC name # Reset the machine account password using provided credentials Reset-ComputerMachinePassword -Server $DomainController -Credential $Cred -Verbose # Verify secure channel if (Test-ComputerSecureChannel) { Write-Host "Machine password successfully rotated." Exit 0 } else { Write-Host "Password rotation failed: Secure channel test failed." Exit 1 } } catch { Write-Host "Error rotating machine password: $($_.Exception.Message)" Exit 1 }

Hi there your not alone with this. We had a 2019 and a 2025 DC and issues with group policy not applying so in the end to resolve the group policy issues we upgraded the 2019 DC to 2025 and that sorted it but to this day we are still finding some machines do not rotate machine password and therefore loose trust with the domain thus I am having to run a script on these machines monthly to rotate the passwords manually. Even if it has already lost trust with the domain it still works and saves a trip to the machine re-joining manually...

Thanks, that has verified secure channel is fine on my domain.

How did you fix secure channel please?

repadmin/showrepl shows mine seem to be replicating without issue. I have made a few changes in AD and these appear to be reflected on the replication partner. Is it possible you had issues with replication prior to making the above changes?

I have made these changes and will monitor for a while. Fingers crossed...

Still ongoing issues here, has anyone come across a fix or even a workaround other then to demote the 2025 DC?

Its really frustrating they have not sorted this issue out yet, it really isn't a good look. I have a few servers running 2025 and every one of them has been fine apart from the DC.

We were still seeing the same issue after July Cumulative update was installed on Win 11 24h2 machines and 2025 DC. Have just upgraded to August Cumulative update but not confident it is going to fix it.

Were still having strange issues here and have one 2019 and one 2025 DC. We are finding that sometimes you will boot up a PC and it states the username and password is correct even though we know it is 100% correct. Reboot again and it logs in fine, it is a bit random of an issue...

Hi all I am looking to lock down my Intune devices so that only users in a specific Azure AD group can logon to Intune managed devices. Has anyone achieved this as I have spent days looking into how this can be done but have yet to find a way that works...

I also suspect the 2025 DC, absolute disgrace Microsoft have not yet sorted out these issues. I am not confident that the August 2025 Cumulative update will resolve either...

Hi all We are seeing a strange issue on our machines most of which are running Windows 11 Education 24h2. Every now and again a user will try to login and it will state the username and password are incorrect however after a reboot they login fine. While we do have some machines still on 23h2 we have only seen this issue on the ones running 24h2. We have 2 domain controllers one 2019 and one 2025 and both DC's have the July Cumulative update installed on them...