Please help me troubleshoot a Win 10 Update failure

Factual Questions
1

My parents’ laptop doesn’t automatically update anymore, since the functional update to version 20H2 in May. I started to update via the Microsoft Update Assistant, but to no avail, it always threw the error 0xc1900101. I’ve done the following since then:

Uninstall Avast antivirus (a pain in the ass anyway). No difference.

Try a system repair with SFC and DISM. No faults indicated, and no difference.

Update every single driver in device manager. Some weren’t up-to-date, like the graphics drivers, the audio drivers, the network card drivers and some system drivers, but updating Windows after having updated the drivers still threw the same error.

Disable every program in auto start. Still, the error persists.

I dug a little deeper and found out about the log file setuperr. It says:

2021-09-20 02:08:52, Error                 MOUPG  CInstallUI::GetDefaultLanguage(2027): Result = 0x80070002[gle=0x00000002]
2021-09-20 02:45:28, Error                 MOUPG  CSetupManager::GetDUSetupResults(6511): Result = 0x80070490
2021-09-20 02:45:31, Error                 MOUPG  CDlpTask::Cancel(982): Result = 0xC1800104
2021-09-20 02:45:31, Error                 MOUPG  CDlpTask::Cancel(982): Result = 0xC1800104
2021-09-20 02:45:31, Error                 MOUPG  CDlpTask::Cancel(982): Result = 0xC1800104
2021-09-20 02:45:31, Error                 MOUPG  CDlpTask::Cancel(982): Result = 0xC1800104

The Microsoft diagnose tool SetupDiag tells me this:

SetupDiag was unable to match to any known failure signatures.
SetupDiag version: 1.6.2107.27002
System Information:
	Machine Name = LAPTOP-OKDRFP2E
	Manufacturer = HP
	Model = HP 255 G6 Notebook PC
	HostOSArchitecture = 1031
	FirmwareType = UEFI
	BiosReleaseDate = 20171101000000.000000+000
	BiosVendor = F.20
	BiosVersion = F.20
	HostOSVersion = 10.0.18363
	HostOSBuildString = 18362.1.amd64fre.19h1_release.190318-1202
	TargetOSBuildString = 10.0.19041.900 (vb_release_svc_prod3.210311-1736)
	HostOSLanguageId = 
	HostOSEdition = Professional
	RegisteredAV = Windows Defender
	FilterDrivers = 
	UpgradeStartTime = 20.09.2021 20:19:31
	UpgradeEndTime = 20.09.2021 20:20:41
	UpgradeElapsedTime = 00:01:10
	CV = 2ic9Xojj6kGiC0I5
	ReportId = 


Matching Profile found: FindRollbackFailure - 3A43C9B5-05B3-4F7C-A955-88F991BB5A48
SetupDiag version: 1.6.2107.27002
System Information:
	Machine Name = LAPTOP-OKDRFP2E
	Manufacturer = HP
	Model = HP 255 G6 Notebook PC
	HostOSArchitecture = 1031
	FirmwareType = UEFI
	BiosReleaseDate = 20171101000000.000000+000
	BiosVendor = F.20
	BiosVersion = F.20
	HostOSVersion = 10.0.18363
	HostOSBuildString = 18362.1.amd64fre.19h1_release.190318-1202
	TargetOSBuildString = 10.0.19041.900 (vb_release_svc_prod3.210311-1736)
	HostOSLanguageId = 
	HostOSEdition = Professional
	RegisteredAV = Windows Defender
	FilterDrivers = FileInfo
	UpgradeStartTime = 20.09.2021 20:19:31
	UpgradeEndTime = 20.09.2021 21:50:37
	UpgradeElapsedTime = 01:31:06
	CV = 2ic9Xojj6kGiC0I5
	ReportId = faac84ce-4a57-4751-bf1b-353096bfbdc1


Error: SetupDiag reports rollback failure found.
Last Phase = Finalize
Last Operation = Remove System Restore checkpoints
Error = 0xC1900101-0x20017
LogEntry: 

Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.

Last Setup Phase:
Phase Name: Finalize
	Phase Started: 20.09.2021 21:50:02
	Phase Ended: 20.09.2021 21:50:19
	Phase Time Delta: 00:00:17
	Completed Successfully? True


Last Setup Operation:
Operation Name: Remove System Restore checkpoints
	Operation Started: 20.09.2021 21:50:17
	Operation Ended: 20.09.2021 21:50:19
	Operation Time Delta: 0:00:00:02.0000000
	Completed Successfully? True

This site tells me that the error 0xC1900101 - 0x20017 means:

Well, ok, seems like a driver misbehaving, a hunch I had all the time. But how do I get to know which module/device is the culprit with this information? Can someone interpret it better for me, or point out how to troubleshoot further? Help would be much appreciated, it’s a pain in the ass. I’ve already spent hours on this problem.

2

Okay. Your mosetup error code is 0xC1900101 so you will want to do a plaintext search of setuperr.log for the string “C1900101”. The snip you provided does not contain the error code but it should be in that file somewhere. Hopefully some lines just before the last occurrence will help you identify which specific driver is causing the problem.

~Max

3

It’s not a snip. it’s the whole setuperr.log file I posted. I looked further in the setupact.log for what happened before the error occured, but by that I also cannot identify a special driver (this is a snippet from the file):

2021-09-20 02:45:29, Warning               MOUPG  Finalize: Compat instance not found.
2021-09-20 02:45:29, Info                  MOUPG  Finalize: Requesting ASIMOV upload.
2021-09-20 02:45:29, Info                  MOUPG  Finalize: Reporting result value: [0x0]
2021-09-20 02:45:29, Info                  MOUPG  CSetupDiagnostics: Tracing Data [DWORD] -> [Setup360MappedResult]=[0x0] [b3efb894-e8ea-4e14-adbf-34fbdef1a905][][][0x7]
2021-09-20 02:45:29, Info                  MOUPG  CSetupDiagnostics: Tracing Data [DWORD] -> [Setup360Result]=[0x0] [b3efb894-e8ea-4e14-adbf-34fbdef1a905][][][0x7]
2021-09-20 02:45:29, Info                  MOUPG  CSetupDiagnostics: Tracing Data [DWORD] -> [Setup360Extended]=[0xB0003] [b3efb894-e8ea-4e14-adbf-34fbdef1a905][][][0x7]
2021-09-20 02:45:29, Info                  MOUPG  CSetupDiagnostics: Tracing Data [CUSTOM] -> [WindowsUpdateExit] -> [Web360][b3efb894-e8ea-4e14-adbf-34fbdef1a905][][][0x7]
2021-09-20 02:45:29, Info                  MOUPG  CSetupDiagnostics: Tracing Data [CUSTOM] -> [UnexpectedEvent] -> [Web360][b3efb894-e8ea-4e14-adbf-34fbdef1a905][][25aa1637-1c57-42e3-8614-49f8989aebd8][][Succeeded][Windows 10 Pro][18363][7][8][0x0][0xB0003][19041]
2021-09-20 02:45:29, Info                  MOUPG  CSetupDiagnostics: TraceOneSettingsEvent -> [0x0][0][os=windows;scenarioId=7;platformEdition=Professional;platformInstallationType=Client;sku=48;AppVer=10.0.19041.572;appBuildLab=vb_release_svc_prod1][][Web360][b3efb894-e8ea-4e14-adbf-34fbdef1a905][][][0x7]
2021-09-20 02:45:29, Info                  MOUPG  Finalize: Retrieving downlevel ticks from registry...
2021-09-20 02:45:29, Info                  MOUPG  Finalize: Converting [513] downlevel ticks to seconds...
2021-09-20 02:45:29, Info                  MOUPG  Finalize: Reporting total downlevel time: [2565 seconds]
2021-09-20 02:45:29, Info                  MOUPG  CSetupDiagnostics: Tracing Data [DWORD] -> [Setup360DownlevelTime]=[0xA05] [b3efb894-e8ea-4e14-adbf-34fbdef1a905][][][0x7]
2021-09-20 02:45:29, Info                  MOUPG  MoSetupPlatform: Release Identifier -> [FinalizeExit]
2021-09-20 02:45:29, Info                  MOUPG  MoSetupPlatform: SuspendAndReleasing Setup Platform object...
2021-09-20 02:45:30, Info                  MOUPG  MoSetupPlatform: Setup Platform object suspended!
2021-09-20 02:45:30, Info                  MOUPG  MoSetupPlatform: Setup Platform object released!
2021-09-20 02:45:30, Info                  MOUPG  Finalize: Leaving Execute Method
2021-09-20 02:45:30, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2004]
2021-09-20 02:45:30, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2003]
2021-09-20 02:45:30, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2001]
2021-09-20 02:45:30, Info                  MOUPG  ProgressHandlerAction: Sending final progress message for action [0].
2021-09-20 02:45:30, Info                  MOUPG  ProgressHandlerAction FinalUpdate: 0x0, 0x0 / 0x0, 0x0
2021-09-20 02:45:30, Info                  MOUPG  ProgressHandlerAction: Sending final progress message for action [0].
2021-09-20 02:45:30, Info                  MOUPG  ProgressHandlerAction FinalUpdate: 0x0, 0x0 / 0x0, 0x0
2021-09-20 02:45:30, Info                  MOUPG  Signalling actions thread to shut down.
2021-09-20 02:45:30, Info                  MOUPG  Waiting for actions thread to exit.
2021-09-20 02:45:30, Info                  MOUPG  Actions thread has exited.
2021-09-20 02:45:30, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2004]
2021-09-20 02:45:30, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2000]
2021-09-20 02:45:30, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x3000]
2021-09-20 02:45:30, Info                  MOUPG  DlpTask: Leaving Execute Method
2021-09-20 02:45:30, Info                  MOUPG  SetupManager: Launching setup.
2021-09-20 02:45:30, Info                  MOUPG  SetupMgr: Deleting environment variable SP_UPLOAD_ASIMOV.
2021-09-20 02:45:30, Info                  MOUPG  SetupManager: Requesting cleanup level [0x1] from parent process.
2021-09-20 02:45:30, Info                  MOUPG  SetupManager: Resetting WinDlp state for full cleanup...
2021-09-20 02:45:31, Error                 MOUPG  CDlpTask::Cancel(982): Result = 0xC1800104
2021-09-20 02:45:31, Error                 MOUPG  CDlpTask::Cancel(982): Result = 0xC1800104
2021-09-20 02:45:31, Error                 MOUPG  CDlpTask::Cancel(982): Result = 0xC1800104
2021-09-20 02:45:31, Error                 MOUPG  CDlpTask::Cancel(982): Result = 0xC1800104
2021-09-20 02:45:31, Info                  MOUPG  CSetupUIManager: Showing exiting Setup
2021-09-20 02:45:31, Info                  MOUPG  CInstallUI::CInstallUIMessageWindow::ForceQuit
2021-09-20 02:45:31, Info                  MOUPG  CInstallUI::Quit: Posted MSG_INSTALLUI_FORCE_QUIT
2021-09-20 02:45:31, Info                  MOUPG  Force ending Message pump
2021-09-20 02:45:31, Info                  MOUPG  CInstallUI::ExitInstance
2021-09-20 02:45:32, Info                  MOUPG  SetupUI: Calling PowerClearRequest with type [0x1]...
2021-09-20 02:45:32, Info                  MOUPG  SetupUI: Power request cleared!
2021-09-20 02:45:32, Info                  MOUPG  **************** SetupHost Logging End ****************
4

Hmm… I noticed the timestamps from your setuperr.log and setupact.log (9/20 around 2:45am) don’t match the readout from your SetupDiag with the 0xC1900101 - 0x20017 code (9/20 around 11:50pm). It might be possible that you checked the log files before this most recent attempt to update, and that the file has changed since then.

So possibly if you look at the log files now, it may have the “C1900101” string in it. Or I could be wrong, I’m just trying to think why the code wouldn’t be in the logs.

~Max

5

You’re right, that’s strange. The logs are are indeed newer than the Setdiag timestamps, though I’m sure that I did run SetupDiag after having done the latest update attempt. I think it’s best now for me to run an update attempt again, thus let create the latest setup logs and then run SetupDiag again. That’ll take at least 1.5 h (every time, that’s why I’m so pissed…).

6

No, it’s the other way around. The SetupDiag says the upgrade that threw the error postdates the log files. I don’t know if you are presently copying text directly from the log files to post, or if you made a copy yesterday and are posting from that. If you made copies they may be outdated.

~Max

7

No, I opened the last logs just before opening this thread. Maybe I have to run SetupDiag once more, or maybe I looked in the wrong folder for the xml file it creates as output Wait a minute…

ETA: it even gets stranger. The system date says that the SetupDiag file has been created today, while the setup logs are from yesterday. That matches with my memory, I took the last update attempt yesterday and ran SetupDiag today. But the timestamps in the event list in the SetupDiag log are earlier than those in the setup logs. I’ve got no explanation.

8

I wouldn’t be too concerned about the file creation date, just the timestamps in the log files themselves and the timestamp SetupDiag gives for “UpgradeStartTime” and “UpgradeEndTime”.

SetupDiag says you started the update on 9/20 at 10:19pm and it ended at 11:50pm, even though you might have run SetupDiag today 9/21. SetupDiag reports that upgrade encountered error 0xC1900101 - 0x20017. Microsoft says with that particular error you have to look in the log files to identify the problematic driver.

The log files you posted contain entries from 9/20 around 2:45am, which is about 20 hours before SetupDiag says your system encountered error 0xC1900101 - 0x20017. If that makes sense.

You should be looking for Setuperr.log and Setupact.log files in the %windir%\Panther directory, just to make sure you have the right log files.

If you are looking at the right files and they don’t even contain the error code you are trying to diagnose, you could try generic troubleshooting (disconnect any devices you can, safe boot, etc) or you can try updating again to generate fresh logs.

~Max

9

I’ve run SetupDiag again, with the same results. I think it catches the setup logs from some other folder, while the logs I was posting are in C:\Windows\Panther\NewOs.

10

Try looking directly in C:\Windows\Panther instead of a subfolder.

C:\Windows\Panther\setuperr.log
C:\Windows\Panther\setupact.log

~Max

11

There are no files in \Panther. I think it really would be best to run the update again, just to make sure to have matching files.

12

Best of luck. :pray:

~Max

13

Thanks. I’d be glad to have your help again when I can post more consistent data, but it’ll take til tomorrow. It’s almost midnight here, I’ll start the update and then go to bed. Thanks again for your help so far.

14

One thing to keep in mind, those log files are by default hidden and have no read permissions. You might have to run notepad as administrator then open them from File->Open by typing in the full path C:\Windows\Panther\setuperr.log.

~Max

15

I’m admin of this account and have set hidden files to be shown in Explorer, but I’ll look into it.

ETA: nope, that wasn’t it, notepad explicetly run as admin didn’t bring up anything in that folder.

16

I am no expert but at this stage, I would be thinking about reloading W10 totally rather than a simple update.

17

I know, I know, and I’m that short of doing just that. But it would be a PITA. My elderly parents are in the middle of selling an apartment in Berlin, 600 kilometers from here, over a real estate company with a lot of email exchanges. I wouldn’t want to take such drastic steps, only as last resort, because I fear that I can’t get everything going as they are used to, because they struggle with the situation anyway. Was it my own laptop, I long would’ve installed from scratch.

18

I’ve not encountered a problem like this before. But, given that what you have right now suggests the issue may be drivers, I would consider completely uninstalling any drivers that aren’t necessary, and trying the update again. You could even go so far as to disable the display and sound drivers, and then reinstall them after the upgrade if it works.

However, before going that far, I’d try one other thing: (temporarily) disabling security features. That’s the one place where I’ve run into potential issues with drivers. I’d pull up “Device Security” and make sure that Core Isolation > Memory Isolation was not enabled. I’d also consider disabling TPM and Secure Boot, in case they gave issues.

You could also make sure there are no BIOS updates for the system in question. Those can often be what keeps Windows from offering the next Feature Update.

I also notice some things I would normally consider that you’ve not mentioned. It’s possible you are considering them but want to try everything else first, and that’s fine, but I do want to mention them.

The first is doing an in-place upgrade of the same version of Windows you are currently on. Get the latest ISO for 20H2 and just try an upgrade install. This worked for me back in the Windows 7 days when I had a problem like this.

The second is to try to feature update to 21H1 using the full ISO version, for similar reasons. You’re an update behind, and I think using the ISO would force a full upgrade. If not, then you could then try the aforementioned same version upgrade, just with 21H1 this time.

19

There wasn’t an option for Core Isolation in Device Security, and no way to deactivate TMP in the snap-in tmp.msc. There was an option to delete TMP, but I’m too timid to do that because I don’t know much about TMP and cannot assess any possible risks. But I did deactivate Secure Boot in BIOS, and now am running another update attempt. Knock on wood!

20

Nope, that wasn’t it. Still didn’t successfully updated with Secure Boot disabled. Taking BigT’s first advice now and disabling drivers.