Company Portal Installation failing due to missing Microsoft.UI.Xaml.2.7

Sriram_Jasti​ 

Hi, you didn't answer me regarding which OS versions this is happening on?

So, no Win32 package as I can see right now...

At this point, you don't have many options. Deploying a platform script will take precedence over app installation in your case (Copilot and Company Portal). In theory, this could work. The problem is (that's why I asked about OS versions): winget is embedded only in Windows 11 and not on all Windows 10 versions.

The second option is calling NuGet directly in a script, but based on your firewall/proxy, I'm not sure if it will go through.

The Fallback Block Only in your case (from lines 15 to 35) should work. I compiled it, ran it myself, and it worked fine on a Windows 11 with no Company Portal.

Good luck! 

# Standalone Microsoft.UI.Xaml.2.7 installer - downloads + installs
# Run as SYSTEM (Intune script) or Admin

# If Winget Present - Use it otherweise fallback to NuGet download + install 
try {
    $wingetPath = (Get-ChildItem "C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_*_x64__8wekyb3d8bbwe" | Sort-Object LastWriteTime -Descending | Select-Object -First 1).FullName
    if ($wingetPath) {
        & "$wingetPath\winget.exe" install --id 9P5VK8KZB5QZ --exact --silent --accept-source-agreements --scope machine --force
        Start-Sleep 3
    }
} catch {
    Write-Output "Winget not available, trying NuGet method..."
}

# Fallback - Direct NuGet download + install
$nugetUrl = "https://www.nuget.org/api/v2/package/Microsoft.UI.Xaml/2.7.3"
$zipFile = "$env:TEMP\xaml27.zip"

try {
    Invoke-WebRequest -Uri $nugetUrl -OutFile $zipFile -UseBasicParsing
    Expand-Archive -Path $zipFile -DestinationPath "$env:TEMP\xaml27" -Force

    # Install
    $appx64 = "$env:TEMP\xaml27\tools\AppX\x64\Release\Microsoft.UI.Xaml.2.7.appx"
    if (Test-Path $appx64) {
        Add-AppxPackage -Path $appx64 -ErrorAction SilentlyContinue | Out-Null
        Write-Output "UI.Xaml x64 installed"
    }

    # Cleanup
    Remove-Item "$env:TEMP\xaml27" -Recurse -Force -ErrorAction SilentlyContinue
    Remove-Item $zipFile -Force -ErrorAction SilentlyContinue
} catch {
    Write-Warning "NuGet method failed: $_"
}

# Verify
<# $pkg = Get-AppxPackage -Name "Microsoft.UI.Xaml.2.7" -AllUsers -ErrorAction SilentlyContinue
if ($pkg) {
    Write-Output "SUCCESS: Microsoft.UI.Xaml.2.7 v$($pkg.Version) installed"
    exit 0
} else {
    Write-Error "FAILED: Microsoft.UI.Xaml.2.7 not found after install"
    exit 1
}
#>

Hi Sriram_Jasti​ ,
that’s likely because Microsoft.UI.Xaml.2.7 is a framework dependency, not a normal “Store app” with a user-facing listing, and those framework packages often don’t show up in Intune’s Store search. Microsoft also explicitly notes that some Store apps won’t be displayed/available when searching inside Intune.

Did you try to take a look here? --> https://learn.microsoft.com/en-us/answers/questions/4186161/what-is-microsoft-ui-xaml-2-7-and-why-dont-i-have