Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. December 2016 servicing release for Microsoft Desktop Optimization Pack

December 2016 servicing release for Microsoft Desktop Optimization Pack

View products that this article applies to.

Summary

This article describes the content of the December 2016 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, Remote Desktop Services (RDS) and Server, and Microsoft BitLocker Administration and Monitoring (MBAM) 2.5 Service Pack 1 (SP1).

Notes
 
  • The App-V Client is "in-box" starting in the Windows 10 Anniversary Edition, and it continues to use the App-V 5.1 Server.
  • 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.

Issues that are fixed in this update

For App-V 5.1 RTM, this servicing release fixes the following issues:
 
  • Group-specific functionality is incorrectly made available to other groups if the Optional feature is used.
  • Using Dynamic Virtualization, file handles are not closed when a shell extension is unloaded. This issue can cause Explorer.exe to keep DLL file handles after a shell extension unloads them. This can block upgrade of the shell extension.
  • After the first-time sync of a Connection Group (CG) on the device, newly added packages to the CG are not enabled.
  • When you install the App-V Server management database (DB) by using SQL scripts, an SQL error is reported. The workaround that was first documented in App-V 5.0 Service Pack 3 (SP3) is now incorporated into the SQL scripts to eliminate this error.
  • The FullVFSWriteMode tag in a Sequencer template is ignored. (This issue is not fixed in the update. However, it is fixed in the latest Sequencer installer. To get the installer, please contact your Microsoft Customer Service and Support representative.)
  • On the Server Management console, applying an action to a filtered subset of packages actually applies the action to all packages.

For MBAM 2.5 SP1, this servicing release fixes the following issues:
 
  • A SQL deadlock issue occurs when multiple users from different domains try to access the database at the same time.
  • A device that has a mounted, nonencrypted, removable drive (for example, an SD card) can cause increased CPU usage and the inability of the device to enter the low-power state.

Improvements that are made in this update

For App-V 5.1 RTM, this servicing release makes the following improvements:
 
  • The App-V 5.1 server update installer now links to the correct content (Privacy Policy and the "App-V 5.1" page).
  • The App-V Client, RDS, and Server now have the same build number.

For MBAM 2.5 SP1, this servicing release Makes the following improvements:
  For more information about the March 2017 Servicing release, go to March 2017 servicing release for Microsoft Desktop Optimization Pack.

↑ Back to the top

Resolution

Update 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 does not 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, go to the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note 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.

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, consider the following scenarios:
If you have the RTM version installed, you can apply this hotfix directly.
If you have HF01 or HF02 installed, you must uninstall the existing server components, install MBAM 2.5 SP1 Server RTM, and then install the server components of this hotfix.
 

Restart requirements

You must restart the computer after you apply this hotfix.
 

Replacement information

This hotfix contains HF07 for APP-V 5.1 and HF03 for MBAM 2.5 SP1 RTM.
 

Registry information

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

↑ Back to the top

More Information

This servicing release includes update installers for 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 make sure of a successful update. To extract the associated .msp file, run the following command: 
AppV5.1RTM_Client_KB3198158.exe /LAYOUT
Important If you try to apply this update by running the AppV5.1RTM_Client_KB3198158.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: '5.1.86.0'. The AppV client is not present on this computer.
File information

The global version of this cumulative update uses a Microsoft Windows Installer package to install the cumulative update. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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.

After the update is installed, the global version of this update has the file attributes, or a later version of the file attributes, that are listed in the following tables.

494601_intl_i386_zip.exe
 
File name Build version File size Date Platform
AppV5.1RTM_Client_KB3198158.exe 5.1.116.0 41,495,856 15-Nov-16 x86 & x64
AppV5.1RTM_RDS_KB3198158.exe 5.1.116.0 41,495,896 15-Nov-16 x86 & x64
AppV5.1RTM_Server_KB3198158.exe 5.1.116.0 4,578,280 15-Nov-16 x86 & x64


494602_intl_i386_zip.exe
 
File name Build version File size Date Platform
MBAM2.5SP1-Client-KB3198158-x86.msp 2.5.1126.0 1,581,056 03-Nov-16 x86
MBAM2.5SP1-Server-KB3198158-x86.msp 2.5.1126.0 5074944 03-Nov-16 x86


494603_intl_x64_zip.exe
 
File name Build version File size Date Platform
MBAM2.5SP1-Client-KB3198158-x64.msp 2.5.1126.0 1,634,304 03-Nov-16 x64
MBAM2.5SP1-Server-KB3198158-x64.msp 2.5.1126.0 5,074,944 03-Nov-16 x64

↑ Back to the top

Keywords: kbqfe, kbsurveynew, kbautohotfix, kbhotfixserver, kbfix, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 3198158
Revision : 8
Created on : 8/13/2018
Published on : 8/15/2018
Exists online : False
Views : 321