Group Policy updates appear to fail after installing the September preview update KB5124010 on Windows 11 25H2 machines using a Microsoft Security Baseline. The logs can look like a domain trust problem. What should I check?
Could KB5124010 be breaking Group Policy with the Windows security baseline?
Answers
The baseline is worth testing, especially if removing the preview restores Group Policy processing. One reported investigation narrowed the problem to a setting in the Windows 11 25H2 security baseline, but the available details do not identify the exact setting or registry value reliably enough to recommend changing it.
Use a test VM with a snapshot and place it in an OU with inheritance blocked. Confirm policy updates work with the preview installed and only minimal policies applied, then add the baseline policies back in small groups until the failure returns. That gives you something concrete to investigate rather than treating the trust message as proof of a broken domain relationship.
Reply to this answer
If you need a short-term recovery step, test removing the preview update from an affected machine and rerun gpupdate /force. The reported case returned to normal after removal. That is a workaround, not proof that every policy failure has the same cause.
3c!harborpiston_275:
Unlinking the baseline was also mentioned as a temporary measure, though machines that cannot process Group Policy may be difficult to reach that way.
Reply to this answer
Don't assume the policy is absent just because your editor doesn't show a friendly name for it. In the reported investigation, it appeared as a registry string in the editor on a Server 2022 system, while an editor installed on Server 2025 could display the setting. Check what your management tools actually expose before deciding the baseline templates are at fault.
Reply to this answer
Be careful about copying a registry workaround from a partial description. A value change was reported to restore processing in some cases, but the key and setting are missing here. Identify the setting in your own test and understand its security impact before changing it.
It would also be useful to report a reproducible test and logs to Microsoft, including the Windows version, update, baseline and the smallest policy set that triggers the failure.
Reply to this answer
Add your answer
Answers are reviewed before publication.
4s+drainpuzzle_816:
Check both client and domain controller logs during the test. A trust-related error can be misleading if other checks show the trust is intact.