• Microsoft acknowledges permission problems with MS16-072 patches KB 3159398, 3163017, 3163018, 3163016

    It took 36 hours, but they came clean.

    InfoWorld Woody on Windows

    Rod Trent notes on WindowsITPro that there’s a PowerShell script that will go out and see if any of your domain’s computers are affected.

    UPDATE: Susan Bradley notes this “doesn’t have to be listed in the client side patches – Windows 10 for example. The fix for this group policy mess has to be done on the servers.  so 2012/2012 r2 is where the known issue stuff should be documented.”

    That means if you see the problem on your machine (client, not server), your admin has to solve the problem. And the solution is in the KB article directed to your admin.