WUA positions remain pending

[Emmanuel64]

Good morning

I have several workstations in WUA testing before the total migration from WSUS of all workstations.

For example, I have KB5058411 marked as "Pending" on a few machines

On the server, this KB is:
is required: False
Downloaded: 2025-05-27T02:38:04.702476

The job description:

Code: Select all

[waptwua]
enabled=true
install_at_shutdown=true
download_scheduling=4h
allowed_severities=Critical
install_delay=15d
default_allow=true

What could be the reason why they are not settling?

THANKS

PS: If I run the installation manually, it works

[sfonteneau]

Hello,

is the computer showing as "pending reboot" in the Windows Update tab?

Simon

[Emmanuel64]

Hello,

thank you for your reply.

No, it's in PENDING_UPDATES.

[sfonteneau]

So, nothing like in the screenshot here.

Logically, if you launch the installer (right-click on the machine, run the Windows update installation),

the machine will go into "Pending reboot" mode and the cab will remain in "PENDING" mode while waiting.

After rebooting, the machine will go into "need scan" mode (to verify that everything is OK)

, and the cab should appear as OK.

[sfonteneau]

Ah, I hadn't seen your message "PS: If I launch the installation manually, it works."

Actually, in this case, you're missing the "install_scheduling=2d" parameter in the waptwua section.

The "install_at_shutdown=true" parameter no longer works because Windows now (for the past 24 hours) returns an error if we try to install while shut down.

[Emmanuel64]

This is indeed the behavior when I update manually.
The problem arises with the update on shutdown, since that's the behavior requested by "install_at_shutdown=true".

[sfonteneau]

Ah, I hadn't seen your message "PS: If I launch the installation manually, it works."

Actually, in this case, you're missing the "install_scheduling=2d" parameter in the waptwua section.

The "install_at_shutdown=true" parameter no longer works because Windows now (for the past 24 hours) returns an error if we try to install while shut down.

[Emmanuel64]

Here's the reasoning behind it:
When setting 2d, for example, we base it on 48 hours, from what point? (Update received or 00:01 of the day?)
Those sudden 24h2 updates in the middle of work are rather annoying (it always happens during a presentation or a video conference... Otherwise, it wouldn't be any fun ).

[sfonteneau]

If we use 2d for example, from what point do we base it on 48 hours? (from the receipt of the update or 00:01 of the day)?

Actually, the service checks in a loop (every minute, for example). If it hasn't checked for more than 48 hours, it starts the next check

The barbaric 24h2 updates in the middle of work are rather annoying (it's always during a presentation or a video call... Otherwise it's not funny )

Technically it does not reboot the machine (at least wapt does not reboot and asks waptwua not to reboot) and it does not close any application.
However, it does increase CPU usage during installation.

[Emmanuel64]

Thank you for all this valuable information