Windows 10 Insider Preview Dev Build 21327.1010 (KB5001277) - March 8 Insider

ish4d0w said:

I know that is as annoying as it may be, but this is intentional. They are testing their servicing pipeline, which means they want to know how quickly updates are applied. Which, you know, means how quickly people reboot their machine after it is done.

However, I fully agree with you on that this measurement could actually be done without a reboot. It should be implemented with a simple counter that would track the time between the moment the update is "ready for restart" until the machine is eventually restarted, or even until the user would eventually click a pseudo-reboot button, which - just like the update - wouldn't do anything actual.

But then again, they are not there yet. I would be ready for an upvote though, on feedback hub, if you were to raise this issue, which as a fact, is quite annoying to ask for a reboot for a placebo update.

Thanks for the feeling!
I think I will let this one go because it will be another complaint seating there forever as many that already is.
As you said and well said "But then again, they are not there yet."
And honestly on my part it was more a statement then a complaint.

Hi there
Different boot / updating message to the basic one this time while updating (did via WU not UUPDUMP this time).



Other than that -- seems to be OK so far.

Running as a VM BTW.

After boot - running fine



Still nothing like as slick / fast running as W2K19K server "frigged to run as a desktop" though even on a VM -- but I'd imagine most people here won't get a copy of W2K19K server (especially a VL one so no activation problems ) to play around with !!!!!!!! --If you can get one (or even a trial) it really shows difference between a Commercial server OS and the W10 consumer grade OS editions !!!

IMO that's what M/s should be doing -- get the W10 consumer grade OS'es to perform as near as possible to their server editions --in theory should not be difficult since W10 is essentially a "Single user OS". Who cares about new icons etc - just get rid of all the bloat etc in the consumer editions of W10.

OK there are difficulties -- particularly with drivers etc since consumer grade OS's will have every bit of conceivable hardware around and a whole infinite (or almost) shedload of applications that could be installed on it while corporate Servers are usually pretty standard - but in reality that shouldn't be an excuse for poor or reduced performance.

Cheers
jimbo

I will know for sure if they've fixed the bug when the next new build is installed...my comments, too, have concerned my own 2.5Gb RealTek NIC, exclusively...doesn't seem at all limited to just the Microsoft driver, as that's not been the case for me. All of the drivers in my system--I have about ten installed between Microsoft and RealTek--have exhibited the problems described in my OP. Glad Microsoft is on the case--but it's never been about the Microsoft driver in particular--that would have been easy to solve as I've been getting my drivers from RealTek for many months now--so I have the Microsoft drivers & the RealTek drivers installed--and they've all had the dropout/lost Gateway problem for the last few months--so far the only cure has been a manual install--1.0.0.4 driver works fine if manually installed through the DM, etc.

We'll see if this one stays up after the next build install!

waltc said:

Open up the DM and look at the network adapter--if you don't have the problem then none of this applies! However, I did notice that you are using a wireless adaptor, and that we have different NICs, whereas I am using a new 2.5GB Reatek NIC and am strictly wired. I don't do wireless or BT.

EDIT: Since I see that we're all doing "I'll show you mine if you show me yours"...Here's what mine looks like...:)

Attachment 321857

And here's mine . . .

New build 21332.1000 in the Dev Channel.

UPDATE: Windows 10 Insider Preview Dev Build 21332 (RS_PRERELEASE) - March 9