Microsoft releases then yanks KB 4032188, a cumulative update for Creators Update, build 15063.501

Topic

New Reply

I’m seeing some sporadic reports, including this one from Bogdan Popa at Softpedia. I expected a cumulative update for 1703 on Tuesday – even mentione[See the full post at: Microsoft releases then yanks KB 4032188, a cumulative update for Creators Update, build 15063.501]

Reply | Quote

Replies

Similar thing happened with 1607 cumulative KB4025334, support changelog was released one day before the update

someone hit the button too soon, or a last “second” bug? 😀

Reply | Quote

But to me it’s very strange that MS designated 1703 as CBB, while this big trove of known bug patches was waiting in the wings.

I’m starting to think the CBB decision is more political than technical.

Reply | Quote

4 months passed, you know… 😉

Fractal Design Pop Air * Thermaltake Toughpower GF3 750W * ASUS TUF GAMING B560M-PLUS * Intel Core i9-11900K * 4 x 8 GB G.Skill Aegis DDR4 3600 MHz CL16 * ASRock RX 6800 XT Phantom Gaming 16GB OC * XPG GAMMIX S70 BLADE 1TB * SanDisk Ultra 3D 1TB * Samsung EVO 840 250GB * DVD RW Lite-ON iHAS 124 * Windows 10 Pro 22H2 64-bit Insider * Windows 11 Pro Beta Insider

Reply | Quote

Roughly

3 an 1/2 month precisely 😀

Reply | Quote

The number of days between CB and CBB has gone down precipitously:

 

 

1 user thanked author for this post.

MrBrian

Reply | Quote

They certainly can’t wait until the Fall Update comes out to declare 1703 CBB!! Ready or not….

Reply | Quote

Bugs will continue to surf up, they never end 🙂
besides, they didn’t want to delay it for one more month, because refreshed CBB media must have patch tuesday cumulative (either 2017-07 or 2017-08), not a non-security one

Reply | Quote

Yep. All the more reason why I would’ve expected MS to move to 10563.501 before declaring CBB.

Reply | Quote

Running winver on this system shows “Version 1703 (OS Build 15063.483)” and “Settings”, in “Update & Security”, “Windows Update” “Update history” only shows:

v Quality Updates (1)
2017-07 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4025342)
Successfully installed on 7/29/2017
v Other Updates (1)
Feature update to Windows 10, version 1703
Successfully installed on 7/28/2017

In “Advanced Options”, “Choose when updates are installed” shows that it is set to “Current Branch for Business”.

HP Compaq 6000 Pro SFF PC / Windows 10 Pro / 22H2
Intel®Core™2 “Wolfdale” E8400 3.0 GHz / 8.00 GB
HP ProDesk 400 G5 SFF PC / Windows 11 Pro / 23H2
Intel®Core™ “Coffee Lake” i3-8100 3.6 GHz / 16.00 GB

Reply | Quote

Except KB4025334 for v1607 was made available a day or two later on WU & MUC while KB4032188 for v1703 is still non-existent, abbodi86.

1 user thanked author for this post.

abbodi86

Reply | Quote

Are we at MS-DEFCON 2 for the Outlook patches that were just released Thursday?

Reply | Quote

If you are using Outlook and are handicapped because of the previous bugs, I would apply the patch. Worst case, if it causes problems, it can be uninstalled.

If you are not using Outlook, or the bugs do not restrict what you need to do, you can afford to wait a few days.

2 users thanked author for this post.

woody, ht

Reply | Quote

Noting the release notes from that pulled update…

It’s nice that Microsoft is fixing their bugs and all, but should stuff like NTFS file corruption due to Data Deduplication or failures to connect to encrypted drives at bootup have ever made it to user systems in the first place?

It really feels like Microsoft thinks running Windows is all about, well, running Windows, not about doing what people need to do with their systems nor protecting their data. An operating system is not an application, and no one makes any progress if all they’re doing is spinning their wheels on Microsoft’s incessant series of builds and patches.

What if Microsoft released Windows 10 on the Current Branch and found that everyone had switched on the “Current Branch for Business” setting (whatever it’s called this week)?

Lifelong computer geek here… I used to be an enthusiastic pre-release tester. Then I descended from that to testing and tweaking the latest CB released code. Now I’m considering waiting until CBB before even trying out the next new version. Frankly I’m getting Windows 10 update fatigue big time. Why is this just not exciting any more?

I’ve never felt Win 10 has gotten good enough – even the CBB releases – to run my actual hardware nor have they released any “must have” features yet, in my view. I’m only running it in a virtual machine, while Win 8.1 and 7 are still my preferred choices for my hardware systems.

Sigh.

-Noel

1 user thanked author for this post.

dononline

Reply | Quote

I honestly don’t know how business/enterprise actually runs 10 or even considers running it.

Since we have more Macs than we do 10 machines in our domain, we haven’t added any of the ADMX files to our DC’s. In an effort to catch up, I was about to do so this morning…until I realized they’ve released ADMX files for each version of 10 up until this point. I had an ADMX installer for 1511, and then found out there are newer ones for 1607 and 1703.

Why? Why is this necessary? Let me take a swing here and say “because they move things around”, for no reason other than to keep everyone guessing where they’re going to jump next.

This is absurd. They may as well just change the nomenclature and say each update of 10 is a dot update. 10.1, 10.2 now we’re at, what, 10.3 and the FCU is 10.4. At least then, it would make slightly more sense.

2 users thanked author for this post.

dononline, woody

Reply | Quote

Even more damning when you realize that MS declared 1703 “Current Branch for Business” (or its equivalent) BEFORE releasing these patches.

This is really getting crazy.

4 users thanked author for this post.

dononline, Noel Carboni, zero2dash, EyesOnWindows

Reply | Quote

Looks like Microsoft is relying far too much on the infinite monkey theorem. Firstly to produce their patches and secondly, rather than following a reliable QA process involving regression testing, they’re using the whole world to see if those patches work. Come on Microsoft, replace your leadership with AI–it has got to be better than what you have now!

Given an infinite length of time, a chimpanzee punching at random on a typewriter would almost surely type out all of Shakespeare’s plays. So why would that not work to produce a working patch? Hint–they are much too slow!

HP Compaq 6000 Pro SFF PC / Windows 10 Pro / 22H2
Intel®Core™2 “Wolfdale” E8400 3.0 GHz / 8.00 GB
HP ProDesk 400 G5 SFF PC / Windows 11 Pro / 23H2
Intel®Core™ “Coffee Lake” i3-8100 3.6 GHz / 16.00 GB

Reply | Quote

Still using Windows 8.1 and running all the necessary stuff efortlessly…

My wife’s tablet is on 1703 since yesterday and she’s not impressed with Edge performance compared to AU.

Reply | Quote

KB4032188 is available.

Reply | Quote

KB4032188 just showed up. Didn’t get it before. Hiding for now

Reply | Quote

I’m  sitting on 1511, all fat and sassy. Don’t care about security. Don’t are about the latest features. Don’t care about MS. All I need is a computer and OS that can run the programs that I want. Thank Bill Gates for WUSHOWHIDE.

 

P.S. I do worry that big bad MS will sabotage my system and leave me stranded. It’s not paranoia if they really are all out to get you.

Reply | Quote

KB4032188 broke support for my keyboard Merc Stealth in windows 10. It’s a legacy device so there will be no new updates from Steel Series. If you are still using this keyboard don’t do the update.

Reply | Quote