Re: Pb wapt and windows 11 ltsc
Published: October 8, 2025 - 10:35 AM
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
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