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?
[RESOLVED] PENDING_UPDATES on different versions of Windows
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
Laurent-Tecelys
- Messages: 6
- Registration: Apr 03, 2025 - 11:59
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.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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.
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.
-
Laurent-Tecelys
- Messages: 6
- Registration: Apr 03, 2025 - 11:59
Thank you for your reply. I will try this and I will be sure to let you know how it goes.
-
Laurent-Tecelys
- Messages: 6
- Registration: Apr 03, 2025 - 11:59
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.
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.
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Laurent,
thanks for the feedback. I'm marking the topic as resolved.
Regards,
Denis
thanks for the feedback. I'm marking the topic as resolved.
Regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
