Page 1 of 1

[RESOLVED] PENDING_UPDATES on different versions of Windows

Published: April 7, 2025 - 3:24 PM
by Laurent-Tecelys
Hello,
For several weeks now, we've had computers and servers stuck on "Pending_updates". We're running version 2.6.0.16881, Windows Server.
Some machines updated successfully, while others remain stuck. This isn't specific to the Windows version; it can happen with Windows 10, 11, Windows Server 2019, or Server 2022. I can't figure out what's causing this problem. I tried modifying the agent configuration, and three machines successfully updated, but now they're stuck again. Can anyone offer any advice?

Re: PENDING_UPDATES on different versions of Windows

Published: April 9, 2025 - 10:33 AM
by guigeek
Hello,
personally I don't use Wapt for servers but it seems to me to be the same problem as for Windows 11 versions in 24H2?

Re: PENDING_UPDATES on different versions of Windows

Published: April 9, 2025 - 1:11 PM
by Laurent-Tecelys
Yes, it's similar, except in my case it affects all versions of Windows client and server. To work around it, I disable Wua, remove all registry keys related to Windows Update, restart, and perform the updates from within Windows. The machines update normally. Then I re-enable Wua. My machines are up-to-date again and show an OK status in WAPT. In short, it's fortunate I don't have many machines, and I hope it won't be the same with the next cumulative update.

Re: PENDING_UPDATES on different versions of Windows

Published: April 9, 2025 - 2:12 PM
by sfonteneau
Hello,

we have just released version 2.6.0.17177 of wapt.

Changes have been made to the waptwua section to take into account the checkpoint-cumulative-updates concept

(https://learn.microsoft.com/fr-fr/windo ... ve-updates).

The problem you are experiencing may occur if the MSU installation fails because the checkpoint MSU is not located in the same folder as the MSU you are trying to install.

The current version also displays the "need reboot" status more clearly (indeed, we can't be certain the update was successful until the machine has restarted (since this new "checkpoint" concept)).

The machine should therefore appear as "NEED_REBOOT" and then as "NEED_SCAN" after rebooting.

We also noticed that some CABs only appear after installing and rebooting a previous CAB, for example, the "Cumulative Update for .NET Framework" (hence the importance of restarting) after installing a cumulative update.

Please let us know if you notice any improvements.

Re: PENDING_UPDATES on different versions of Windows

Published: April 9, 2025 - 2:49 PM
by Laurent-Tecelys
Thank you for your reply. I will try this and I will be sure to let you know how it goes.

Re: PENDING_UPDATES on different versions of Windows

Published: April 16, 2025 - 09:33
by Laurent-Tecelys
Hello,
Just a quick update.
After updating the WAPT server to version 2.6.0.17177 and after several restarts and checks for updates on workstations and servers, the updates installed successfully. My network is now up to date with the latest April patches.
Thank you.

Re: PENDING_UPDATES on different versions of Windows

Published: April 17, 2025 - 12:19 PM
by dcardon
Hi Laurent,

thanks for the feedback. I'm marking the topic as resolved. :-)

Regards,

Denis