Can you clarify the problem?
Is it the installation that's failing? (Note that a reboot is required after installation for the cab to be recognized as installed.)
[RESOLVED] WAPTWUA on 24H2
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello
, yes, this is new. We had to remove the option because of Windows.
Now, if we launch the Windows Update engine while it's stopped on a 24/7 server to start the installations, the engine responds "impossible, stopping in progress."
The workaround is to use "installation scheduling" -> for example: install_scheduling=1d. The installations will then take place during the day (no other option).
, yes, this is new. We had to remove the option because of Windows.
Now, if we launch the Windows Update engine while it's stopped on a 24/7 server to start the installations, the engine responds "impossible, stopping in progress."
The workaround is to use "installation scheduling" -> for example: install_scheduling=1d. The installations will then take place during the day (no other option).
Hello,
I'm still having trouble, particularly with KB5053598.
On some machines, I managed to install it, but on others, it seems to install, but it doesn't show up as installed despite several reboots.
On other machines, I even manually pushed the KB, but it's the same; it doesn't show up as installed afterward. However, on some machines, it works...
It's very strange; I can't understand why it works on some machines and not on others...
Have you had any other feedback?
Thank you.
I'm still having trouble, particularly with KB5053598.
On some machines, I managed to install it, but on others, it seems to install, but it doesn't show up as installed despite several reboots.
On other machines, I even manually pushed the KB, but it's the same; it doesn't show up as installed afterward. However, on some machines, it works...
It's very strange; I can't understand why it works on some machines and not on others...
Have you had any other feedback?
Thank you.
Actually, after analyzing which machines are working and which aren't, I realize it seems to be a display issue:
the machines that remain in PENDING despite manually installing the KB still appear as version 10.0.26100.3476 [24H2].
So, everything seems to be okay, except that it shows some updates still need to be installed.
Any idea where the problem might be coming from?
Thanks!
the machines that remain in PENDING despite manually installing the KB still appear as version 10.0.26100.3476 [24H2].
So, everything seems to be okay, except that it shows some updates still need to be installed.
Any idea where the problem might be coming from?
Thanks!
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello,
I was looking here (still on 24h2).
The 24h2 installation is done with DISM (a new method to work around 24h2 bugs). When installing with DISM, if you run a scan again, the Windows Update engine still considers the KB to be uninstalled. After restarting the Windows machine, if you run another scan, it then considers the KB installed.
On your end, after rebooting and rescanning, is it working correctly?
I was looking here (still on 24h2).
The 24h2 installation is done with DISM (a new method to work around 24h2 bugs). When installing with DISM, if you run a scan again, the Windows Update engine still considers the KB to be uninstalled. After restarting the Windows machine, if you run another scan, it then considers the KB installed.
On your end, after rebooting and rescanning, is it working correctly?
No, not on all positions.
The KB is still PENDING, but the displayed Windows version is indeed 10.0.26100.3476 [24H2] (So the KB should be installed)
I've done several reboots and rescans... but for now it only represents a minority of the workstations.
The KB is still PENDING, but the displayed Windows version is indeed 10.0.26100.3476 [24H2] (So the KB should be installed)
I've done several reboots and rescans... but for now it only represents a minority of the workstations.
- Screenshot 2025-03-14 163325.png (26.98 KB) Viewed 21718 times
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
I just noticed that in your screenshot your Windows version is 26100.3476
https://support.microsoft.com/en-us/top ... 99f551cec2.
So the version looks correct, but Windows Update reports that it's not installed. I would have suggested rebooting and then running another scan, but you've already done that.
You should also check if the KB update appears in the Software Inventory by searching for 5053598.
Alternatively, you could try a forced inventory update to be sure.
Could you also clean the C:\Windows\SoftwareDistribution folder and then run another scan?
https://support.microsoft.com/en-us/top ... 99f551cec2.
So the version looks correct, but Windows Update reports that it's not installed. I would have suggested rebooting and then running another scan, but you've already done that.
You should also check if the KB update appears in the Software Inventory by searching for 5053598.
Alternatively, you could try a forced inventory update to be sure.
Could you also clean the C:\Windows\SoftwareDistribution folder and then run another scan?
