Release Notes for App-V for Windows 10 version 1703 and later
Applies to:
- Windows 10
- Windows 11
The following are known issues and workarounds for Application Virtualization (App-V) running on Windows 10 version 1703 and later
Problem: Unable to manually create a system-owned folder needed for the
set-AppVClientConfiguration
PowerShell cmdlet when using the PackageInstallationRoot, IntegrationRootUser, or IntegrationRootGlobal parameters.Workaround: Don't create this file manually, instead let the
Add-AppVClientPackage
cmdlet auto-generate it.Problem: Failure to update an App-V package from App-V 5.x to the latest in-box version, by using the PowerShell sequencing commands.
Workaround: Make sure you have the complete App-V package or the MSI file from the original app.
Problem: Unable to modify the locale for auto-sequencing.
Workaround: Open the
C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\AutoSequencer\Unattend_Sequencer_User_Setup_Template.xml
file and include the language code for your locale. For example, if you wanted Spanish (Spain), you'd use: es-ES.Problem: Filetype and protocol handlers aren't registering properly with the Google Chrome browser, causing you to not see App-V packages as an option for default apps from the Settings > Apps> Default Apps area.
Workaround: The recommended workaround is to add the following code to the AppXManifest.xml file, underneath the
<appv:Extensions>
tag:<appv:Extension Category="AppV.URLProtocol"> <appv:URLProtocol> <appv:Name>ftp</appv:Name> <appv:ApplicationURLProtocol> <appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon> <appv:ShellCommands> <appv:DefaultCommand>open</appv:DefaultCommand> <appv:ShellCommand> <appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId> <appv:Name>open</appv:Name> <appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine> <appv:DdeExec> <appv:DdeCommand /> </appv:DdeExec> </appv:ShellCommand> </appv:ShellCommands> </appv:ApplicationURLProtocol> </appv:URLProtocol> </appv:Extension> <appv:Extension Category="AppV.URLProtocol"> <appv:URLProtocol> <appv:Name>http</appv:Name> <appv:ApplicationURLProtocol> <appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon> <appv:ShellCommands> <appv:DefaultCommand>open</appv:DefaultCommand> <appv:ShellCommand> <appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId> <appv:Name>open</appv:Name> <appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine> <appv:DdeExec> <appv:DdeCommand /> </appv:DdeExec> </appv:ShellCommand> </appv:ShellCommands> </appv:ApplicationURLProtocol> </appv:URLProtocol> </appv:Extension> <appv:Extension Category="AppV.URLProtocol"> <appv:URLProtocol> <appv:Name>https</appv:Name> <appv:ApplicationURLProtocol> <appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon> <appv:ShellCommands> <appv:DefaultCommand>open</appv:DefaultCommand> <appv:ShellCommand> <appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId> <appv:Name>open</appv:Name> <appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine> <appv:DdeExec> <appv:DdeCommand /> </appv:DdeExec> </appv:ShellCommand> </appv:ShellCommands> </appv:ApplicationURLProtocol> </appv:URLProtocol> </appv:Extension>
Related resources list
For information that can help with troubleshooting App-V for Windows client, see the following articles: