KB4592438 CU Windows 10 v2004 build 19041.685 and v20H2 19042.685 Win Update

sgage said:

Why was 661 made available if it was incomplete? Let's don't blame the victims here...

Here, here. Was just going to say it myself.

People are going back to 630 then to 685. That is not necessary as using MCT you can go from 661 to 685. How do I know? Just did it and kept all files as well.

Geneo said:

Why did you install a non-official update ? If you are going to do that, you should be sure to have some means to back out.

It was NOT an unofficial update. Get your facts right before sounding off.

It was offered by WU a few days ago.

Geneo said:

Why did you install a non-official update ? If you are going to do that, you should be sure to have some means to back out.

It was not at all clear that it was a non-official update until after the fact. Happily, I had a freshly made image to restore, for just that reason, as I always do. It was nothing to me. But the next time TenForums posts an announcement of an update with download links and all, looking for all the world like any other announcement of a MS release, I hope they put IN ALL CAPS in the subject line something like THIS IS NOT AN OFFICIAL UPDATE!!!

My facts are straight. I didn't know about that update till it appeared in my three computer's Update screen. Two worked but one didn't.

Geneo said:

What makes you think it was official? Was it offered through windows update? I couldn't even find it in the update catalog? .661 was never offered through Windows Update. You get your facts straight.

linw said:

My facts are straight. I didn't know about that update till it appeared in my three computer's Update screen. Two worked but one didn't.

.661 was official, in the sense that it was delivered through Windows Update - but only to those on Insider preview builds. As such it was, by definition, 'for testing only' and should have been expected to contain bugs. Anyone who downloaded the .cab file and installed it on a non-Insider machine was doing so unofficially, and should have been prepared for the risks.

With all of this talk about problems with .661, a person like me with build .630 should be fine with this update?