Cumulative Update KB4526447 Windows 10 v1903 build 19002.1002 Oct. 18 Insider

EdTittel said:

I did manage to get both test machines upgraded to 19002.1. So far, WU is not offering the 19002.1002 CU. Will this come with time, or is it only offered to those who didn't succeed with the original 19002.1? I'm not sure I completely understand what's going on here. Thanks,
--Ed--

It seems that .1002 is a small cumulative update for .1 to correct the stalled shutdown issue.
I would think it would be immediately available to you in the Fast Ring from Windows Update.

They released a similar update to the Release Preview ring. Seems it had this problem as well.

If your not having shutdown issues, like was not, then I wouldn't even worry about rushing to get it.

peace
wanna

I'm getting Defender updates so WU is working. But no proffer of 19002.1002 yet. Just check the Microsoft Update Catalog for KB4526447, and here's what I see:



I am coming to the opinion that I won't be offered the follow-up CU. If that changes, I'll be sure to amend this post accordingly.
--Ed--

I updated to 19002.1002 in less than 15 minutes and the shutdown issue seems to be fixed. I still get the Windows Update "View optional updates" prompt which tries and fails to install Canon MX922 Printer and Fax drivers. I wonder why they did not include the Shut Down fix in 19002.1


WEK

EdTittel said:

I'm getting Defender updates so WU is working. But no proffer of 19002.1002 yet. Just check the Microsoft Update Catalog for KB4526447, and here's what I see:



I am coming to the opinion that I won't be offered the follow-up CU. If that changes, I'll be sure to amend this post accordingly.
--Ed--

Hello Ed,

It won't be available in MUC since it's an Insider update.

Brink said:

Hello Ed,

It won't be available in MUC since it's an Insider update.

Hmmmm, if he got an update to 19002.1001, shouldn't @EdTittel be an Insider?

I wasn't paying attention to Little Lenovo, but when I turned it on, it almost immediately offered me 19002, then the next morning, it had 19002.1002 downloaded and wanted me to Restart.

Grrrrrrrrrr, they didn't fix everything ... I turned my back on it and when I turned around 10 or 15 minutes later it was still "shutting down". Had to do a hard shutdown, then when I rebooted and shut down again, things seem to be OK. This is not something a novice Windows person would understand.

Wynona said:

Hmmmm, if he got an update to 19002.1001, shouldn't @EdTittel be an Insider?

I wasn't paying attention to Little Lenovo, but when I turned it on, it almost immediately offered me 19002, then the next morning, it had 19002.1002 downloaded and wanted me to Restart.

Grrrrrrrrrr, they didn't fix everything ... I turned my back on it and when I turned around 10 or 15 minutes later it was still "shutting down". Had to do a hard shutdown, then when I rebooted and shut down again, things seem to be OK. This is not something a novice Windows person would understand.

Hey Wynona,

Sorry, it was just to let Ed know that he wouldn't find a MSU file download available in MUC since KB4526447 is an Insider build.

Brink said:

Hey Wynona,

Sorry, it was just to let Ed know that he wouldn't find a MSU file download available in MUC since KB4526447 is an Insider build.

I'm totally confused, Shawn. Are you saying Ed isn't an Insider on Build 19002? I know what WU and CU are, but what are MSU and MUC?

Wynona said:

I'm totally confused, Shawn. Are you saying Ed isn't an Insider on Build 19002? I know what WU and CU are, but what are MSU and MUC?

Sorry for the confusion.

It's not saying Ed is an Insider or not.

MUC is short for the Microsoft Update Catalog where you can manually download updates online from Microsoft instead of Windows Update if wanted. You can look up an update by it's KB number in MUC to download.

MSU is the file type typically used for updates that you can download from MUC. You can just double click on the download MSU file to install it.

I was just saying the Insider update in the first post wouldn't be available to download from MUC.

@Brink: Doh! Of course...
--Ed--