Xelion Windows App Deployment Guide
Breadcrumbs

Xelion Windows App Deployment Guide (Enterprise)

Any files needed to complete the steps in this guide, can be found as attachemnts at the bottom of the page.

App Information

App Name: Xelion
Store ID: 9NBLGGH5Q9BJ
Web Store URL: https://apps.microsoft.com/detail/9NBLGGH5Q9BJ

The information above is sufficient for most deployment scenarios
Read the FAQ if you are uncertain about what to do next.

Preferred deployment options

Preferably, use store-based deployment via Intune:

  • Intune: Deploy directly from the Microsoft Store app (new) catalog; updates and licensing are automatic.

  • SCCM: Use co-management and let Intune handle the Store apps. SCCM continues to manage other workloads.

Alternative methods:

  • Winget: Use if you want to install using a command or custom script.

  • MSIX packages:

    • For offline installations,

    • Deploying via SCCM without co-management,

    • On a multi-user environment (e.g. RDS) without Intune/SCCM and without direct store access.

Prerequisites

Winget is needed to download or install Xelion. If winget is missing on your system, you can install it by running this script:

Install-WinGet.ps1

If the old AppInstaller version of the Xelion app is currently installed on a multi-user environment without Intune/SCCM and without direct store access (e.g. RDS), you need to uninstall and deprovision it first, by running this script:

Xelion-Cleanup-AppInstaller.ps1

Install using Winget

If you ever need to install Xelion from the command line or from a script, you can use Winget:

winget install Xelion --architecture x64 --accept-package-agreements *> log.txt

You may need to provision the app for other users on the same system. This is documented below.

Install MSIX Packages manually

Try to use your deployment solution (Intune, RDS, VDI, App Attach) where possible to install packages. Manual installation as outlined below should only be used when the deployment solution cannot handle the package.

First download the packages using winget

winget download Xelion --architecture x64 --accept-package-agreements --skip-license

Packages are downloaded to the Downloads folder by default. To specify a different folder, use the -d option. You may be asked to sign in as an administrator.

To manually install packages

Add-AppxPackage .\Dependencies\Microsoft.VCLibs.*.appx
Add-AppxPackage .\Dependencies\Microsoft.WindowsAppRuntime.*.msix
Add-AppxPackage .\71F23AFD.Xelion_*_X64.msixbundle

You can also run the following scripts that automate these steps:

PowerShell
Xelion-MSIX-Download.ps1
Xelion-MSIX-Install.ps1

You may need to provision the packages as well. This is documented in the next paragraph.

Provision for new users (shared/VDI/RDS)

To make the app available to new users on a shared system, you need to provision it.
Before you can provision the app to new users, you need to install Xelion first, either by using winget install or by installing the MSIX packages manually.

To start provisioning the app for new users, run this script:

Xelion-ProvisionStoreApp2.ps1

Any new user logging into the machine will have the app available automatically.

Register the app for existing users (shared/VDI/RDS)

If the Xelion app is already installed for one or more users, but is not visible for some users, it may need to be registered for these users.

To register the app for an existing user, run the provided script in the user's context. Ideally, this should be executed at startup.

Xelion-RegisterStoreApp.ps1

Alternatively, you may install the app for each user using winget install, but this script is a simpler operation that does not need an internet connection.

Frequently Asked Questions

Is Scripts.zip still relevant?

No. You can ignore Scripts.zip. The methods described there will no longer be supported in the future.

Winget is missing on my system (e.g. Windows Server 2022). How can I install winget?

Start a terminal as Admin. And then start these commands:

PowerShell
$progressPreference = 'silentlyContinue'
Write-Host "Installing WinGet PowerShell module from PSGallery..."
Install-PackageProvider -Name NuGet -Force | Out-Null
Install-Module -Name Microsoft.WinGet.Client -Force -Repository PSGallery | Out-Null
Write-Host "Using Repair-WinGetPackageManager cmdlet to bootstrap WinGet..."
Repair-WinGetPackageManager -AllUsers
Write-Host "Done."

I get an error when installing Xelion using winget: The package is not compatible with the current Windows version or platform. How to proceed?

When winget install does not work, you need to download the MSIX packages and install them manually. See ‘Install MSIX packages manually’

Do I need to uninstall the old app installer based Xelion app first?

Typically the old AppInstaller version will be removed automatically if a user installs the app from the store.
If users do not have permissions to access the store, or when a user is not permitted to add or remove apps, you need to run this script as an administrator instead:

PowerShell
Xelion-Cleanup-AppInstaller.ps1

Can I use xelionget.exe to install the Xelion Windows App from the store?

No. This is not supported. The recommended approach is to install using winget instead. If you need to provision as well, use the Xelion-ProvisionStoreApp2.ps1 script.

Do I need the MSIX package to deploy Xelion with Microsoft Intune?

No. Intune handles everything when deploying via the Microsoft Store app (new) experience:

  • Retrieves the correct MSIX package from the Microsoft Store

  • Installs and updates the app on devices automatically

  • Manages dependencies

Can I use an MSI installer to install Xelion from the Store?

No. Microsoft Store apps are packaged as MSIX, not MSI. Conversion to MSI is not supported.

I need the MSIX packages, do I still need the AppInstaller file?

No. The AppInstaller file is no longer supported. Use winget download to retrieve MSIX packages instead.

In what situations do I need to provision the Xelion Windows App?

Provisioning is needed whenever you want the Xelion Windows App to be available to multiple users on the same machine without each user installing it individually. Common scenarios include:

  • Virtual Desktop Infrastructure (VDI) environments

  • RDS / Remote Desktop Session Hosts

  • Golden/master images used for deploying multiple devices

In short, any multi-user or pre-imaged scenario usually requires provisioning.

In what situations do I need to manually update the Xelion Windows App?

Usually the Xelion app updates itself through the store. But if the user does not have store access (e.g. on RDS), the app needs to be updated manually.
You can update the app by running the download and install scripts again.

PowerShell
Xelion-MSIX-Download.ps1
Xelion-MSIX-Install.ps1

The provisioned store app is missing for existing users. How to fix this?

Provisioning will make the app available to new users. But existing users might need to register the app at startup. To register the app, run this script in the user’s context:

Xelion-RegisterStoreApp.ps1

How can I get information about the installation status?

Run this PowerShell command to get the installation status of all users on the system:

Get-AppXPackage -AllUsers *Xelion*

How can I get information about the provisioning status?

To check if the app is provisioned, you can run this PowerShell command:

Get-AppxProvisionedPackage -Online | Where-Object DisplayName -eq 71F23AFD.Xelion

It will return the package, if the app has been provisioned successfully.

Is there a way to uninstall the app for a single user?

Yes, you can run this PowerShell command in the context of the user:

Get-AppxPackage -Name *Xelion* | Remove-AppPackage

How do I stop provisioning the app to new users?

If you no longer want the app to become available to new users on the system, run the following script:

Xelion-DeprovisionStoreApp2.ps1

Where can I find information from Microsoft on deploying apps from the store?

Here are some relevant links from Microsoft:

PowerShell scripts

The PowerShell scripts below are mostly needed in multi-user environments where Intune or SCCM is not being used. Please consider to use a store-based deployment model first, before falling back to these scripts.

Prerequisites

Install-WinGet.ps1


Xelion-Cleanup-AppInstaller.ps1

MSIX based installation and update

Xelion-MSIX-Download.ps1


Xelion-MSIX-Install.ps1

Provisioning and registration

Xelion-DeprovisionStoreApp2.ps1Xelion-ProvisionStoreApp.ps1Xelion-ProvisionStoreApp2.ps1Xelion-RegisterStoreApp.ps1

Xelion-ProvisionStoreApp.ps1 only works with older PowerShell versions (PowerShell 5).

Xelion-ProvisionStoreApp2.ps2 should work with all versions.