{"id":8779,"date":"2017-08-17T04:30:12","date_gmt":"2017-08-17T12:30:12","guid":{"rendered":"http:\/\/www.palada.net\/index.php\/2017\/08\/17\/news-2552\/"},"modified":"2017-08-17T04:30:12","modified_gmt":"2017-08-17T12:30:12","slug":"news-2552","status":"publish","type":"post","link":"http:\/\/www.palada.net\/index.php\/2017\/08\/17\/news-2552\/","title":{"rendered":"Where\u2019s the KB 4034661 jumbo bug fix for Win10 Anniversary Update?"},"content":{"rendered":"

<\/p>\n

Credit to Author: Woody Leonhard| Date: Thu, 17 Aug 2017 04:33:00 -0700<\/strong><\/p>\n

Wednesday night, Microsoft claims, it issued KB 4034661<\/a> for Windows 10 Anniversary Update, bringing version 1607 up to build 14393.1613. It was supposed to go out the Automatic Update chute. But as of early Thursday morning, U.S. time, nobody\u2019s seen it. There may be a good reason why. Or maybe not. Such are the vagaries of patching Windows.<\/p>\n

It\u2019s a laundry-list patch, rolling out on a Wednesday (or Thursday, or \u2026), nine days after the regular Patch Tuesday patch, KB 4034658 wiped out the Update History<\/a> on many Win10 Anniversary Update machines. The KB 4034661 article<\/a> lists dozens of small bug fixes (that\u2019s \u201cquality improvements\u201d in Microsoft Speak).<\/p>\n

It also says that this new patch wipes out your Update History and drives WSUS systems nuts. Microsoft still hasn\u2019t fixed that bug and, since all Win10 updates are cumulative, the sins of the father are vested upon the son.<\/p>\n

We do<\/em><\/strong> know that the new patch is available in the Microsoft Update Catalog<\/a>. But at this point it\u2019s anyone\u2019s guess if this notice in the KB article:<\/p>\n

This update will be downloaded and installed automatically from Windows Update.<\/p>\n

… is right, wrong, wishful thinking, or a viable threat.<\/p>\n

The last time Microsoft issued a huge bunch of bug fixes for 1607, just a month ago, the KB 4025334<\/a> article explicitly said that the patch was only available for download. It never came down the Automatic Update chute. Instead, Microsoft let would-be beta testers download the package, install it, and see what broke before the big bunch of fixes rolled out on the next Patch Tuesday.<\/p>\n

That\u2019s a great idea, in my opinion. It’s exactly the method being used for Windows 7 and 8.1’s “Preview of Monthly Rollup” patches, except the Win10 cumulative update previews have been haphazardly documented and kicked into an untidy pile in the corner.<\/p>\n

Are we witnessing another implementation of a Win10 cumulative update preview? Is the documentation wrong? Is there another patch headed out the Automatic Update chute? Will Jon Snow … whatever. I guess we\u2019ll find out sooner or later.<\/p>\n

In the interim, my old advice stands<\/a>. It\u2019s still too early to install any August patches.<\/p>\n

Man, I wish Microsoft would rationalize its naming.<\/p>\n

Join the discussion on the AskWoody Lounge<\/a>.<\/em><\/p>\n

http:\/\/www.computerworld.com\/category\/security\/index.rss<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

<\/p>\n

Credit to Author: Woody Leonhard| Date: Thu, 17 Aug 2017 04:33:00 -0700<\/strong><\/p>\n

\n
\n

Wednesday night, Microsoft claims, it issued KB 4034661<\/a> for Windows 10 Anniversary Update, bringing version 1607 up to build 14393.1613. It was supposed to go out the Automatic Update chute. But as of early Thursday morning, U.S. time, nobody\u2019s seen it. There may be a good reason why. Or maybe not. Such are the vagaries of patching Windows.<\/p>\n

It\u2019s a laundry-list patch, rolling out on a Wednesday (or Thursday, or \u2026), nine days after the regular Patch Tuesday patch, KB 4034658 wiped out the Update History<\/a> on many Win10 Anniversary Update machines. The KB 4034661 article<\/a> lists dozens of small bug fixes (that\u2019s \u201cquality improvements\u201d in Microsoft Speak).<\/p>\n

To read this article in full or to leave a comment, please click here<\/a><\/p>\n<\/section>\n<\/article>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"colormag_page_container_layout":"default_layout","colormag_page_sidebar_layout":"default_layout","footnotes":""},"categories":[11062,10643],"tags":[714,10525],"class_list":["post-8779","post","type-post","status-publish","format-standard","hentry","category-computerworld","category-independent","tag-security","tag-windows"],"_links":{"self":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/8779","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/comments?post=8779"}],"version-history":[{"count":0,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/8779\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/media?parent=8779"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/categories?post=8779"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/tags?post=8779"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}