Windows 10: Cannot Update from Preview 17074; Crashes then reverts, 0xC1900101

So I've been stuck for a few days now on the dreaded wdfilter.sys infinite green screen of death loop. Finally broke out of it while reading some of the other threads but in the process some weird stuff happened (some drivers/settings changed/were changed such as at one point all services were turned off). I haven't been able to update successfully since build 17074. Now the only thing that kind of works is running the OS without windows defender but I don't want to do that for too long. How do I fix this update process? It always gets to the first boot up screen, crashes (the most recent one was PAGE_FAULT_IN_NONPAGED_AREA)

ASHDESKTOP (2018-04-05 20 50).zip

:)

 

Microphone doesn't work

I just updated from stable version to insider preview 17074, that's all

 

Windows 10 Insider Builds

The current Insider Preview Build is 17074.

My machine runs on Build 17025.rs_prerelease.171020-1626, with all released updates applied.

My question is:

Is my OS identical or equivalent to the Preview Build 17074?

Thankyou,

Fred

 

Yep, 0x800700C1 = SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

The special pool is only present when you have driver verifier turned on.

 

Have you tried directly downloading the ISO from Microsoft and installing that way?

Download Windows 10 ISO File

 

Yeah this actually was the iso file that I tried to install from. Have tried a few different builds that all fail. First goes to page fault then on reverting goes to driver io verification error or something.

 

Do you attempt the installation as a clean install and reformat the hard drive?

 

I'm trying to avoid a clean install if possible as this is the shotgun approach that I thought was mainly warranted about 20 years ago. "If it's broke just wipe and reinstall! " I don't want to have to reinstall everything and change all the settings back, especially if it's not guaranteed to work (as I've read in other threads the error could come back in the new install as well and wouldn't want to risk losing the rollback).

I did post the zip file from the beta logger program; if I were to try to continue manually debugging this; how do I figure out what driver/install process caused the failure?

Also things I have tried (not all inclusive list):
Chkdsk
DISM cleanup-image restorehealth
sfc scannow
Windows Update troubleshooting

 

To maximise your chance of a successful install I would remove every device on your PC apart from a simple wired mouse and keyboard and a monitor. Remove any disks other than the system disk. See if it helps. You can then add the removed items back afterwards.

 

Is there a way to go through the update log to see what caused the failure? Additionally is there some way to manually download insider preview updates? I know there's a way for normal windows to download packaged updates.

 

You will need to find the panther logs and see if you can determine which driver is blocking the update. These logs are not collected by the log collector we provide for BSOD analysis so you will need to search for them yourself:
c:\windows\panther\setuperr.log & setupact.log


If its any help here is the sequence of errors in the system log that we do collect:

Code: 2018-04-05T19:47:10.348 Installation Failure: Windows failed to install the following update with error 0x80073D0A: 9WZDNCRD29V9-Microsoft.MicrosoftOfficeHub. 2018-04-05T19:47:24.254 Installation Failure: Windows failed to install the following update with error 0x80073D0A: 9WZDNCRFJ3Q2-Microsoft.BingWeather. 2018-04-05T19:47:31.159 Installation Failure: Windows failed to install the following update with error 0x80073D0A: 9NBLGGH10PG8-Microsoft.People. 2018-04-05T19:47:54.585 Installation Failure: Windows failed to install the following update with error 0x80073D0A: 9WZDNCRFJBBG-Microsoft.WindowsCamera. 2018-04-05T19:49:03.254 Installation Failure: Windows failed to install the following update with error 0x80073D0A: 9NBLGGH4R32N-Microsoft.WindowsFeedbackHub. 2018-04-05T19:51:28.439 Installation Failure: Windows failed to install the following update with error 0x80073D0A: 9WZDNCRFJ364-Microsoft.SkypeApp. 2018-04-05T19:54:31.777 Installation Failure: Windows failed to install the following update with error 0x80073D0A: 9WZDNCRFHVJL-Microsoft.Office.OneNote. 2018-04-05T19:57:03.147 Installation Failure: Windows failed to install the following update with error 0x80073D0A: 9WZDNCRFHVQM-microsoft.windowscommunicationsapps. 2018-04-05T19:59:53.182 Installation Failure: Windows failed to install the following update with error 0x80073D0A: 9WZDNCRFJBH4-Microsoft.Windows.Photos. 2018-04-05T20:41:36.158 Crash dump initialization failed! 2018-04-05T20:41:36.305 The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. 2018-04-05T20:41:54.979 Installation Failure: Windows failed to install the following update with error 0xC1900101: Windows 10 Insider Preview 17133.1 (rs4_release).[/quote]

 

The errors in that log are the windows store apps failing to install (maybe because my windows is too outdated? idk).
I have attached the panther folder; weirdly setuperr.log is 0bytes.

 

Microsoft has released SetupDiag that helps analyze upgrade logs. It wouldn't hurt to give that a try.

The typical locations for Windows 10 upgrade logs are:
Code: C:\$Windows.~BT\Sources\Panther\setupact.log C:\$Windows.~BT\Sources\Panther\setuperr.log C:\$Windows.~BT\Sources\Rollback\setupact.log C:\$Windows.~BT\Sources\Rollback\setuperr.log[/quote] But to be honest, serious problems with Insider fast ring builds are to be expected, and it is not always a guarantee that you can upgrade to the next flight, given the beta (and often alpha) quality of the releases. If you are not comfortable wiping your installation, insider builds are probably not what you want to run as a daily driver.

 

So I got:
Code: Matching Profile found: FindSetupHostReportedFailure - 6253C04F-2E4E-4F7A-B88E-95A69702F7ECError: SetupDiag reports down-level failure, Operation: Finalize, Error: 0x800700C1 - 0x5001[/quote] Edit: Actually this was only the most recent upgrade attempt. It didn't mention the previous ones which did go a bit further

Edit: I fixed it! Turns out that somewhere along the line verifier was re-enabled which was likely causing the verification errors doh! But now it works for now. Ty all for the help! Y'all are the best!