Forum Discussion
Unable to update Windows 10 Insider Preview 17063.1000 (rs_prerelease)
Hello,
Currently, I'm using Windows 10 Insider Preview Build 17025.rs_prerelease.171020-1626
As windows launched update with a new version 17063.1000, I'm unable to update.
Each time system restarts and update runs for a while. Then, it rolls back to previous version of windows.
Error Code is - 0xc1900101.
Please help
Hi,
This code refers to a possible driver issue, please refer to c:\windows\panther\setuperr.log & setupact.log to find out which driver is blocking your upgrade, if possible remove / update the driver / software for the upgrade
(if you get an access denied error on the logfile, just copy the files somewhere before opening them)
Hope this helps
Erik
- Per JohanssonCopper ContributorDisabling virtu worked on my HP Envy ...
- WanTang ChenCopper Contributor
Here is my log message, please help me to explain what's happened and solution ? thanks.
2018-01-06 14:57:30, Error DU DU::CDUSession::Search: Failed to end the asynchronus search. hr = 0x8024401b
2018-01-06 14:57:30, Error SP pDUSearchAndDownload: DU search failed. hr = 0x8024401b
2018-01-06 14:57:30, Error MOUPG DUSetup: Failed to execute DUSetup seach and download [0x8024401b]
2018-01-06 14:57:32, Error CONX Windows::Compat::Appraiser::AppraiserSettings::GetSettingsInternal (268): Failed to retrieve DeviceTicket: [0x800704cf][gle=0x800704cf]
2018-01-06 15:08:03, Error DU DU::CDUSession::Search: Failed to end the asynchronus search. hr = 0x8024401b
2018-01-06 15:08:03, Error SP CDownloadDUUpdates::DoExecuteInternal: Failed to search for updates. hr = 0x8024401b
2018-01-06 15:08:03, Error SP CSetupPlatform::DownloadDynamicUpdates: Failed to download updates. Error: 0x8024401B
2018-01-06 15:08:03, Error MOUPG DUImage: Failed to execute critical search and download [0x8024401b]
2018-01-06 15:08:15, Error DU DU::CDUSession::Search: Failed to set WU internal configuration property for targeted scans. hr = 0x80070057
2018-01-06 15:08:15, Error DU DU::CDUSession::BuildSearchCriteria: Caller profile search criterion is not supported. hr = 0x80070032
2018-01-06 15:08:15, Error DU DU::CDUSession::Search: Failed to build the search criteria. hr = 0x80070032
2018-01-06 15:08:16, Error DU DU::CDUSession::Search: Failed to end the asynchronus search. hr = 0x8024401b
2018-01-06 15:08:16, Error DU DU::CDUSession::Search: Failed to end the asynchronus search. hr = 0x8024401b
2018-01-06 15:08:17, Error DU DU::CDUSession::Search: Failed to end the asynchronus search. hr = 0x8024401b
2018-01-06 15:08:17, Error SP CDownloadDUUpdates::DoExecuteInternal: Failed to search for updates. hr = 0x8024401b
2018-01-06 15:08:17, Error SP CSetupPlatform::DownloadDynamicUpdates: Failed to download updates. Error: 0x8024401B
2018-01-06 15:08:17, Error MOUPG DUImage: Failed to execute driver search and download [0x8024401b]
2018-01-06 15:08:27, Error CONX Windows::Compat::Appraiser::AppraiserSettings::GetSettingsInternal (268): Failed to retrieve DeviceTicket: [0x800704cf][gle=0x800704cf]
2018-01-06 15:08:39, Error CONX Windows::Compat::Appraiser::WicaApplicationInventory::AddItemProperty (492): App Inventory returned duplicate file c:\program files (x86)\intel corporation\intel widi\intel(r) software asset manager\bin\intelsoftwareassetmanagerservice.exe.[gle=0x8007000d]
2018-01-06 15:08:39, Error CONX Windows::Compat::Appraiser::WicaApplicationInventory::AddItemProperty (492): App Inventory returned duplicate file c:\program files (x86)\lenovo\pcmanager\2.6.10.12111\security\service\lavservice.exe.[gle=0x8007000d]
2018-01-06 15:09:01, Error CONX 0xd0000034 Failed to add user mode driver [%SystemRoot%\system32\DRIVERS\UMDF\uicciso.dll]
2018-01-06 15:13:12, Error MOUPG CSetupHost::OnProgressChanged(1916): Result = 0x800704C7
2018-01-06 15:13:12, Error MOUPG CSetupManager::DlpManagerCallback(1763): Result = 0x800704C7
2018-01-06 15:13:16, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::CheckUserCancelled(275): Result = 0x800704D3[gle=0x00000156]- Piero TimpanoCopper Contributor
Mine also does the "hang at firstboot" error with only the windows logo showing.
Errlog shows 2018-01-05 07:06:53, Error [0x0606ae] IBS [SetupCl library] Required profile hive does not exist: [\??\D:\WINDOWS\system32\config\systemprofile\NTUSER.DAT].
or 0xc1900101 in windows. Happens on my Surface Pro 4, and my laptop. Tried both safe boot off, and disabling virtualisation / acpi as reccomended without success on EITHER system.
not a mega genius, but it seems that after the reboot, its trying to start from the wrong partition.... (that would explain the reference above to D as my system, and also the repeated customers saying that they have a disk error / no space error)
- Matt KatzerCopper ContributorI have a similar problem with 1703 OS 15063.786 (1709 update fails). The update is loaded installs, boots a couple of times and rolls back. I'm running Windows defender ATP Win 10/E5 the error in the panther err log is: 2017-11-07 11:00:12, Error [0x0606ae] IBS [SetupCl library] Required profile hive does not exist: [\??\F:\WINDOWS\system32\config\systemprofile\NTUSER.DAT].
- Minh_TaCopper Contributor
I am seeing an issue where I am unable to update as it gives me a BSOD with error System_Service_Exception and the file is wdfilter.sys. The computer reboots and then restores back to original version (v1709 build 16299.192). This computer was recently restored using USB drive and I haven't done anything else besides Windows updates.
- Paul RademakerCopper Contributor
All insiders,
Today is a remarkable day. 20 times a try to install preview 17063. Reassigned sata disks on original sata ports. No matter.
Windows 10 Insider Preview 17063.1000 (rs_prerelease) (3) (used all the windows tools to reset the update history and Dbase.)
Error code: 0xd0000001
Waiting for 17074.....
- Jonathan StrongCopper Contributor
Hi all -
Hoping for some help here... I've been reading through the thread, and many of the posts are all too familiar. I've been been on the insider program with both laptops for a while now -- Dell XPS 15 9530 on Windows 10 Home (4 years old, updating fine - now on 17083), and my primary laptop - an XPS 15 9560 on Windows 10 Pro (a year old, 32GB RAM, 1TB SSD). The 9560 is stuck on 17046 -- that's the last insider prerelease update that worked.
In general, the machine is functioning well, with the only anomaly being that the Intel Management Engine Components Installer will NOT install -- and I've had Dell engineers poking at this on two different one hour calls. They're now suggesting that I wait for a Windows Update that works, or consider a clean install of the production version. I'm hoping to 1) get the insider previews working again on this machine, and 2) getting the Intel installer to work as well.
I must have tried the Insider updates since 17046 about 20 times. I had a LOAD of Windows.Old dirs, most of which are gone now. The error I get, consistently, is: 0xc1900101
I've used the powershell cmdlett to export the windowsupdate log, but can't make heads of tails out of it. I saw a reference in this thread to the "setuperr.log" and "setupact.log" files, which I found under C:\WINDOWS\Panther\NewOs\Panther. I see a number of errors, but can't really tell which are warnings, which are fatal, and which I can actually do anything about. I'm attaching setuperr.log here, in case anyone has the time and expertise, and might be willing to take a look (the other one is too big to upload here).
Thanks in advance!
- Jon
- Paul RademakerCopper Contributor
Jonathan,
I never succeeded in the update 17063, even now Windows 10 Insider Preview 17083.1000 (rs_prerelease) wil not update. On my Asus Transformer book 300 Chi all the updates worked without any flaw. So I am completely not able to say what the problem is. Used every tool there is to correct the problem, no results.
- Deleted
I have the same problem. The latest version I made was 17025,1000. Since then, he has been trying for another five versions, but always unsuccessful. Lastly, it was version 17093. On disk C:\ I already have the seventeenth directory Windows.old (17). Directories can not be removed because the system reports that they do not exist. What should I do?
- Jonathan StrongCopper Contributor
Deleted wrote:
I have the same problem. The latest version I made was 17025,1000. Since then, he has been trying for another five versions, but always unsuccessful. Lastly, it was version 17093. On disk C:\ I already have the seventeenth directory Windows.old (17). Directories can not be removed because the system reports that they do not exist. What should I do?
There are utilities you can use to remove some of those Windows.old directories. But you should keep the one that holds your last working production version of Windows -- you could theoretically fall back to that one if necessary, and apply updates later on when they are working for you, or when the next production release comes out. This might save the you hassle of doing a clean Windows install and reinstalling all your applications.
Be sure you know which directory you want to keep (especially the current Windows directory, as well as your last working production version of Windows). If you DO want to remove those directories, search the web for Iobit Unlocker. It's a free utility that will let you quickly unlock and, optionally, delete directories like this that appear impervious to deletion.
Re: compatibility: I think that part of the reason I finally get 17093 to install on my machine was that I used a 3rd party utility (I used Iobit's Driver Booster -- seems to be best to me, but there are others you can consider as well) to make sure all the drivers were completely up to date. That was one big change I made just prior to attempting the 17093 update. It's also possible that this build was simply more compatible and forgiving of surprises it might run into than prior builds had been -- I really don't know for sure if the driver updates made the difference.
- Joel RiekeCopper Contributor
Hello,
I keep getting failures like exactly like this one for simple HP driver updates. The driver updates fail. It then gets in a loop where it tries to update the drivers over and over again.
I am running Windows Insider 171020-1626.
I doubt this is a space issue because I have 48Gb left on my hard drive.
One thing to consider is that I have compressed my entire C:\ drive to save space (wherever it allows). I wonder if this could contribute to problems although because it is allowed, obviously should be supported and tested for I think.
- Dinos KonCopper Contributor
This is an old post, but what I had to do to overcome this problem was disable all built-in devices (old laptop with webcam, audio, wlan etc) using the bios setup.
After that, the upgrade was successful.
Then I re-enabled the devices one by one to identify the offending one.
I hope this helps someone out there...