New
#30
As far as I am concerned MS can make it happen in the background, just as @kado897 suggested in post # 29.
Windows 10 Insider Preview Dev Build 21387.1 (co_release) - May 21 Insider
-
-
New #31
Personally, I think this was a needed and welcome fix, and good news. It was a PITA. I cleaned that up quite a bit.
We fixed an issue where some devices were re-offered the .NET update after it is installed. After taking this build you should no longer be reoffered the .NET update. If you experience and issue getting Build 21387 because of a pending .NET update, you can work around the issue by pausing then un-pausing updates.
-
New #32
Which I swear is what must have been happening for the first several years of Insider (either incorporated or tacked onto the install such that it was transparent to the user). Then in the last year or so they stopped.
-
New #33
Done! I didn't check the time but it didn't take very long at all. No hiccups.
And now I have to head for the store . . . good thing it's only a couple miles away.
I'll leave the 'puter on and play with it when I get back.
-
-
-
New #36
downloading
-
New #37
Gaming performance still not fixed since April Update and PC will not fully idle (I will reset Power Plans later), had this before though they fixed it with another build.
Damn folders still horrid closed view, that is what you get with Millennials and Gen Z working/in charge at MS these days, oh and lots of new emojis!
-
New #38
44 minutes on PC
-
-
New #39
Going for third build in a row that refuses to install...laying odds it will fail, too--because of the way the following is worded:
"We fixed an issue causing some devices to fail with error code 0xc1900101. While this fix will resolve the problem on some devices, there is a second issue causing the same error code (noted below). We’re working on a fix for this issue as well."
...Ah, if only Microsoft could figure out why neither issue occurs in 21370 or earlier...but maybe it's just taking them some time to think about that.
There are apparently multiple issues in these builds (post 21370) that cause them not to install--to fail the installation process, dramatically. Microsoft says here it has fixed one issue--but alas, not the other one. And so this build, too, may fail because although one serious issue has been fixed, alas, the other (unidentified) serious issue (with the same error code) has not been fixed. Perhaps Microsoft simply did not think about fixing both bugs first and then flighting the next build...but maybe they will in a couple of weeks...
So...I expect this build will fail to install, too, since we have the case of two separate fatal bugs bearing the same error code which cause the install to fail--one of those bugs fixed, the other not.
Flip....and the coin is in the air, spinning and falling....will let you know how it turns out...
__________________________________________
And...as much as I really hate to have called this one...it's yet another boot-to-perpetual-unresponsive-black-screen with the 21387 desktop a no show--yet again...!
Will the fourth consecutive build since 21370 finally put things right--uh, whenever Microsoft flights it? Tune in soon for the next exciting chapter of, The Windows Insider Builds That Won't Install!
Meanwhile...build 21370--the build that just works--continues to hold down the fort.Last edited by waltc; 21 May 2021 at 20:36.
Quote
Related Discussions
