Release Notes for App-V for Windows 10, version 1607
- Windows 10, version 1607
The following are known issues and workarounds for Application Virtualization (App-V) running on Windows 10, version 1607.
Windows Installer packages (.msi files) generated by the App-V sequencer (version 5.1 and earlier) fail to install on computers with the in-box App-V client
There are MSI packages generated by an App-V sequencer from previous versions of App-V (Versions 5.1 and earlier). These packages include a check to validate whether the App-V client is installed on client devices, before allowing the MSI package to be installed. As the App-V client gets installed automatically when you upgrade user devices to Windows 10, version 1607, the pre-requisite check fails and causes the MSI to fail.
Install the latest App-V sequencer, which you can get from the Windows Assessment and Deployment Kit (ADK) for Windows 10, version 1607. See Download the Windows ADK. For more information, see Install the App-V Sequencer.
Ensure that you've installed the MSI Tools included in the Windows 10 SDK, available as follows:
Copy msidb.exe from the default path of the Windows SDK installation (C:\Program Files (x86)\Windows Kits\10) to a different directory. For example: C:\MyMsiTools\bin
From an elevated Windows PowerShell prompt, navigate to the following folder:
<Windows Kits 10 installation folder>\Microsoft Application Virtualization\Sequencer\
By default, this path will be:
C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\Sequencer
Run the following command:
Update-AppvPackageMsi -MsiPackage "<path to App-V Package .msi file>" -MsSdkPath "<path>"
where the path is to the new directory (C:\MyMsiTools\ for this example).
Error occurs during publishing refresh between App-V 5.0 SP3 Management Server and App-V Client on Windows 10
An error is generated during publishing refresh when synchronizing packages from the App-V 5.0 SP3 management server to an App-V client on Windows 10. This error occurs because the App-V 5.0 SP3 server doesn't understand the Windows 10-operating system that is specified in the publishing URL. The issue is fixed for App-V publishing server, but isn't backported to versions of App-V 5.0 SP3 or earlier.
Workaround: Upgrade the App-V 5.0 Management server to the App-V Management server for Windows 10 Clients.
Custom configurations don't get applied for packages that will be published globally if they're set using the App-V Server
If you assign a package to an AD group that contains machine accounts and apply a custom configuration to that group using the App-V Server, the custom configuration won't be applied to those machines. The App-V Client will publish packages assigned to a machine account globally. However, it stores custom configuration files per user in each user’s profile. Globally published packages won't have access to this custom configuration.
Workaround: Implement one of the following tasks:
Assign the package to groups containing only user accounts. This assignation ensures that the package’s custom configuration will be stored in each user’s profile and will be applied correctly.
Create a custom deployment configuration file and apply it to the package on the client, using the Add-AppvClientPackage cmdlet with the –DynamicDeploymentConfiguration parameter. See About App-V Dynamic Configuration for more information.
Create a new package with the custom configuration using the App-V Sequencer.
Server files not deleted after new App-V Server installation
If you uninstall the App-V 5.0 SP1 Server and then install the App-V Server, the installation fails, the wrong version of the Management server is installed, and an error message is returned. The issue occurs because the Server files aren't being deleted when you uninstall App-V 5.0 SP1, so the installation process does an upgrade instead of a new installation.
Workaround: Delete this registry key before you start installing App-V:
Under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall, locate and delete the installation GUID key that contains the DWORD value "DisplayName" with value data "Microsoft Application Virtualization (App-V) Server". This is the only key that should be deleted.
File type associations added manually are not saved correctly
File type associations added to an application package manually using the Shortcuts and FTAs tab at the end of the application upgrade wizard aren't saved correctly. They won't be available to the App-V Client or to the Sequencer when updating the saved package again.
Workaround: To add a file type association, open the package for modification and run the update wizard. During the Installation step, add the new file type association through the operating system. The sequencer will detect the new association in the system registry and add it to the package’s virtual registry, where it will be available to the client.
When streaming packages in Shared Content Store (SCS) mode to a client that is also managed with AppLocker, additional data is written to the local disk.
To decrease the amount of data written to a client’s local disk, you can enable SCS mode on the App-V Client to stream the contents of a package on demand. However, if AppLocker manages an application within the package, some data might be written to the client’s local disk that wouldn't otherwise be written.
In the Management Console Add Package dialog box, the Browse button is not available when using Chrome or Firefox
On the Packages page of the Management Console, if you click Add or Upgrade in the lower-right corner, the Add Package dialog box appears. If you're accessing the Management Console using Chrome or Firefox as your browser, you will not be able to browse to the location of the package.
Workaround: Type or copy and paste the path to the package into the Add Package input field. If the Management Console has access to this path, you will be able to add the package. If the package is on a network share, you can browse to the location using File Explorer by doing these steps:
While pressing Shift, right-click on the package file
Select Copy as path
Paste the path into the Add Package dialog box input field
Upgrading App-V Management Server to 5.1 sometimes fails with the message “A database error occurred”
If you install the App-V 5.0 SP1 Management Server, and then try to upgrade to App-V Server when multiple connection groups are configured and enabled, the following error is displayed: “A database error occurred. Reason: 'Invalid column name 'PackageOptional'. Invalid column name 'VersionOptional'.”
Workaround: Run this command on your SQL database:
ALTER TABLE AppVManagement.dbo.PackageGroupMembers ADD PackageOptional bit NOT NULL DEFAULT 0, VersionOptional bit NOT NULL DEFAULT 0
where “AppVManagement” is the name of the database.
Users cannot open a package in a user-published connection group if you add or remove an optional package
In environments that are running the RDS Client or that have multiple concurrent users per computer, logged-in users cannot open applications in packages that are in a user-published connection group if an optional package is added to or removed from the connection group.
Workaround: Have users log out and then log back in.
Error message is erroneously displayed when the connection group is published only to the user
When you run Repair-AppvClientConnectionGroup, the following error is displayed, even when the connection group is published only to the user: “Internal App-V Integration error: Package not integrated for the user. Ensure that the package is added to the machine and published to the user.”
Workaround: Execute one of the following tasks:
Publish all packages in a connection group.
The problem arises when the connection group being repaired has packages that are missing or not available to the user (that is, not published globally or to the user). However, the repair will work if all of the connection group’s packages are available, so ensure that all packages are published.
Repair packages individually using the Repair-AppvClientPackage command rather than the Repair-AppvClientConnectionGroup command.
Determine which packages are available to users and then run the Repair-AppvClientPackage command once for each package. Use Windows PowerShell cmdlets to execute the following tasks:
Get all the packages in a connection group.
Check to see if each package is currently published.
If the package is currently published, run Repair-AppvClientPackage on that package.
Icons not displayed properly in Sequencer
Icons in the Shortcuts and File Type Associations tab are not displayed correctly when modifying a package in the App-V Sequencer. This problem occurs when the size of the icons is not 16x16 or 32x32.
Workaround: Only use icons that are 16x16 or 32x32.
InsertVersionInfo.sql script no longer required for the Management Database
The InsertVersionInfo.sql script is not required for versions of the App-V management database later than App-V 5.0 SP3.
Microsoft Visual Studio 2012 not supported
App-V doesn't support Visual Studio 2012.
Workaround: Use a newer version of Microsoft Visual Studio.
Currently, Visual Studio 2012 doesn't support app virtualization, whether using Microsoft App-V or third party solutions such as VMWare ThinApp. While it is possible you might find that Visual Studio works well enough for your purposes when running within one of these environments, we are unable to address any bugs or issues found when running in a virtualized environment at this time.
Application filename restrictions for App-V Sequencer
The App-V Sequencer cannot sequence applications with filenames matching "CO_<x>" where x is any numeral. Error 0x8007139F will be generated.
Workaround: Use a different filename
Related resources list
For information that can help with troubleshooting App-V for Windows 10, see:
- Application Virtualization (App-V): List of Microsoft Support Knowledge Base Articles
- The Official Microsoft App-V Team Blog
- Technical Reference for App-V
- App-V TechNet Forum
For App-V issues, use the App-V TechNet Forum.