RUSH POST: Microsoft Convenience Update and VMware VMXNet3 Incompatibilities

Introduction

Posted on June 1, 2016 by Deji

Microsoft recently released a “Convenience Update” patch for Windows 7 and Windows Server 2008 R2 SP1. This update has incompatibility issues with virtual machines running on the VMware vSphere virtualization platform. This incompatibility is confined to one specific configuration scenario – It impacts VMs that use the VMware VMXNet3 virtual network adapter type.

Here is the incompatibility issue as described in Microsoft’s announcement of the Update:

Known issue 1 in this convenience rollup

Symptoms

A new Ethernet vNIC may be created with default settings in place of the previously existing vNIC, causing network issues. Any custom settings on the previous vNIC are still persisted in the registry but unused.

Resolution

To resolve this issue, uninstall the convenience rollup.

Status

Microsoft is investigating this issue to determine proper course of action with VMWare. To resolve this issue uninstall the convenience rollup. Further information will be posted here as the investigation continues.

Known issue 2

Symptoms

After you install this rollup, virtualized applications in Microsoft Application Virtualization (App-V) versions 4.5, 4.6, and 5.0 may have problems loading. When these problems occur, you may receive an error message that resembles the following:
Launching MyApp 100%

Note In this error message, MyApp represents the name of the App-V application.

Depending on the scenario, the virtualized app may freeze after it starts, or the app may not start at all.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows.

Resolution

To fix this known issue, configure the TermSrvReadyEvent registry entry on the computer on which the Microsoft Application Virtualization Client is installed.

For Microsoft Application Virtualization 5.0

Registry Key: HKEY_LOCAL_MACHINE\Software\Microsoft\AppV\Subsystem\ObjExclusions
Value name: 93 (or any unique value)
Type: REG_SZ
Data: TermSrvReadyEvent

Example
For example, type the following command at an elevated command prompt to add the entry to a system that is running Application Virtualization 5.0:
reg add HKEY_LOCAL_MACHINE\Software\Microsoft\AppV\Subsystem\ObjExclusions /v 93 /t REG_SZ /d TermSrvReadyEvent

For Microsoft Application Virtualization 4.6

For all supported x86-based systems

Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions
Value name: 95 (or any unique value)
Type: REG_SZ
Data: TermSrvReadyEvent

Example
For example, type the following command at an elevated command prompt to add the entry to an x86-based system that is running Application Virtualization 4.6:
reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions /v 95 /t REG_SZ /d TermSrvReadyEvent
For all supported x64-based systems

Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions
Value name: 95 (or any unique value)
Type: REG_SZ
Data: TermSrvReadyEvent

Example
For example, type the following command at an elevated command prompt to add the entry to an x64-based system that is running Application Virtualization 4.6:
reg add HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions /v 95 /t REG_SZ /d TermSrvReadyEvent

Rating: 5/5


Comments are closed.