The Win10 cumulative updates are out

Topic

New Reply

KB articles are out. (Thanks, MN!) KB 3194798 for 1607 brings the OS build number up to 14393.321 KB 3192441 for 1511 brings the OS build number up to
[See the full post at: The Win10 cumulative updates are out]

Reply | Quote

Replies

Any bets on what breaks this month?

Reply | Quote

October 2016 Patch Tuesday Win10 1607 now is OS Build 14393.321 downloaded and installed successfully for me. Entire process took 45 minutes to complete. Download slowed to a crawl at 84-95% so be patient about it! You might think it is stuck when in fact it taking it’s sweet time. All is stable and good now. Loving Win10 and all updates. Semper fidelis.

Reply | Quote

Woody,

Any idea what happens with an Edge patch when Edge has been removed?

Reply | Quote

I know I have said this before, but I have wushowhide installed and working and ConfigureAutomaticUpdates.exe installed. Based on the past, when I saw Defcon 2 I didn’t even check for updates, I just went on and worked. But at 1802 I got the dreaded “restart and update” message. Oh well, I’m now an unpaid Beta tester. The only difference I’ve seen so far is a little hard to explain. The previous update caused my screen short cut icons to act strangely. The little blue curved arrow in a white box would change to a white check mark in a green circle and then to a white x and then a little white block with what seemed like two people figures. This had no discernable pattern. Since the current update that has stopped. Any ideas?

Reply | Quote

Don’t know just yet.

Have you blocked updates for Win10? http://www.infoworld.com/article/3053701/microsoft-windows/block-windows-10-forced-updates-without-breaking-your-machine-part-2.html

Reply | Quote

Not a clue.

Reply | Quote

I’m at 1511 Build 10586.589
Is the the month to show and install > Feature update to Windows 10 Version 1607

Reply | Quote

I’ve blocked updates for Win10 per the instructions at http://www.infoworld.com/article/3053701/microsoft-windows/block-windows-10-forced-updates-without-breaking-your-machine-part-2.html.

That enabled me to prevent the automatic installation of Feature Update 1607 and Update for Windows 10 Version 1511 for x64-base Systems (KB3150513).

But, I now have a notice that restart is required to install Cumulative Update for Windows 10 Version 1511 for x64-based Systems (KB3192441).

So, it seems that the blocking isn’t entirely effective.

David

Reply | Quote

In a word, yes.

Reply | Quote

Just to make sure, did you uncheck the box marked “Apply repairs automatically” on the first screen when you blocked the update that later installed on its own? It happened to me in the past, but it was due to me forgetting to uncheck the box

Reply | Quote

Good point. It’s a really bad design…

Reply | Quote

On updates for yesterday..getting “Me – downgraded Me SpiLock Failed Request” error or something like that. Do you think this is related to monthly update?

Reply | Quote

bjm says:
October 11, 2016 at 10:40 pm

I’m at 1511 Build 10586.589
Is the the month to show and install > Feature update to Windows 10 Version 1607
————————
Is this the month to install > Feature update to Windows 10 Version 1607
What does 1607 buy me.
My 1511 is okay.
What do you recommend regarding 1607.
Will Mickysoft keep offering updates for 1511.

Reply | Quote

bjm says:
October 11, 2016 at 10:40 pm

I’m at 1511 Build 10586.589
Is the the month to show and install > Feature update to Windows 10 Version 1607
———————————
Is this the month for me to install Feature update to Windows 10 Version 1607.
What does 1607 buy me.
My 1511 is purring.
Will Mickysoft keep offering updates for 1511.
Yes, we’re at DEFCON 2.

Reply | Quote

Lea, thanks. I’ve tried to be very conscientious to uncheck that box, but it’s possible that I missed it. However, that’s not likely to be at the root of the unintended installation because I had not used wushowhide in the several weeks before.

My experience seems to parallel that described by Jim Lasch above. I.e., it appears that the blocking is not consistent.

David W

Reply | Quote

There’s something rather scary in this update KB 3192441 for Win 10 1511 called “Connected User Experience and Telemetry service”. (Yikes!) I want to avoid that until I hear more about how to completely disable it after 3192441 is eventually installed.

KB 3192441 had already been downloaded and was begging me to reboot to install it, so I had to use System Restore to go back to the previous Restore Point to avoid it. But I’ll have to act fast to disable WiFi to prevent it from downloading it all over again after I reboot to go back to the restore point.

That’s pretty drastic, but Microsoft has now lost about all of their credibility for maintaining their own software. I’m turning off all updates on all my Win10 systems for now. I already did that on Win7 because installing the cumulative update packs disables Bluetooth, which is important to me.

Reply | Quote

“A funny thing happened at work today” more like a cautionary tale for win 10 education 1511 and above ver. If you install kb3192441 as a standalone (from catalogue)you are no longer Cortana free. Yep on a test VHD with kb3192441 it installed M$s talkative companion (certainly not desired) cant speak for Enterprise and Branch ver. LTSB etc and the VHD was not connected to the network and was suitibly GPOL-ed, entirely possible that the WUD ver. may not do this.

Reply | Quote

Here’s my situation:

My main PC is a self-built Win 7 Home Premium SP(2)x64 hardwired to my router, haven’t decided on Group A or B yet, but fully updated on Monday night, then WU switched to “Never.”

I also have 2 old (2009) 16?”-class HP laptops that were Win 7 Home Premium pre-SP1 that I took the free Win 10 upgrade on in mid-July.

These laptops are used almost exclusively for surfing and watching DVDs on while my GF & I are being couch potatos, which isn’t often. No real personal info on them,and they are definitely not mission-critical.

I upgraded them to the 1607 AU version when it popped, and they are at the 14393.222 build right now.

When I update them, I shut down my desktop and unplug it from the router, then hardwire the laptops (they have 100Mb/s LAN cards in them,and they only manage ~40 Mb/s when on wi-fi.

They are as fortified against telemetry as I know how to make them: privacy settings, etc. maxed out and Spybot Anti-Beacon totally immunized.

So I guess my question is: Should I go ahead and update them to the 14393.321 or just hang loose a while and see what M$ manages to break?

As always, thanks for any help/advice/admonishments/whippings. 😉

Reply | Quote

Hang loose. Post coming.

Reply | Quote

After installing KB3192441 I wanted to do a clean-up: Disk Clean-up said there were 3.99TB of old Windows Update files. My SSD is only 32GB!
Now I see more people having this issue. What’s going on?
I did the clean-up anyway, took about 10 minutes and now it’s all fine.

Reply | Quote

Yep, I’m seeing that reported all over the place – although my machines are OK.

I need to get an article put together for InfoWorld on this very topic.

Reply | Quote

Just FYI: the Connected User Experience and Telemetry service isn’t new. It’s been there since 1511 was released, and even then, it wasn’t new. In 1511, they renamed a diagnostic tracking service to this new name.

The update is just changing something with the service.

Reply | Quote

Win10 1511. Today Belarc advised I was shy 3192441 and 3194343. After system image + DEFCON 2 aware. Installed 3192441, 3194343 and 890830.
wushowhide is gold.
Woody for President.
🙂

Reply | Quote

Accidental on my NUC, but I also got the updates. It all happened in the background, and restart was fast. But remember, this is a powerful core-i5 system with SSD and loads of RAM (16GB). So it’d better do updates fast!

Reply | Quote

For me, wushowhide works just fine, as long as Metered Connection is also used. My mistake was not closing the connection and not running wushowhide on the NUC after some sort of experiment with the Windows Store Apps and their updating mechanism (totally unrelated to Ms Updates and its mechanism). So my accidental updating was not a failure of wushowhide. It was User Error.

Reply | Quote