New Windows 10 Insider Preview Fast+Slow Build 18362 (19H1) - Mar. 22 Insider

jimbo45 said:

Hi there
@Brink
I think your build is still missing an update or two. I just used WU from within this build that I´d downloaded via UUPDUMP

My latest from this build is :
Attachment 229490


Cheers
jimbo

Hey Jimbo,

This was just for the lastest update for the Slow ring release notes below.

UPDATE 4/2: We have released Build 18356.21 (KB4496796) to Windows Insiders in the Slow ring who are currently on Build 18356.16. This update will get Insiders who are on Build 18356.16 back into a good state so they can update to Build 18362. We are allowing a few days for this update to roll out before offering Build 18362 – so that means Insiders will still not see Build 18362 offered after updating to Build 18356.21. But stay tuned!

Tip

Allow or Deny Apps Access to Use Voice Activation in Windows 10 | Tutorials

jimbo45 said:

Hi there...

You can even use UUPDUMP for "Standard" Windows builds plus the "Features update" one as well. I've found it works every time with whatever build you want to install.

I know Ms wants to test the standard WU process but IMO since this method is so reliable why doesn't Ms recommend using this process to install new builds and just keep WU for updating fixes and security upgrades.
Cheers
jimbo

From the "Since we appear to have some time before the next build," dept...

Well, it's kind of strange, judging by some responses in the forums here, but I guess for at least the last forty or so Insider build installs (I've turned the reverb up on that a notch or two, to let that "sink in" for a moment--"forty or so builds, forty or so builds, forty builds"...)--it's kind of strange that in all that time--years, now, as the calendar flies--the WU mechanism has performed as designed by Microsoft with hardly a hiccup in protest... For me It's been consistently reliable, so much so much that I no longer even think about it anymore and "whether I'm going to use it" is not even a question at this stage of the game. I always begin a new build install through WU and as I am never required to change horses in midstream the build install finalizes where it began, in Windows Update. It has literally been calendar *years* of time since I was forced to install an Insider build through a method other than that which was designed and purposed by Microsoft--Windows Update--because of being forced to do so by some failure of the Windows Update mechanism. Again, I have seen no such failure in that mechanism in years. So...it's been years since I have had a need for UUPDump, etc.

My experience has been simply that Windows Update also "works every time" for whatever build I wish to install, and so, in that regard alone, there is nothing that indicates a superior end result gained when going the UUUPDump route. However, I note that in a comparison between the two methods, Windows Update is both faster and simpler to use, while delivering a qualitative result certainly not *worse* than that which is the best obtainable via the UUPDump method (We'll crack this nut a little more precisely in a moment...)

So...in trying to sincerely answer your question as to "Why does Microsoft use Windows Update for installing builds, instead of a possible alternative--in this case UUPDump?", I've come up with what I think are the only answers possible--you may wish to consider them, or you may not, as the case may be.... I would hope that you might consider them as they certainly seem to be conclusions of note worth heeding, imo, for those not already aware of them.

*The idea that Microsoft simply wants to use Windows Update to "test" how well the update delivery mechanism works, while having no intention to actually use Windows Update as the primary Windows 10 delivery system globally, strikes me as an obviously an invalid assumption. (Lots of obvious stuff going on here, imo.) Of course, Microsoft wants to "test" Windows Update with the Windows 10 Insider build installs, naturally--but Microsoft is doing that testing because Microsoft intends to use Windows Update to deliver those builds, globally. That basic, clearly announced intent has not changed since 10/1/2014, to my knowledge, when the Insider program began, .

*Second, since this is Microsoft's obvious intent--that is, Windows Update is the intended delivery system, and Microsoft has made no announcement or suggestion to the effect that it is even considering changing to a different delivery system, or in some way moving to incorporate the UUPDump methodology at a future date, I think it's necessary to examine why there are some people whose experience with the Windows Update system has been so poor and so negative that it would lead them to consider or desire to use an alternative method for build installation, such as UUUPDump, etc.

*Here we arrive at the crux of this truly exciting, enthralling matter! (Similar to the ultimate thrill of watching paint peel!) : There doesn't seem to be any underlying software problem with the Windows Update mechanism that would cause the problems some people experience--for if there was such a fundamental flaw or flaws, then there would be absolutely no way to explain the flawless service I've experienced over the last few years with the very same Windows Update mechanism. And of course, it isn't just me--there are likely millions of people who also have little if any problems with Windows Update and who, also like me, continue to use it without incident--some of those people pop up in the forums here to attest to their non-issues with Windows Update, as well, from time to time! The largest signaler of positives with Windows Updates is, of course, Microsoft itself--as the company reaches hundreds of millions of people globally every day through various avenues--a significant portion of those interactions coming by way of Windows Update.

Sheer, elementary logic dictates that the causes of severe problems with Windows Update which cannot be traced to similar problems, known and experienced by other people using the same software under standard operating procedure and conditions, are very likely to be caused by local problems in the user's hardware and network environment as opposed to problems with the Windows Update software. The distinction is an important one, critically so, for if one cannot isolate the origins of a problem one cannot hope to solve it. The assumption--the faulty assumption--is that Microsoft controls every aspect of the user's Windows' experience, including the hardware and drivers the user has installed and is currently using, including the firmware relative to the hardware employed, and that Microsoft controls the very physical network the user's machine resides on and of course the software the user has elected (or not elected!) to install, etc, ad infinitum! Microsoft does not control these things--they are controlled by the user himself and by the administrators of the network by which the user accesses the Internet, and by extension, of course, is able to connect to Windows Update. If problems occur that render Windows Update unusable so that an Insider's build cannot be installed so that an alternative method such as UUUDump *must* be employed to install the build, then the problem must of necessity lie at the end of the hardware and software spectrum completely uncontrolled by Microsoft or the Windows Update mechanism itself. Windows Update is prevented in its task by X factors in the user's local environments.

MUser said:

Anyone else also just get NVIDIA Geforce driver v430.00 installed via Windows Update?

Just been reading about that NVIDIA driver but can't find it on the NVIDIA servers. A feature of it is WDDM 2.6 support.