Unable to get Windows 11 24H2 upgrade successful through WSUS :/

Itsarapong Intoum 6 Reputation points
2024-10-10T03:52:48.05+00:00

So, I've tried to troubleshoot this issue by myself but none of the solution I tried help.

I've approved 24H2 update through WSUS for the specific group, put the client in the correct OU, the target version in GPO is set to 24H2 and the client detect the 24H2 in the Windows update.

However, during the download, it stops and say "We couldn't install some updates using the account you're signed in with" so I tried sign out and sign in with other account but then the client no longer detect the 24H2 update.

I've tried the following troubleshooting step:

Delete WSUS client from WSUS server.

Run net stop wuauserv

Run reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f

  • Run reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientIDValidation /f
  1. Run net start wuauserv
  2. Run wuauclt /resetauthorization /detectnow

Although WSUS server detect the WSUS client in the correct group the 24H2 update never show up to WSUS client anymore. when I run rsop.msc on the WSUS client it also receives the correct setting.

I've no issue upgrading Windows 10 to Windows 11 23H2 through WSUS.

In-place upgrade can be done through ISO file and Windows 11 installation assistant but I'm curious what's going on with the update through WSUS. After the in-place upgrade it detect the Cumulative update for 24H2 just fine though.

2024-10 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5044285) Already installed

Anyone have some idea?

Thank you in advance!

Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments
{count} vote

1 answer

Sort by: Most helpful
  1. Adam J. Marshall 10,356 Reputation points
    2024-10-10T10:34:47.11+00:00

    the target version in GPO is set to 24H2

    Why are you setting WUfB policies when you're controlling updates and upgrades through WSUS?

    You are likely setting yourself up with a dual scan scenario:

    https://www.ajtek.ca/wsus/dual-scan-making-sense-of-why-so-many-admins-have-issues/

    Also see:

    https://www.ajtek.ca/wsus/does-wuauclt-exe-detectnow-reportnow-work/

    as /detectnow is deprecated since Windows 10 and doesn't work.

    I can confirm following my 8 part blog series on How to Setup, Manage, and Maintain WSUS, approving an upgrade for 24H2 installs on supported systems that are 23H2 without any more interaction.

    https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-1-choosing-your-server-os/

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.