Streamline desktop deployment consistency across your entire organization by eliminating manual user prompts during software rollouts. This guide provides IT administrators with the essential steps to deploy Azure RTOS GUIX Studio efficiently using enterprise management suites like Microsoft Intune, SCCM, or PDQ. By executing the verified silent install command with elevated administrator privileges, you can automate this machine-user scope installation seamlessly. Ensure a reliable setup with proper detection rules configured to confirm successful deployment without interrupting end users.
Quick snapshot: Silently install Azure RTOS GUIX Studio on Windows
Run in an elevated PowerShell session:
Add-AppxProvisionedPackage -Online -PackagePath "Microsoft.AzureRTOSGUIXStudio_6.4.0.0_x86__8wekyb3d8bbwe.msix" -DependencyPackagePath "Microsoft.VCLibs.140.00.UWPDesktop.appx" -SkipLicenseOverview
| Application | Azure RTOS GUIX Studio |
|---|---|
| Version | 6.4.0.0 |
| Publisher | Microsoft Corporation |
| Installer type | MSIX / Store app |
| Install scope | Machine + User |
| Requires admin | Yes |
| Silent install | Available |
| Silent uninstall | Available |
| Detection method | MSIX package family |
| Installer file | Microsoft.AzureRTOSGUIXStudio_6.4.0.0_x86__8wekyb3d8bbwe.msix |
Silent install steps
Azure RTOS GUIX Studio installs through a PowerShell command, so run it in an elevated PowerShell session. Command Prompt cannot run this cmdlet.
Install with PowerShell
- Download or stage the installer (
Microsoft.AzureRTOSGUIXStudio_6.4.0.0_x86__8wekyb3d8bbwe.msix) to a local folder, for exampleC:\Installers. Place the dependency packageMicrosoft.VCLibs.140.00.UWPDesktop.appxin the same folder. The install references it via-DependencyPackagePath.
- Open PowerShell as Administrator — right-click Start (or press Win+X), then:
- On Windows 10: choose Windows PowerShell (Admin).
- On Windows 11: choose Terminal (Admin) — it opens Windows Terminal running PowerShell.
- Run the silent install command:
Add-AppxProvisionedPackage -Online -PackagePath "Microsoft.AzureRTOSGUIXStudio_6.4.0.0_x86__8wekyb3d8bbwe.msix" -DependencyPackagePath "Microsoft.VCLibs.140.00.UWPDesktop.appx" -SkipLicensePS C:\> Set-Location 'C:\Installers'PS C:\Installers> Add-AppxProvisionedPackage -Online -PackagePath "Microsoft.AzureRTOSGUIXStudio_6.4.0.0_x86__8wekyb3d8bbwe.msix" -DependencyPackagePath "Microsoft.VCLibs.140.00.UWPDesktop.appx" -SkipLicenseInstalling Azure RTOS GUIX Studio 6.4.0.0…Installation complete — exit code 0.PS C:\Installers> ▋
Deployment Notes
Key facts to confirm before rolling this out to production machines — permissions required, scope of install, and reboot behavior.
| Requirement | Administrator privileges required |
|---|---|
| Install scope | Machine + User |
| Restart behavior | No restart expected |
Detection Rules
Configure your deployment tool with the detection rule below to confirm a successful install of Azure RTOS GUIX Studio. The same rule work for Microsoft Intune, SCCM, PDQ Deploy, and most RMM platforms — just paste the values into the matching fields.
MSIX detection
Silent Uninstall Steps
Remove Azure RTOS GUIX Studio silently from one machine or your entire fleet. The commands below uninstall without prompts and suppress automatic reboots so you control the timing.
Uninstall with PowerShell
Azure RTOS GUIX Studio is removed through a PowerShell command (Command Prompt cannot run it).
- Open PowerShell as Administrator.
- Run the silent uninstall command.
Get-AppxProvisionedPackage -Online | Where-Object { $_.PackageName -like 'Microsoft.AzureRTOSGUIXStudio_*' } | Remove-AppxProvisionedPackage -OnlineDeployment Examples
Drop the snippet below into your deployment tool, Group Policy, or scheduled task. It wraps the silent install command for Azure RTOS GUIX Studio as a PowerShell script — copy, save, and run.
PowerShell script example
Save the following content as install-azure-rtos-guix-studio.ps1 in the same folder as the installer.
Set-Location -Path $PSScriptRoot
$Installer = 'Microsoft.AzureRTOSGUIXStudio_6.4.0.0_x86__8wekyb3d8bbwe.msix'
Add-AppxProvisionedPackage -Online -PackagePath $Installer -DependencyPackagePath "Microsoft.VCLibs.140.00.UWPDesktop.appx" -SkipLicense
exit $LASTEXITCODEFrequently asked questions
Can I silently install Azure RTOS GUIX Studio on Windows?
Do I need administrator privileges to install Azure RTOS GUIX Studio?
Will installing Azure RTOS GUIX Studio restart the computer?
Add-AppxProvisionedPackage avoids restarting your machine, registering the application for all users upon their subsequent login.How do I verify Azure RTOS GUIX Studio installed successfully?
How do I silently uninstall Azure RTOS GUIX Studio?
Remove-AppxProvisionedPackage along with the complete package full name.Which deployment tools support these commands?
Troubleshooting
If the install fails, exits with a non-zero code, or leaves no trace on the target machine, work through the checks below. Most issues come down to permissions, paths, or exit code handling.
| Run as administrator | Make sure Command Prompt or PowerShell is opened as Administrator. This installer writes to a machine-wide location and will fail silently without elevated permissions. |
|---|---|
| Verify the installer file name | Confirm that the installer file name matches the command shown in this guide: Microsoft.AzureRTOSGUIXStudio_6.4.0.0_x86__8wekyb3d8bbwe.msix. |
| Run from the correct folder | Run the command from the folder that contains the installer file. For batch or PowerShell deployments, place the script and installer in the same folder. |
| Check exit codes | If the installer returns a non-zero exit code, review the installer log or your deployment tool's logs. Some packages use additional success exit codes. |
| Restart if required | If the application does not appear immediately after installation, sign out and sign back in, or restart the device — this refreshes Start menu shortcuts, file associations, and Path entries written by the installer. |
| Validate detection rules | If your deployment tool reports the app as not installed, verify that the detection rule matches the installed version, MSI product code, registry key, or file path. Use the Detection Rules section above to confirm whether the application was installed successfully. |
