September 2016 servicing release for Microsoft Desktop Optimization Pack

S’applique à : Desktop Optimization PackMicrosoft Advanced Group Policy Management 4.0 Service Pack 3App-V 5.1 for Remote Desktop Services


This article describes the content of the September 2016 servicing release for Microsoft Desktop Optimization Pack. This servicing release contains the latest fixes for Microsoft Advanced Group Policy Management (AGPM) 4.0 Service Pack 3 (SP3), Microsoft Application Virtualization (App-V) 5.1 RTM Client, Remote Desktop Services (RDS) and Server, and Microsoft BitLocker Administration and Monitoring (MBAM) 2.5 SP1.

Note 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 with the previous update package. We recommend that you consider applying the latest servicing release.

For AGPM 4.0 SP3, this servicing release fixes the following issue:For App-V 5.1 RTM, this servicing release fixes the following issues:
  • A folder lock issue that occurs when a user logs off from a session and then logs back on while he or she has multiple sessions running simultaneously.
  • Mounting an App-V package with many files takes longer than 5 seconds and fails. Provides a registry key to override the default time-out. (See Release Notes for App-V 5.1 for detailed information.)
  • Fixes an issue in which publishing a new package for the same application removes the shortcut.
  • Fixes an issue in which sorting packages by date is not performed correctly in the Server Management console UI.
  • Fixes an issue in which packages cannot be added in the Server Management console UI.
For MBAM 2.5 SP1, this servicing release adds the following functionality:
  • Adds support for the BitLocker XTS-AES encryption type
  • In the self-service portal, automatically inserts the dashes in the recovery key ID

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that's described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section doesn't appear, submit a request to Microsoft Customer Service and Support to get the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that don't qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:


  • The downloadable file for App-V 5.1 has the form <Hotfix ID> _intl_i386_zip.exe and contains installers for both x86-based and x64-based architectures. See the names for the downloaded files under the "File Information" section.
  • The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you don't see your language, it's because a hotfix isn't available for that language.


  • 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.

Registry information

To apply this hotfix, you don't have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix contains HF02 for AGPM 4.0 SP3, HF06 for APP-V 5.1, and HF02 for MBAM 2.5 SP1.


Microsoft has confirmed that this is an update in the Microsoft products that are listed in the "Applies to" section.

More Information

Note This servicing release includes update installers for AGPM 4.0 SP3, App-V 5.1 RTM, and MBAM 2.5 SP1.

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 ensure a successful update. To extract the associated .msp file, run the following command:
AppV5.1RTM_Client_KB3168628.exe /LAYOUT
Important If you try to apply this update by running the AppV5.1RTM_Client_KB3168628.exe file instead of the (extracted) associated .msp file, you may receive the following error message:
Setup failed while scanning the system for prerequisites. The update only applies to App-V client version: ''. The AppV client is not present on this computer.

File information 

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File nameBuild versionFile sizeDatePlatform
File nameBuild versionFile sizeDatePlatform
Appv5.1rtm_client_kb3168628.exe5.1.115.041,012,16822-Sep-16x86 & x64
Appv5.1rtm_rds_kb3168628.exe5.1.115.041,012,23222-Sep-16x86 & x64
File nameBuild versionFile sizeDatePlatform
File nameBuild versionFile sizeDatePlatform
File nameBuild versionFile sizeDatePlatform


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