Latest:   #    1909 1903 1809 1803 1709 Notes

Sept

2019

  none

4 issues fixed

6 issues fixed

11 issues fixed

19 issues fixed

 List updated through the November updates.

Note1: You should not depend on the accuracy of my interpreting Microsoft documentation when it comes to these updates, especially when it comes to security issues; always go to the source at Microsoft when in doubt. The information here is a best effort view of items that might be of importance to customers that use Microsoft App-V.

Note2: There is no official list of Fixes affecting App-V for Windows 10 (and Server 2016+) since the App-V client was baked into the OS. Fixes appear in the normal monthly (and abnormal in-between) roll-ups.  This list is my best attempt at combing through the release notes to give you a clue what to look out for.  Of  course, anything can affect App-V or apps running under App-V, but these are the ones specifically hitting App-V and components used only with App-V.  You only need to get your OS to the latest roll-up date to get all of the fixes.

If an OS version box for an issue says "none" it means we didn't find a fix for that OS version.  It might be because the problem didn't exist there, or that Microsoft hasn't released a fix for that OS version. WE DON'T KNOW most of the time which it is.

Issue 1909 1903 1809 1803 1709 Notes

'Addresses an issue that prevents a Microsoft App-V application from opening and displays a network failure error. This issue occurs under certain circumstances, such as when a system's battery is low or there is an unexpected power failure.'

none

Sept 26, 2019

KB4517211 (OS Build 18362.387)

Sept 24, 2019

KB4516077

(OS Build 17763.774)

Sept 24, 2019

KB4516045

(OS Build 17134.1039)

Sept 24, 2019

KB4516071

(OS Build 16299.1420)

The described issue is listed as resolved in both the Sept patches AND the July patches for 1903 and August for 1809/1803.  Use the September one to be sure.

'Addresses an issue that prevents Microsoft App-V from handling a parameter of the CreateProcess API properly, which prevents the virtual process from opening.'

none

Sept 26, 2019

KB4517211 (OS Build 18362.387)

none

none

none

 

"Addresses an issue that prevents Microsoft Application Virtualization (App-V) scripting from working if you run it when you’re not connected to a domain controller (DC). App-V scripting also fails when you run it in an environment that only contains Microsoft Azure Active Directory. "

"Addresses an issue that prevents an App-V application from opening if the client is offline and a startup script is defined for the App-V application."

none

July 26, 2019

KB4505903 

(OS Build 18362.267)

July 22, 2019

KB4505658

(OS Build 17763.652)

July 16, 2019

KB4507466

(OS Build 17134.915)

July 16, 2019

KB4507465

(OS Build 16299.1296 )

These two items appear independently in the same KB for 1903, but only the first text appears in the 1809/1803/1709 KBs. They appear to be slightly different situations of the same problem, likely fixed with the same code change in all cases. 

Wow!  This has been a long time feature request (well, we documented it as a bug but were told that it was per-design).  Presumably this was addressed for the Azure Active Directory scenarios that are not co-managed. But it should mean that App-V scripts now work on non-domain joined machines.

"Addresses an issue that causes Office 365 applications to stop working after opening when they are deployed as App-V packages. " none

June 27, 2019

KB4501375

(OS Build 18362.207)

June 18, 2019

KB4501371

(OS Build 17763.592)

June 18, 2019

KB4503288

(OS Build 17134.858)

June 18, 2019

KB4503281

(OS Build 16299.1237)

 
"Addresses an issue that fails to update a user hive when you publish an optional package in a Connection Group after the Connection Group was previously published." none

none

June 18, 2019

KB4501371

(OS Build 17763.592)

June 18, 2019

KB4503288

(OS Build 17134.858)

June 18, 2019

KB4503281

(OS Build 16299.1237

 

"Fast restart of VirtualApp causes error 0xc0000225"

Also described as this in some articles:

"Addresses an issue that locks a user account when you move applications to a shared platform using App-V."

none

none

March 1, 2019
KB4482887
March 19, 2019
KB4489894
March 19, 2019
KB4489890

Use the credentials of a local admin to create and set the following registry key:
    Registry subkey: HKLM\SOFTWARE\Microsoft\AppV\MAV\Configuration
    Registry key name: MaxAttachWaitTimeInMilliseconds
    Registry Type: DWORD

Set the value to a nonzero will enable the fix. The default is zero, the maximum value is 10,000 (without commas set in the registry) A MaxAttachWaitTimeInMilliseconds value of 1 is often sufficient to eliminate application startup failures

See: KB4494206

Addresses an issue that fails to update a user hive when you publish an optional package in a Connection Group after the Connection Group was previously published.

none

none

March 1, 2019
KB4482887
Feb 19, 2019
KB4487029
Feb 19, 2019
KB4487021

 

Addresses an issue that can cause App-V packages to fail because of a missing file or DLL error

none

none

none

October 24, 2018
KB4462933

October 18, 2018
KB4462932

 

Addresses an issue in which connection group folders are not properly merged.

none

none

none

October 24, 2018
KB4462933

none

This issue is believed to have started with Feb 2018 updates; it made connection groups useless until fixed!

Addresses an issue that prevents the App-V client’s scheduled task from syncing if the Device Guard lockdown policy is enabled.

none

none

none

October 24, 2018
KB4462933

September 26, 2018
KB4457136

 

Addresses performance regression in App-V, which slows many actions in Windows 10

none

none

none

June 26, 2018
KB4284848

June 21, 2018
KB4284822

 

Addresses an issue with the April 2018 Windows Servicing update that causes App-V Scripts (User Scripts) to stop working.

none

none

none

May 8, 2018
KB4103721

none

 

Addresses an issue that causes an access violation in Internet Explorer when it runs on the Microsoft Application Virtualization platform.

none

none

none

none

April 10, 2018
KB4093112

 

Addresses an issue that might cause the App-V service to stop working on an RDS server that hosts many users.

none

none

none

none

April 10, 2018
KB4093112

 

Addresses an issue where user accounts are locked when applications are moved to a shared platform using App-V (e.g., XenApp 7.15+ with Windows Server 2016, where Kerberos authentication isn't available).

none

none

none

none

April 10, 2018
KB4093112

 

Addresses issue where the App-V client didn't read the policy for SyncOnBatteriesEnabled when the policy was set using a Group Policy Object (GPO).

none

none

none

none

February 13, 2018
KB4074588

 

Addresses issue where the Supported On field for the Enable App-V Client policy is blank in the Group Policy editor.

none

none

none

none

February 13, 2018
KB4074588

 

Addresses issue where the user’s hive data in the registry is not maintained correctly when some App-V packages belong to the connection group.

none

none

none

none

February 13, 2018
KB4074588

 

Provides additional logging for administrators to take action, such as picking a proper configuration for their App-V package, when there are multiple configuration files for a single package

none

none

none

none

February 13, 2018
KB4074588

 

 

Addresses issue with App-V packages that aren't compatible with registry virtualization using kernel containers. To address the issue, we changed the registry virtualization to use the earlier (non-container) method by default.

none

none

none

none

February 13, 2018
KB4074588

Customers who would like to use the new (kernel container) method for registry virtualization can still switch to it by setting the following registry value to 1:

    Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\Compatibility

    Setting: ContainerRegistryEnabled

    DataType: DWORD