The MDOP December servicing release is now available

We are pleased to announce that the MDOP December servicing release is available for immediate download.

Issues 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, unencrypted, 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 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 complete details please see the following:

3198158 - December 2016 servicing release for Microsoft Desktop Optimization Pack (

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Comments (7)
  1. Brian Smith says:

    I think there is still an issue with the reporting database scripts. I run them on the SQL server and it creates the database ok but when I run the App-V installer and select reporting server and fill out the correct details it gives me an error saying the database needs to be upgraded. Any workarounds to this?

  2. Rory says:

    Please make the new Sequencer installer available for download or make sure the Win10 ADK is updated at the same time that a new Sequencer is available.

  3. NP says:

    Does the MBAM fix deal with the SQL 2016 block during install?

  4. Andy Knowles says:

    As the client is only an update release to the 5.1 RTM client we still have to install the unsupported Visual C++ 2005 redistributable as a pre-requisite. Is this not a bizarre security oversight? It’s been out of support for months.

  5. Sandy says:

    Hello, what this mean “To apply this hotfix for MBAM 2.5 SP1, you must uninstall the existing server components, install the RTM version of MBAM 2.5 SP1 Server, and then install the server components of the hotfix. “? So if we already have MBAM 2.5 SP1 Installed in server, do I need to uninstall all the MBAM components and install only this December hotfix? Or if I have September Hotfix installed, do I need to uninstall the September Hotfix first, then install Dec. Hotfix? This “existing server components” is unclear for me.

  6. Waldy says:

    “Group-specific functionality is incorrectly made available to other groups if the Optional feature is used. ” Which optional feature please?

  7. Shaun says:

    Can this blog be maintained and updated?

Comments are closed.

Skip to main content