Foundry-Local Unable to install azure foundry in windows 2022 Server VM

Hi, I tried installing the azure foundry local with the provided step. But it always fails with vclib version is wrong. The require VClibs higher but installed is lower. There is no way to install azure foundry local to windows 2022 server VM. Please advice.

Expected version33728 by installed is different version. This is not getting the correct version Invoke-WebRequest -Method Get -Uri $crtUri -OutFile .\VcLibs.appx

Neither any location to pull the correct version.

These instructions not worked

$releaseUri = "https://github.com/microsoft/Foundry-Local/releases/download/v0.3.9267/FoundryLocal-x64-0.3.9267.43123.msix" Invoke-WebRequest -Method Get -Uri $releaseUri -OutFile .\FoundryLocal.msix $crtUri = "https://aka.ms/Microsoft.VCLibs.x64.14.00.Desktop.appx" Invoke-WebRequest -Method Get -Uri $crtUri -OutFile .\VcLibs.appx

Add-AppxPackage .\FoundryLocal.msix -DependencyPath .\VcLibs.appx

Sep 25 '25 22:09 knetway-us

Hi So your trying install a really old version releases/download/v0.3.9267/FoundryLocal-x64-0.3.9267.43123.msix"

https://github.com/microsoft/Foundry-Local/releases

I would suggest you try to install https://github.com/microsoft/Foundry-Local/releases/tag/v0.6.87

Sep 26 '25 09:09 leestott

@knetway-us Are you able to install using WinGet?

Sep 26 '25 14:09 natke

@natke WinGet is not part of 2022 server. I tried few ways to get that installed but so far no success in 2022 server.

@leestott still same error. Below is the detailed error

Add-AppxPackage .\FoundryLocal-x64-0.6.87.msix -DependencyPath .\VcLibs.appx Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF3, Package failed updates, dependency or conflict validation. Windows cannot install package Microsoft.FoundryLocal_0.6.87.59034_x64__8wekyb3d8bbwe because this package depends on a framework that could not be found. Provide the framework "Microsoft.VCLibs.140.00.UWPDesktop" published by "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version 14.0.33728.0, along with this package to install. The frameworks with name "Microsoft.VCLibs.140.00.UWPDesktop" currently installed are: { Windows cannot install package Microsoft.FoundryLocal_0.6.87.59034_x64__8wekyb3d8bbwe because this package depends on a framework that could not be found. Provide the framework "Microsoft.VCLibs.140.00.UWPDesktop" published by "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version 14.0.33728.0, along with this package to install. The frameworks with name "Microsoft.VCLibs.140.00.UWPDesktop" currently installed are: {Microsoft.VCLibs.140.00.UWPDesktop_14.0.33321.0_x64__8wekyb3d8bbwe} NOTE: For additional information, look for [ActivityId] 2b10571e-f585-0001-39f6-15e0442edc01 in the Event Log or use the command line Get-AppPackageLog -ActivityID 2b10571e-f585-0001-39f6-15e0442edc01 At line:1 char:1

Add-AppxPackage .\FoundryLocal-x64-0.6.87.msix -DependencyPath .\VcLi ...

+ CategoryInfo : WriteError: (C:\Users-a...x64-0.6.87.msix:String) [Add-AppxPackage], IOException + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

Sep 26 '25 16:09 knetway-us

Hi @knetway-us, we have other users installed on Windows Server. We are working to get instructions for you, and will also add these to the documentation

Sep 27 '25 16:09 natke

@knetway-us here is a guide and example of installing foundry local on Windows Server 2025 https://techcommunity.microsoft.com/blog/itopstalkblog/install-and-run-azure-foundry-local-llm-server--open-webui-on-windows-server-202/4457788

Sep 30 '25 07:09 leestott

@knetway-us WinGet the Windows Package Manager is available on Windows 11, modern versions of Windows 10, and Windows Server 2025 as a part of the App Installer. The App Installer is a System Component delivered and updated by the Microsoft store on Windows Desktop versions, and via Updates on Windows Server 2025. see https://learn.microsoft.com/en-us/windows/package-manager/winget/

The WinGet command line tool is only supported on Windows 10 version 1809 (build 17763) or later. WinGet will not be available until you have logged into Windows as a user for the first time, triggering Microsoft Store to register the Windows Package Manager as part of an asynchronous process. If you have recently logged in as a user for the first time and find that WinGet is not yet available, you can open PowerShell and enter the following command to request this WinGet registration: Add-AppxPackage -RegisterByFamilyName -MainPackage Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.

Oct 02 '25 17:10 leestott

@knetway-us

Windows Server 2022 does not natively include support for WinGet (Windows Package Manager), but you can install it manually with a few extra steps.

Manual Installation Is Possible

WinGet is officially supported on Windows 10, Windows 11, and Windows Server 2025.
For Windows Server 2022, you can install WinGet by manually downloading and provisioning the required packages:
- Microsoft.UI.Xaml dependency
- WinGet MSIX bundle
- License file for App Installer
You’ll need to use Windows PowerShell 5.1 (not PowerShell 7) and run commands like Add-AppxProvisionedPackage to install it. See https://gist.github.com/erwinkersten/626ed456c1bd84fd5e023b081d6d450e and this walkthrough https://www.ajitsharma.in/installing-winget-on-windows-server-2019-2022/

Alternative: Use a Script

Some community scripts (like WinGet_Script.ps1) automate the process:

Set execution policy
Download dependencies
Install and verify WinGet
This installs the App Installer bundle, which includes WinGet.
You may need to enable App Installer support via Group Policy or Settings if blocked.
If you're behind a proxy or firewall, make sure the URLs are accessible

# WinGet Installer for Windows Server 2022
# Run as Administrator in PowerShell 5.1

# Step 1: Set execution policy
Set-ExecutionPolicy RemoteSigned -Scope Process -Force

# Step 2: Create temp folder
$temp = "$env:TEMP\WinGetInstall"
New-Item -ItemType Directory -Path $temp -Force | Out-Null
Set-Location $temp

# Step 3: Download dependencies
Write-Host "Downloading dependencies..."
Invoke-WebRequest -Uri "https://aka.ms/Microsoft.VCLibs.x64.14.00.Desktop.appx" -OutFile "$temp\Microsoft.VCLibs.x64.appx"
Invoke-WebRequest -Uri "https://aka.ms/Microsoft.UI.Xaml.2.7.appx" -OutFile "$temp\Microsoft.UI.Xaml.2.7.appx"
Invoke-WebRequest -Uri "https://aka.ms/getwinget" -OutFile "$temp\AppInstaller.appxbundle"

# Step 4: Install dependencies
Write-Host "Installing dependencies..."
Add-AppxPackage -Path "$temp\Microsoft.VCLibs.x64.appx"
Add-AppxPackage -Path "$temp\Microsoft.UI.Xaml.2.7.appx"
Add-AppxPackage -Path "$temp\AppInstaller.appxbundle"

# Step 5: Verify installation
Write-Host "Verifying WinGet installation..."
winget --version

# Step 6: Cleanup
Remove-Item -Path $temp -Recurse -Force
Write-Host "WinGet installation complete."

After Installation

Once installed, you can run winget --version to confirm it’s working.

Oct 02 '25 17:10 leestott