Microsoft.UI.Xaml 2.8.6 install hangs #10183
Comments
microsoft-github-policy-service
bot
added
the
needs-triage
|
The build you are running is unsupported, you are running Build 21966, which is a leaked build from May 2021. Please verify behavoir on a supported build of Windows |
|
Thanks @Pinguin2001! I was not aware that this build is not supported, as the package README mentions "Windows 10 1809 - Build 17763 or newer (including Windows Insider Previews)". Could you point me to where I can find a list of all the supported builds? We have a wrapper around a tool that has WinUI as a dependency, so being unable to provision WinUI means the end-user cannot use our software. Knowing where we can provision it would allow us to present a better error message to the user. |
|
@agiacomolli No issue here, the operation works perfectly. This command executes the same underlying functionality but via dism directly rather than powershell, which is preferred for such operation because you cannot 100% guarantee ps is present on the users' machine. D:\>dism.exe /online /Add-ProvisionedAppxPackage /PackagePath:"D:\Microsoft.UI.Xaml.2.8.x64.appx" /SkipLicense
Deployment Image Servicing and Management tool
Version: 10.0.26100.1150
Image Version: 10.0.26120.2222
The operation completed successfully.Please check if you appx is valid Via PS it also works perfectly: PS D:\> Add-AppxProvisionedPackage -Online -PackagePath .\Microsoft.UI.Xaml.2.8.x64.appx -SkipLicense -LogLevel WarningsInfo -LogPath c:\dism.log
Path :
Online : True
RestartNeeded : False |
|
Yes, I've tested it on other Windows versions, and it works as expected. I got the same results as you. I believe the issue is likely to occur on that specific build as you mentioned. To be honest I found it wasn't working by chance. On that specific Windows build (21966), the command gets stuck when using either dism or the cmdlet. Here is the dism output, which never completes: C:\> dism.exe /LogPath:"c:\dism.log" /online /Add-ProvisionedAppxPackage /PackagePath:"C:\Microsoft.UI.Xaml.2.8.x64.appx" /SkipLicense
Deployment Image Servicing and Management tool
Version: 10.0.21996.1
Image Version: 10.0.21996.1The logs in Just a bit more context, upon installation, our software automatically provisions the required dependencies, including WinUI. However we cannot control which Windows version the user installs our software on, which is why I asked you about supported Windows builds. Anyway, I think it's fine to add a manual check to exclude this build on our side. This way, we can fail the install with a useful error message. |
|
I'm going to close it because it is not related to WinUI itself. Thanks for your help @Pinguin2001! |
microsoft-github-policy-service
bot
added
needs-triage
Describe the bug
The install hangs without any output using
Add-AppxProvisionedPackage.Steps to reproduce the bug
Expected behavior
The package being correctly provisioned.
Screenshots
No response
NuGet package version
None
Windows version
No response
Additional context
Package version: 2.8.6
Windows version: 11 (10.0.21996)
Logs mention missing dependencies. Full DISM log:
The text was updated successfully, but these errors were encountered: