{"id":19783,"date":"2016-07-26T11:46:55","date_gmt":"2016-07-26T10:46:55","guid":{"rendered":"https:\/\/aidanfinn.com\/?p=19783"},"modified":"2016-07-26T11:50:55","modified_gmt":"2016-07-26T10:50:55","slug":"kb3172614-to-replacefix-hyper-v-installations-broken-by-kb3161606","status":"publish","type":"post","link":"https:\/\/aidanfinn.com\/?p=19783","title":{"rendered":"KB3172614 To Replace\/Fix Hyper-V Installations Broken By KB3161606"},"content":{"rendered":"

Microsoft released a new update rollup<\/a> to replace the very broken and costly (our time = our money) June rollup, KB3161606<\/a>. These issues affected Hyper-V on Windows 8.1 and Windows Server 2012 R2 (WS2012 R2).<\/p>\n

It\u2019s sad that I have to write this post, but, unfortunately, untested updates are still being released by Microsoft. This is why I advise that updates are delayed by 2 months.<\/p>\n

In the case of the issues in the June 2016 update rollup, the fixes are going to require human effort \u2026 customers\u2019 human effort \u2026 and that means customers are paying for issues caused by a supplier. I\u2019ll let you judge what you think of that (feel free to comment below).<\/p>\n

A month after news of the issues in the update became known (the update rollup was already in the wild for a week or two), Microsoft has issued a superseding update that will fix the issues. At the same time, they finally publicly acknowledge the issues in the June update:<\/p>\n

\"image\"<\/a><\/p>\n

So it took 1.5 months, from the initial release, for Microsoft to get this update right. That\u2019s why I advise a 2 month delay on approving\/deploying updates, and I continue to do so.<\/p>\n

What Microsoft needs to fix?<\/p>\n