Cumulative Update KB4464330 Windows 10 v1809 Build 17763.55 - Oct. 9

DaiB · 02 Nov 2018

Edge seems a bit buggy in this version. I've had more than one PC where it takes ages to download a page or even close Edge and re-start. Once it's 'settled' or re-started thru Task Manager it behaves normally.

IronZorg89 · 02 Nov 2018

hachiroku said:

For some reason the update downloaded and installed again today...

Maybe you didn't have it installed in the first place. It failed just like mine the first time (according to screenshot below). Only installed successfully the second time. I think KB4464330 was just before MS paused FU 1809. Do You have a screenshot of your update history in its entirety?

Cumulative Update KB4464330 Windows 10 v1809 Build 17763.55 - Oct. 9-kb4464330-successfully-installed-finally.png

hachiroku · 02 Nov 2018

IronZorg89 said:

Maybe you didn't have it installed in the first place. It failed just like mine the first time (according to screenshot below). Only installed successfully the second time. I think KB4464330 was just before MS paused FU 1809. Do You have a screenshot of your update history in its entirety?

Sorry I don't have the whole update history. I cleared the cache because I was getting an error (0x8024a223) sometimes when checking for updates (I have automatic updates disabled via group policy, though Defender Definition updates download automatically anyway, but that doesn't bother me). But I can show you this so you can see I had it already installed for a while now.

IronZorg89 · 02 Nov 2018

hachiroku said:

Sorry I don't have the whole update history. I cleared the cache because I was getting an error (0x8024a223) sometimes when checking for updates (I have automatic updates disabled via group policy, though Defender Definition updates download automatically anyway, but that doesn't bother me). But I can show you this so you can see I had it already installed for a while now.

It is a weird, puzzling but by the same token, very interesting case. Supposedly, if the FU 1809 was paused, so should be the CU (KB4464330) that came right after it. The only thing I can think of, for now, would be that maybe you recently rolled back your system with a system image backup to a date before this CU was installed, meaning before October 21 and now Windows is reinstalling it. Go figure!

hachiroku · 02 Nov 2018

I didn't rollback anything. I have everything disabled, system restore, updates, that kind of stuff. I just deleted the Windows Update cache yesterday, and today it decided to download and install the update again.

Bree · 02 Nov 2018

hachiroku said:

Sorry I don't have the whole update history. I cleared the cache...

Not to worry, even if you have cleared you update history you ~~may~~ edit: will still be able to see both your successful and your failed updates recorded in the Reliability Monitor. Here's one of each I had on 10th October.

Cumulative Update KB4464330 Windows 10 v1809 Build 17763.55 - Oct. 9-image.png

View Reliability History in Windows 10 | Windows 10 Tutorials

Edit: I've just checked that on a test machine.

IronZorg89 · 02 Nov 2018

hachiroku said:

I didn't rollback anything. I have everything disabled, system restore, updates, that kind of stuff. I just deleted the Windows Update cache yesterday, and today it decided to download and install the update again.

I just went to check for the presence of the update (KB4464330) in the Microsoft Update Catalog and it is still there. I would have thought that it would be paused also just as the FU 1809. In a way, that partly explained your case. Maybe, just the fact of cleaning the update cache would trigger the re-install of the update. The only way to be sure would be to reproduce the same thing by cleaning the update cache again and see if the update reinstall itself, but that is completely up to you.

Cumulative Update KB4464330 Windows 10 v1809 Build 17763.55 - Oct. 9-kb4464330-still-available-microsoft-update-catalog.png

hachiroku · 02 Nov 2018

IronZorg89 said:

I just went to check for the presence of the update (KB4464330) in the Microsoft Update Catalog and it is still there. I would have thought that it would be paused also just as the FU 1809. In a way, that partly explained your case. Maybe, just the fact of cleaning the update cache would trigger the re-install of the update. The only way to be sure would be to reproduce the same thing by cleaning the update cache again and see if the update reinstall itself, but that is completely up to you.

Actually is the second time I clear the Update cache since I installed 1809 (I did a clean install). The first time it didn't reinstall the update, but now it did.

However, I DID have it install twice after I clean installed. First time it failed, and the second time it installed fine (some other people in this thread already reported the same behavior).

I guess this version of 10 is still rough around the edges. At this point I don't know if I should format and go back to 1803 or just wait for the next cumulative update to roll out.

Bree · 02 Nov 2018

IronZorg89 said:

I just went to check for the presence of the update (KB4464330) in the Microsoft Update Catalog and it is still there. I would have thought that it would be paused also just as the FU 1809...

No. The updates aren't paused. Those that did upgrade successfully to 1809 will need them. After all, 2.3% of all the Windows 10 computers in the world are now on 1809.

AdDuplex Windows 10 Report for October 2018 now available - Windows 10 Forums

IronZorg89 · 02 Nov 2018

Bree said:

No. The updates aren't paused. Those that did upgrade successfully to 1809 will need them. After all, 2.3% of all the computers in the world are now on 1809.

AdDuplex Windows 10 Report for October 2018 now available - Windows 10 Forums

@Bree again to the rescue as usual. Thanks, mate!. After all, that makes complete sense. I would have thought that the % (2.3) would be much higher than that !