Trouble with PrincipalContext.ValidateCredentials After Windows 11 24H2 Update

0
4
Asked By CuriousCoder42 On

Hey everyone! I've been relying on a PowerShell function to validate domain accounts, and it's been working great until I updated to Windows 11 24H2. Here's a quick look at my function: I use the PrincipalContext.ValidateCredentials method to check user credentials. The odd thing is, after the update, it always returns false, regardless of the credentials or domain I use. It's worth noting that everything was running smoothly in Windows 10 and in Windows 11 up to version 23H2. Does anyone know what might have changed or how I can fix this issue?

2 Answers

Answered By PowerShellPal99 On

It sounds like you might be hitting a change related to NTLM in the 24H2 update. NTLM is disabled by default now, so try using the User Principal Name (UPN) instead of the NetBIOS username format. That could help fix your validation issue.

Answered By AuditNinja On

Don't forget to check your audit logs to see if you can get more insight into why the access is failing. It might point you in the right direction!

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.