{"id":2143,"date":"2017-01-25T19:29:13","date_gmt":"2017-01-25T18:29:13","guid":{"rendered":"http:\/\/borncity.com\/win\/?p=2143"},"modified":"2024-10-03T00:26:46","modified_gmt":"2024-10-02T22:26:46","slug":"windows-10-version-1607-update-kb3211320","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2017\/01\/25\/windows-10-version-1607-update-kb3211320\/","title":{"rendered":"Windows 10 Version 1607: Update KB3211320"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline\" src=\"http:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2015\/01\/win102.jpg\" width=\"58\" align=\"left\" height=\"58\">[<a href=\"http:\/\/www.borncity.com\/blog\/2017\/01\/25\/windows-10-version-1607-update-kb3211320\/\" target=\"_blank\" rel=\"noopener\">German<\/a>]Microsoft has released update KB3211320 for Windows 10 Version 1607 on January 24, 2017. Again this update is still undocumented and suspicious. Here are a few details. <\/p>\n<p><!--more--><\/p>\n<p><strong>Addendum:<\/strong> Microsoft has released a KB3211320 description yet \u2013 it's a servicing stack update \u2013 some assumption made below are wrong.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" alt=\"\" src=\"https:\/\/ssl-vg03.met.vgwort.de\/na\/ce5007e7464244809cda15e18a362ad3\" width=\"1\" height=\"1\">I haven't recognized this update until I stumbled upon a German <a href=\"https:\/\/www.deskmodder.de\/blog\/2017\/01\/25\/kb3211320-changelog-windows-10-1607-steht-zum-download-bereit-2\/\" target=\"_blank\" rel=\"noopener\">deskmodder.de<\/a> blog post. The update is released on January 24, 2017 (Microsoft Update Catalog says 01\/23\/2017). <a href=\"https:\/\/www.catalog.update.microsoft.com\/ScopedViewInline.aspx?updateid=2d02246e-6c4f-4552-8c2c-43a427cfa5d8\" target=\"_blank\" rel=\"noopener\">Update details<\/a> says \"install this update to fix issues with Windows and references to a knowledgebase article that doesn't exists. <\/p>\n<p>The description in Microsoft Update Catalog (tab <em>Package Details<\/em>) says, the new patch exchanges updates <a href=\"https:\/\/support.microsoft.com\/de-at\/help\/3199986\/servicing-stack-update-for-windows-10-version-1607-and-windows-server-2016-october-27,-2016\" target=\"_blank\" rel=\"noopener\">KB3199986<\/a> (Servicing Stack Update Oktober 27, 2016) and <a href=\"https:\/\/support.microsoft.com\/de-de\/help\/3199209\/servicing-stack-update-for-windows-10-version-1607-october-18,-2016\" target=\"_blank\" rel=\"noopener\">KB3199209<\/a> (Oktober 18, 2016). The screenshot below shows that this update was installed (silently) on January 24, 2017.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/web.archive.org\/web\/20191011010511\/https:\/\/c75.imgup.net\/UpdateKB32971b.jpg\"><\/p>\n<p>But update <a href=\"https:\/\/support.microsoft.com\/de-de\/help\/4009938\/january-10-2017-kb3213986-os-build-14393-693\" target=\"_blank\" rel=\"noopener\">KB3213986<\/a> (released January 10, 2017) has been installed on January 25, 2017. Don't know, why the update released on early January was installed after the yesterday update. <\/p>\n<h3>No details and confusion<\/h3>\n<p>Because there are not details provided from Microsoft, some <a href=\"https:\/\/www.tenforums.com\/windows-10-news\/75700-critical-update-kb3211320-windows-10-version-1607-a.html\" target=\"_blank\" rel=\"noopener\">sites was pointing<\/a> to <a href=\"https:\/\/technet.microsoft.com\/en-us\/library\/security\/ms17-jan.aspx\" target=\"_blank\" rel=\"noopener\">Microsoft Security Bulletin Summary for January 2017<\/a>, where a critical update for Microsoft Edge (3211320) was named. But it seems that the association of the number 3211320 to KB3211320 is wrong. <\/p>\n<p>Microsoft Update Catalog says clearly it's a package, that exchanges prior servicing stack updates. I've downloaded the package from update catalog and have had a brief look at the details. The .mum manifest files says it's a servicing stack update, and a restart isn't required. <strong>Addendum:<\/strong> The servicing stack update is confirmed in <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/3211320\/servicingstackupdateforwindows10version1607andwindowsserver\" target=\"_blank\" rel=\"noopener\">KB3211320<\/a> description.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/web.archive.org\/web\/20191011010510\/https:\/\/d00.imgup.net\/UpdateKB3218b4.jpg\"><\/p>\n<p>But I was puzzled after looking into the windows shown above. Servicing stack updates are normally uninstallable. But update KB3211320 is shown in the uninstall list \u2013 and I (wrongly) thought I had seen an uninstall button \u2013 but the update is clearly not uninstallable. Overall, there are many questions and Microsoft failed again to deliver a description just in time. Woody Leonhard aked similar <a href=\"https:\/\/web.archive.org\/web\/20170604091114\/http:\/\/www.infoworld.com:80\/article\/3161452\/microsoft-windows\/conflicting-descriptions-document-windows-10-patch-kb-3211320.html\" target=\"_blank\" rel=\"noopener\">questions<\/a> at InfoWorld. <strong>Addendum:<\/strong> Ok, the <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/3211320\/servicingstackupdateforwindows10version1607andwindowsserver\" target=\"_blank\" rel=\"noopener\">KB3211320<\/a> description is now online (I guess 24 hours after releasing the update).<\/p>\n<h3>Some damages after installing this update?<\/h3>\n<p>During writing this blog post, I stumbled upon this <a href=\"https:\/\/answers.microsoft.com\/en-us\/windows\/forum\/windows_10-update\/2017-jan-24-windows-10-pro-version-1607-updates\/941aeb73-20e8-4583-bc25-2d8a091b229a\" target=\"_blank\" rel=\"noopener\">Microsoft answers forum thread<\/a> where users are complaining about that update. <\/p>\n<ul>\n<li>One user wrote that he need to re-register Microsoft Office, Excel runs unstable since update installation and Microsoft Edge has no more internet access.\n<li>Another user lost his pinned icons on taskbar and start menu.\n<li>Another user wrote that his second monitor did not work after installing this update. <\/li>\n<\/ul>\n<p>Don't know, maybe bad karma at users side this time. I could not detect similar behavior in my virtual machine. If you have issues with this update, drop a comment. <\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]Microsoft has released update KB3211320 for Windows 10 Version 1607 on January 24, 2017. Again this update is still undocumented and suspicious. Here are a few details.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[22,2],"tags":[640,76],"class_list":["post-2143","post","type-post","status-publish","format-standard","hentry","category-update","category-windows","tag-update-kb3211320","tag-windows-10"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/2143","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=2143"}],"version-history":[{"count":1,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/2143\/revisions"}],"predecessor-version":[{"id":35316,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/2143\/revisions\/35316"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=2143"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=2143"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=2143"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}