See Announcing Windows 10 Insider Preview Build 20201 for features, fixes, and known issues.
--Joe
![]() |
Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don't do it. |
SIGN IN | Not a member? | REGISTER | PLUS MEMBERSHIP |
Home » Forums » AskWoody support » Windows » Windows 10 » Windows 10 beta builds » Windows 10 Insider Preview build 20201 released to DEV Channel
See Announcing Windows 10 Insider Preview Build 20201 for features, fixes, and known issues.
--Joe
One more crash.
There is no REAL support for Insider problems (or ANY Windows problems, for that matter). I have made multiple reports on the Insider Feedback Hub (Ha! that’s a joke).
I have not been able to update the Dev Channel Insider Preview since Build 20161. I have tried EVERY Build since then (with the exception of 20170 when my machine was down for a fan replacement) including this one. I have been able to successfully install Beta Channel build 19042.450, but all of the Dev Channel Builds go through download/install, reboot, Configure to 100%, and lock up on the second reboot on a black screen with blue logo. (BTW Fast Boot is turned off, Safe Boot doesn’t apply))
Here are some of the things I have tried:
+ Removing (uninstalling) all antivirus/antimalware programs.
+ Removing any USB connected devices
+ Installing through Windows Update from 20161.
+ Installing from an ISO (20175 and 20201) on the machine saving progs and data, saving only data, saving nothing.
+ Installing from bootable media (DVD) saving progs and data, saving only data, saving nothing.
+ Installing Beta Channel 19042.450 (successful), moving to Dev Channel and trying to upgrade to 20201 through WU and from an ISO.
It is my opinion that MS has changed something in Windows that is causing the problem and my guess that it was in Build 20170 (which I missed). The installation now puts the new system files in place and configures the system, but the machine cannot boot successfully on the new setup. Perhaps it has stopped supporting some of the hardware or how it works, as it seems that the error report 0xC19000101 – 0x20017 would suggest. And it seems the only solution is to wait and see if MS fixes the problem they have created or simply eliminates the machines with my configuration from running Windows (which wouldn’t surprise me).
Count me an OUTsider.
Further information on Dev Channel Builds:
I have been reporting my difficulties on the Insider Feedback Hub. There are MANY with the same problem. If I had to guess, the problem may be with the Intel HD 4000 graphics. Graphics h/w seems to be the most frequent spoiler.
In the meantime, I will either try to run the Beta Channel Builds or get out of the Insider Program altogether. It’s a shame, b/c I have been doing it since Oct 2014.
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
Welcome to our unique respite from the madness.
It's easy to post questions about Windows 11, Windows 10, Win8.1, Win7, Surface, Office, or browse through our Forums. Post anonymously or register for greater privileges. Keep it civil, please: Decorous Lounge rules strictly enforced. Questions? Contact Customer Support.
Want to Advertise in the free newsletter? How about a gift subscription in honor of a birthday? Send an email to sb@askwoody.com to ask how.
Mastodon profile for DefConPatch
Mastodon profile for AskWoody
Home • About • FAQ • Posts & Privacy • Forums • My Account
Register • Free Newsletter • Plus Membership • Gift Certificates • MS-DEFCON Alerts
Copyright ©2004-2025 by AskWoody Tech LLC. All Rights Reserved.
Notifications