June 2017 servicing release for Microsoft Desktop Optimization Pack

This article describes the contents of the June 2017 servicing release for Microsoft Desktop Optimization Pack (MDOP). This servicing release contains the latest fixes for the Microsoft Application Virtualization (App-V) 5.1 RTM Client and Remote Desktop Services (RDS), Microsoft BitLocker Administration and Monitoring (MBAM) 2.5 Service Pack 1 (SP1), and Microsoft User Experience Virtualization (UE-V) 2.1 Service Pack 1 (SP1).

Notes

• The App-V and UE-V Clients are "in-box" starting in the Windows 10 Anniversary Edition (Version 1607). The "in-box" App-V client continues to use the App-V 5.1 Server.
• Fixes that are delivered to the "out-of-box" versions of App-V and UE-V are first delivered for the "in-box" versions of App-V and UE-V in the monthly Windows 10 cumulative updates.
• We recommend that you test fixes before you deploy them in a production environment. Because the builds are cumulative, each new servicing release contains all the fixes (including security fixes) that were included in the previous update package. We recommend that you apply the latest servicing release.

App-V 5.1 (release version)

This servicing release fixes the following issues:

• The Office Click2Run macro functionality does not work correctly with enterprise App-V virtualization.

• When two or more packages in the same connection group have "Any Version" selected, and the connection group is upgraded at the same time, the packages are not published to the user.

• A race condition exists between the App-V catalog manager and the profile roaming service. This condition is now fixed by a new registry key that controls the waiting period for the App-V catalog manager to allow any third-party profile roaming service to be completed. The registry key details are as follows:

  Parameter	Value
  Path	HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\Catalog
  Setting	UserCatalogWaitingPeriod
  DataType	DWORD
  Units	Milliseconds
  Default	0

• The Office Outlook search functionality does not work correctly.

• AppV Hotfix 7 fixed an issue in which a function of the Connection Group Optional feature was broken. After the hotfix was issued, we received reports that the PackageGroups registry hive consumes a lot of space in installations that involve App-V connection groups on RDS computers. A modified fix in the latest hotfix release significantly reduces the registry space that is used by the Connection Group Optional feature. It does this by grouping user settings based on the effective group that a user belongs to, instead of by individual users.

MBAM 2.5 Service Pack 1

This servicing release fixes the following issues:

• The MBAM client does not allow the safe removal of USB devices.
• The MBAM compliance report displays blanks when the cipher strength is set to XTS-AES.
• A deadlock issue occurs on the MBAM SQL cluster server.
• The self-service portal does not return recovery keys under certain circumstances.

UE-V 2.1 Service Pack 1

This servicing release improves the following functionality:

• Adds the ADMX Template for UE-V 2.1 SP1 to control Office 2016.

Microsoft Download Center

A supported hotfix is available for download.

Download the June 2017 servicing release now

Prerequisites

• To apply this hotfix for APP-V 5.1, you must have APP-V 5.1 RTM or a later App-V 5.1 servicing release installed.
• To apply this hotfix for MBAM 2.5 SP1, you must have MBAM 2.5 SP1 RTM installed.
• To apply this hotfix for UE-V, you must have UE-V 2.1 SP1 RTM or a later UE-V 2.1 SP1 servicing release installed.

Restart requirements

You must restart the computer after you apply this hotfix.

Replacement information

This hotfix replaces the following hotfixes:

• HF08 for APP-V 5.1
• HF04 for MBAM 2.5 SP1

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

This servicing release includes update installers for App-V 5.1 RTM.

For App-V, the original client installation file contains installers for both x86-based and x64-based architectures. Running the .exe file automatically deploys the correct client. However, if the original client was deployed by extracting and using the architecture-specific .msi file, you must apply the associated .msp file to make sure that the update is successful. To extract the associated .msp file, run the following command:

AppV5.1RTM_Client_KB4018510 /LAYOUT

Important If you try to apply this update by running the AppV5.1RTM_Client_KB4018510.exe file instead of the (extracted) associated .msp file, you may receive the following error message: 

File information 

App-V 5.1

MBAM 2.5

Learn about the terminology that Microsoft uses to describe software updates.