Pb wapt et windows 11 ltsc

Share your tips or issues concerning the WAPT Console or WAPT Agent here
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
User avatar
dcardon
WAPT Expert
Messages: 1930
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

October 8, 2025 - 10:35

Hi Irving,

we've added a Windows 11 LTSC 2024 to our test farm in the meantime, and I haven't been able to reproduce any issues with waptexit. Did

the Citrix Workspace package you have come from the wapt store? If so, the problem likely stems from one of the executables being listed in the package's impacted_process attribute.

When installing a wapt package, if one of the processes mentioned in the impacted_process attribute is still running, the wapt agent won't perform the installation. This allows updates to be performed during the day without killing user-launched applications.

However, it seems there are some extra processes in the list. Could you please check which processes are actually being launched by the user and which are coming from background servers? Or, if you don't perform automatic daytime updates, you can simply remove all the values ​​mentioned on the `impacted_process` line. This will prevent a resident process from blocking the update.

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
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

October 29, 2025 - 10:44 PM

For your information, we have added Windows 10 LTSC and Windows 11 LTSC to the LUTI farm for even more testing

; however, the tis-citrix-workspace-ltsr package is now available here.
Answer