Windows 10 Insider Preview Dev Build 21286.1 (RS_PRERELEASE) - Jan. 6 Insider

Fabler2 said:

For those that dual boot 'timeout' boot setting was set to zero again.

@f14tomcat my terminology might have messed it up and perhaps I should have called it an 'app' that opens rather than a pane.

I'm used to it setting to 0, I've trained my eyes to check that prior to switching OS. Sadistic little bug.

emilcioran99 said:

Me too.

I assume you've rebooted and still no option. Right click the taskbar and look for it near the top.

f14tomcat said:

I assume you've rebooted and still no option. Right click the taskbar and look for it near the top.

I'ts not there on mine A/B testing again.

kado897 said:

I'ts not there on mine A/B testing again.

Really? I'm sure this has been mentioned a zillion times, but the A/B testing in a testing environment with an OS that is supposed to be tested is absurd.

Mini-rant over.




but they put out an ISO for it. that makes sense.

f14tomcat said:

Really? I'm sure this has been mentioned a zillion times, but the A/B testing in a testing environment with an OS that is supposed to be tested is absurd.

Mini-rant over.

Quite so.

f14tomcat said:

I assume you've rebooted and still no option. Right click the taskbar and look for it near the top.

After a reboot, still not there.

magilla said:

After a reboot, still not there.

You're with Keith, A/B negative blood type.

Missed out last Flight....Update did not give choice "Pick insider settings".

f14tomcat said:

You're with Keith, A/B negative blood type.

I never get the A.

rseiler said:

Did you also have that one back some months ago when it was a problem for some people for months on end? Or were you exempt back then?
https://aka.ms/AAabcmd

Back then, it was people with certain NICs, always older ones, especially Intel.

IIRC, I haven't had this problem in over a year! Bizarre. I've reported it every time--they've apparently not even looked into it, yet. Ah, well, 20270 is a sweet build. I really thought this kind of nonsense was long over and done. Other people in the hub are reporting the same problems. Seems like Microsoft is dedicated to reinventing the wheel repeatedly.

Right now, I'm using the RealTek 2.5GB Controller--but I'm using it with 20270 and all the builds this year with no problem. Maybe I'll try to switch to the Intel Ethernet controller, just to see. When I get the inclination. I've wasted enough time trying to fix this, though.