Page 1 of 1

[SOLVED] Package does not appear

Published: July 18, 2025 - 09:30
by fredemme
Hello,
I downloaded the Office 2024 LTSC package and added it to the SELF list.
In the CONFLICT section, there are previous versions of Office
listed:

tis-microsoft-access-2016-runtime,
tis-microsoft-office-2016,
tis-microsoft-office-2013
, tis-microsoft-office-365-enterprise
, tis-microsoft-office-2019-standard,
and tis-microsoft-office-2021-standard.

On a new machine, the Office 2024 LTSC package appears in the SELF list.
On a machine with Office 2016 installed, the package does not appear.

Is this because of the CONFLICT section? I thought this section was for uninstalling older versions.

Re: Package not appearing

Published: July 18, 2025 - 1:45 PM
by sfonteneau
Good morning

In an administrator command prompt on the machine, can you execute the following command:

Code: Select all

wapt-get search office --direct
to see if the package is visible

Re: Package not appearing

Published: July 21, 2025 - 10:06 AM
by dcardon
Hello Frédérique,

if the Office 2016 package is a dependency on the machine (through its machine package, a group package, an OU package, profile, etc.), then the self-service option won't allow you to uninstall it. Conflicts force uninstallation during installation, so that might be the problem. Could you check the machine's dependencies?

However, the package should still appear, even if it's not installable.

Sincerely,

Denis

Re: Package not appearing

Published: July 22, 2025 - 2:23 PM
by fredemme
Thank you,
the Office 2016 or 2013 package is not machine-dependent.
The 2024 package has finally appeared on my machine... probably due to a permissions update.
Thank you for your feedback.

Re: Package not appearing

Published: July 22, 2025 - 3:42 PM
by dcardon
Hello Frédérique,

thank you for your feedback, glad it's working well for you in the end. :-)

Actually, the WaptSelfService rules are contained in a Wapt package like any other, so it needs to be installed/updated on the machine for the display to update correctly in the self-service interface itself.

Best regards,

Denis