Issues we are still tracking:

KB30000061 is a kernel update:

KB3000061 fails to install on Server 2012:   Also impacting Windows 8.   Cases opened: 114101711916740 and 114101711915623

Status:  See in that thread, Microsoft engineer in the forum is asking for cbs.log files from impacted machines.  Some recommendations have been made, no solution at this time.

Two issues with KB2984972 – this is a patch to update the RDP restricted admin mode

“Heads up, KB2984972 on Server 2008R2 RD server caused issues with our Wyse thinclients – it caused them all to span desktops across multiple monitors rather than presenting multiple monitors to the host OS. After uninstalling & rebooting clients are presented with multiple monitors again.”  <<<< will impact MultiPoint Server as well too <<<<<

Another thread on the issue here:

Status:  Unknown if this is being investigated by Microsoft.  Have seen some updates from the thin client vendors, so unsure if this will be patched from the vendor side or from the Microsoft side.    If someone has a serverfault reputation of greater than 50 can you post in there and ask them to email me at (change the -at- to @) to set up a support case?  I really am unsure if there are cases being worked on regarding the thin client impact and I’d love to make sure they are.

App v and KB2984972 impact:   << case opened on this issue SRX 114101611907865.

  Status:  Known issue now documented

Known issues with this security update

  • Symptoms
    After you install this security update, virtualized applications in Microsoft Application Virtualization (App-V) versions 4.5, 4.6, and 5.0 may experience problems loading. When the problem occurs, 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 stop responding 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:


    How to back up and restore the registry in Windows

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

    For Microsoft Application Virtualization 5.0

    • Registry Key: HKLM\Software\Microsoft\AppV\Subsystem\ObjExclusions
      Value name: 93 (Or any unique value)
      Type: REG_SZ
      Data: TermSrvReadyEventExample
      For example, type the following command at an elevated command prompt to add the entry to a system running Application Virtualization 5.0:

      reg add HKLM\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: HKLM\SOFTWARE\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions
      Value name: 95 (Or any unique value)
      Type: REG_SZ
      Data: TermSrvReadyEvent

      For example, type the following command at an elevated command prompt to add the entry to an x86-based system running Application Virtualization 4.6:

      reg add HKLM\SOFTWARE\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions /v 95 /t REG_SZ /d TermSrvReadyEvent
    • For all supported x64-based systemsRegistry Key: HKLM\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions
      Value name: 95 (Or any unique value)
      Type: REG_SZ
      Data: TermSrvReadyEvent

      For example, type the following command at an elevated command prompt to add the entry to an x64-based system running Application Virtualization 4.6:

      reg add HKLM\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions /v 95 /t REG_SZ /d TermSrvReadyEvent

KB2949927 – the SHA-2 update: Also seeing issues with KB2949927 getting installed:  and

STATUS:  KB2949927 has been pulled from Microsoft update on 10/17/2014

Then KB2995388 8.1 cumulative update causing issues with VMware workstation:

Workstation 10 issue with recent Microsoft Windows 8.1 Update | VMware Workstation Zealot – VMware Blogs:
We noticed that a recent Windows 8.1 Update (KB2995388) may cause issues when running VMware Workstation on a Windows 8.1 host with this update installed. User will see an error message “not enough physical memory” when booting up a virtual machine

STATUS:  per the thread reinstalling vmware 10 will fix the issue, unsure if this patch will be redone or merely the recommendation will be to reinstall VMware

2990942 ASP. MVC security update
Microsoft Asp.Net MVC Security Update MS14-059 broke my build! – .NET Web Development and Tools Blog – Site Home – MSDN Blogs:

Windows Azure Pack: Cannot create Plans.:

Status:  Lots of upset developers.

Driver Patch released by vendor bricks users chips

FTDI appears to have used a recent Windows update to deliver the driver update to brick all cloned FTDI FT232s.

FTDI’s surprise new driver reprograms the USB PID to 0, killing the chips instantly.

The hardware hackers at Hack A Day first reported that a recent driver update deployed over Windows Update is bricking cloned versions of the very common FTDI FT232 [USB to UART] chip

Status:  A driver update delivered through Windows update supplied by a vendor was designed to nuke non genuine chips.  If suddenly your clients/customers start complaining that their USB devices are missing/won’t work, it may be due to this.  The vendor used the MU driver update channel to nuke unlicensed chips
 (Susan note:  despite what the Microsoft folks say I use the driver updates offered up to me via MU as indicators I need to look for vendor drivers, I do not install them on production machines due to too many years of being burnt by them)



Adobe update 11.0.9 causes problems with opening files across network shares.  Error message received is
“There was an error opening this document. The network path was not found.”

Status:  Workaround to issue – disable protected mode (which is not acceptable), otherwise use Foxit or CutePDF reader as an alternative.


4 Responses to October patch status report – 10 days past release

  1. I’ve posted a comment on the Server Fault thread directing any interested parties here.

    • Aaron Walters says:

      Thanks Harry.

      I got in contact with Susan and she setup a support case for KB2984972 causing dual display issues with Wyse thin client terminals.

  2. Rik de Vroom says:

    Not sure if anyone will be checking this; but the issue with KB2984972 has risen again on 2 of our clients servers. Both 2008 R2, but WITHOUT the KB2984972. Yet wyse thin-clients have a spanned screen. What other, more recent, update could be the culprit?

  3. Chris Burg says:

    Hi Rik

    We are in the same boat as you on this one, completed updates over the weekend and have our clients 35 wyse c10le spanning across dual screens now 🙁

    We removed the updates as per the above and still no luck 🙁

    Hoping for a solution from someone out there.