deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 05:17:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
windows-itpro-docs/windows/application-management/app-v/appv-release-notes-for-appv-for-windows-1703.md
MandiOhlinger 6308ff83d7 app-v applies to round 3
2021-09-28 17:15:06 -04:00

6.4 KiB
Raw Blame History

title, description, author, ms.pagetype, ms.mktglfcycl, ms.sitesec, ms.prod, ms.date, ms.reviewer, manager, ms.author
title description author ms.pagetype ms.mktglfcycl ms.sitesec ms.prod ms.date ms.reviewer manager ms.author
Release Notes for App-V for Windows 10 version 1703 (Windows 10/11) A list of known issues and workarounds for App-V running on Windows 10 version 1703 and Windows 11. greg-lindsay mdop, appcompat, virtualization deploy library w10 04/19/2017 dansimp greglin

Release Notes for App-V for Windows 10 version 1703 and later

[!INCLUDE Applies to Windows client versions]

The following are known issues and workarounds for Application Virtualization (App-V) running on Windows 10 version 1703 and later

Problem Workaround
Unable to manually create a system-owned folder needed for the set-AppVClientConfiguration PowerShell cmdlet when using the PackageInstallationRoot, IntegrationRootUser, or IntegrationRootGlobal parameters. Don't create this file manually, instead let the Add-AppVClientPackage cmdlet auto-generate it.
Failure to update an App-V package from App-V 5.x to the latest in-box version, by using the PowerShell sequencing commands. Make sure you have the complete App-V package or the MSI file from the original app.
Unable to modify the locale for auto-sequencing. 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.
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. 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:


For App-V issues, use the App-V TechNet Forum.

Related topics