We will update issues on this page for about a week or so as they evolve.We appreciate updates
US based customers can call Microsoft for free patch related support on 1-866-PCSAFETY

(*): ISC rating

We use 4 levels:

PATCH NOW: Typically used where we see immediate danger of exploitation. Typical environments will want to deploy these patches ASAP. Workarounds are typically not accepted by users or are not possible. This rating is often used when typical deployments make it vulnerable and exploits are being used or easy to obtain or make.

Critical: Anything that needs little to become "interesting" for the dark side. Best approach is to test and deploy ASAP. Workarounds can give more time to test.

Important: Things where more testing and other measures can help.

Less Important patches for servers that do not use outlook, MSIE, word etc. to do traditional office or leisure work.

The rating is not a risk analysis as such. It is a rating of importance of the vulnerability and the perceived or even predicted threats.

Two things people need to remember: First, this is the last month for Windows 2003 patches. Second, beginning in January 2016, Microsoft will only patch the most recent version of IE so the time to upgrade is now.

Microsoft has information in KB 2264107 about mitigating DLL search-path exploitation, titled "A new CWDIllegalInDllSearch registry entry is available to control the DLL search path algorithm." Since this month's batch included such an issue, I was surprised they didn't mention it as a workaround.

In my case, setting the system-wide CWDillegalinDLLsearch to its strictest setting, FFFFFFFF, did break one app, an old image editor, which I had to make an exemption for in the Registry. So test carefully if you decide to use this.

Updates trashed the virtual switch on one of my Hyper-V 2012R2 servers, resulting in a visit to the datacenter to fix. Proceed with caution! I don't know which update caused it but suspect the MS15-068 Remote Code Execution Vulnerabilities in Hyper-V.