Windows 10: Cumulative Update KB4032188 Windows 10 v1703 Build 15063.502

Same here on 3 laptops, even created a separate thread: KB 4032188 issue...
First time I have a problem with W 10 updates, no matter of the build.

Any clues??

 

^^Disable any of your anti-virus software.

 

My old Acer laptop is reporting as up to date with no sign of the latest offering. Could it be that it is deemed to old (nearly 11yr old) to automatically receive these ?

My Dell is set to defer for 7 days which gives me chance to see what mayhem the latest updates are/are not causing *Smile

 

I doubt it's too old, but it might have been screened for hardware that got it pushed back in the rollout schedule. Just like my 12+ yrs old Dell desktop that didn't get the update until a couple weeks ago. And this was still too early, since it rendered this machine unable to connect to the internet ("Broadcom" issue).

 

I would like to see a list of known bugs not yet fixed.

 

I'm pretty sure the Acer would be to old to receive feature updates such as going from AU to CU but I was wondering about the frequent cumulative such as here. I think someone mentioned in the thread that this wasn't a security related update so maybe that is why this one has been skipped.

 

Mooly, are you already on CU? If so did you manually upgrade to CU? Not sure now from your latest comment.

 

Yes, CU and yes, a clean install. Other updates have all been picked OK apart from this one.

 

Updated, so far so good.

 

Installed fine. Only issue was Definition Update for Windows Defender - KB2267602 (Definition 1.249.685.0) installed twice for some reason and App Readiness was a critical event in RH.

Anybody else have either of them? First time regarding the Defender definitions

 

My Acer laptop is also the same sort of age (bought in 2007) and it has been blocked from getting Creator's Update due to the Broadcom issue which MartinO mentions.
Old computers not yet compatible with 1703 (Broadcom 440x driver)

But I think a fix is now in the Cumulative Update which is the subject of this thread, so it may come through soon. Although I may go straight to the '1709' Creators Update in a few weeks' time as the laptop needs a clean install in any case.

 

My Acer has an Atheros wireless adapter and W10 has always taken around 2 hours to install because of a faulty driver. I started reporting this back to MS nearly 3yrs ago.

Help ! System Interrupts are running are crippling CPU Solved - Windows 10 Forums

stop W10 installing specific driver during installation? - Windows 10 Forums

On the Acer I found much later that pressing the WiFi button a few times at the appropriate point in the installation seemed to disable things and the process speeded up.

The problem was still not solved even with the CU and I had to go through the same performance again.

 

Being curious (and with time on my hands) I got my test machine (15063.483) to check for updates on a metered connection, then waited to see what would happen. It duly found KB4032188 and went straight to 'downloading', crawling painfully slowly to 1% then stuck at 2%. Task Manager showed it was actually downloading something occasionally over the WiFi , but not much and not very often. I presumed these were the few bits that MS deemed 'required to keep Windows running smoothly'.

I waited (and waited) to see what, if anything, might eventually get installed - nothing, it turns out. Instead, after waiting quarter of an hour it eventually gave the 'Updates are available. We'll download them when you are not using a metered connection' message and the 'Download' button.

Instead of clicking 'Download' I restarted the PC, just to see if something got installed after all. Nothing, but some part of the update had obviously been downloaded (though not installed) because when I checked for updates again it skipped straight to the message and the 'Download' button.

Curious. Why would it have downloaded something it can't then install? 1703's new idea of overriding metered connections to 'download only those updates required to keep Windows running smoothly' still seems to be a 'work in progress'. *Smile

 

i still have not gotten this update

 

So on my 12yr old Dell today finally got around to doing the clean install of CU next to my existing AU 1532 which goes back to Windows 7.

Boot and install from USB drive on my 2nd SSD went surprisingly quick, and after a few restarts everything was up and running with no issues whatsoever. Just in case I had disabled the Broadcom NIC in the BIOS. First install (despite it looking and finding Updates in the process) identified itself as 15063.0, but after another round of WUs that got stuck at 17% upon which I manually restarted, it booted into 15063.502. Enabled the NIC and as expected the Broadcom issue is fixed. Doesn't come as a surprise that the new CU feels a bit "snappier" overall than the old AU. Next course of action will be to leave the old junk behind and migrate from AU to CU.

This is what the boot manager looked like right after the install.