New
#250
I can see a pattern: When a new build is released, if I boot an Insider machine and first update Defender definitions using Defender GUI, and only thereafter check Windows Update which then finds the new build, the download / preparing / initializing phase of the upgrade does not fail.
However, if I let WU to check the updates / upgrades and it finds both Defender definition update and a new build, most often (I estimate two times out of tree) the download, preparing or initialising phase fails (in my case, that is; I am not stating a fact, just what I have experienced).
I get no failed downloads when doing this first, and only when done letting WU to check available updates / build upgrade:
![]()