Error moupg cdlptask cancel 982 result 0xc1800104

Full Windows Version: Version 10.0.18363 Build 18363

I am attempting to update Windows 10 Pro from version 1909 to 21H1. This is running on a SuperMicro X9DRL-7F motherboard with Xeon E5-2670 CPUs. The BIOS is current (to my knowledge) at v3.3.

When applying the update, the normal install process chugs along until Windows attempts to restart. During the restart, the system gets to the Windows logo and after a few minutes comes up with a Blue Screen and the message IRQL Driver Not Less or Equal.

After this the system restarts and loads Windows successfully, but the upgrade has been aborted/rolled back and the system is still on 1909. When using the Media Creation Tool for 21H1, after the install attempt, the system reports 0xC1900101 — 0x20017.

This makes me believe there is an old driver (certainly plausible) that needs updating, but I’m unsure how to track down what that driver is.

The Setuperr.log shows:

MOUPG CInstallUI::GetDefaultLanguage(2027): Result = 0x80070002[gle=0x00000002]

MOUPG CSetupManager::GetDUSetupResults(6511): Result = 0x80070490

MOUPG CDlpTask::Cancel(982): Result = 0xC1800104

MOUPG CDlpTask::Cancel(982): Result = 0xC1800104

MOUPG CDlpTask::Cancel(982): Result = 0xC1800104

MOUPG CDlpTask::Cancel(982): Result = 0xC1800104

Any ideas on where I need to drill down further in order to find the Driver (or other culprit) that’s stopping the update?

Sorry for the delay in replying.

First a quick update for Boggin, or anyone else.

I closed the ‘stuck’ Tweaking Repair task by clicking on the ‘X’ with the Red Background, expecting it to stop the ‘All Repairs’ task I had started running, as Administrator, in Safe Mode, with Network.  Instead it stopped the current stuck individual task and jumped to the next one of the 49 tasks in the ‘All Repairs’ list.  As it did so I briefly saw a flash of a log repeating something like ‘… can’t access or access denied … file in use …’ then the log was gone!!  I got the meaning of it though and assume it indicated it had spent all those 25 hours I’d left it running repeatedly trying to access a file that another process was using, (not that this was indicated on the screen).  It progressed on to all the other tasks in the list and completed them, though there was one task on which it appeared to get stuck, but as I was was clicking between the log and task list, and was about give up on that task and click ‘X’ to cancel it, the task finished. (I don’t think I did click ‘X’, so I think it completed ok!.)  Anyway the ‘All Repairs’ task moved on down the list and finished.

So I believe all repairs were completed except one, (maybe two).

But having had at least one task fail I decided to rerun the full repair list again, in Safe Mode, but this time without Network, in case it was a Network related process that was using the file causing it to get stuck.  I also thought I’d run the tasks one at a time so I could track where any problems were occurring more easily.  So that’s what I’m currently doing.  On task ’04 — Register System Files’, which is where I think it got stuck before, its trying to register C:windowssysWOW64FPWPP.DLL but is again stuck.  If this is because it’s in use by another process, I’ve no idea which one, or what I could do to get the registration to proceed.  Neither can I see a way to skip to the next item in that ‘Register System Files’ repair script.  Also, I guess if I stop the task, it will mean that the registration repair of all the subsequent System Files won’t be done.  That may, or may not, be a problem!

Also as clarification for Boggin , I’m not trying to sort out my MS Surface, running fine which is why I’m using it to submit these posts. 

Its my other machine that’s having problems. It’s a HP Pavilion dv6 which, to answer Boggin‘s question in his last post, does have Radeon Dual Graphics and Quad Core.  The processor is AMD A6-3410MX APU with Radeon(tm) HD Graphics, 1597 Mhz, 4 Core(s), 4 Logical Processor(s).  I’ve been trying do a repair this PC since early September following repeated BSOD with ‘Stop code: DPC  WATCHDOG VIOLATION’.  The advice for fixing this amounted to a rather vague, «update the drivers and run Windows Update», … which didn’t fix it.  So after many attempts at different resolutions I decided to do a Windows 10 re-installation, using the Microsoft MediaCreationTool as I understand this will mean I can avoid having to reinstall all my Apps.  However every time I ran it, it fails, after «Creating Media», it ‘cleans up and closes’, and doesn’t progress to the installation stage!  This is the reason why I followed Bitec69’s YouTube advice and decided to run the Tweaking Repairs as I hope, if I can run all the repairs, that the MediaCreationTool may then succeed.

I’m not sure if the following have any relevance to resolving these problems but I’ll restate them now in case they do.  The computer originally had AMD Catalyst Suit installed and AMD had repeatedly, over the previous couple of years, sent updates for this, which, when run responded with «this update can’t be applied to the chip-set and version of AMD Catalyst Suit installed», (why offer me the update then …)   I did try to update the drivers in the normal way as Boggin describe, and it responded that the current driver was the best available, but I thought I’d checkout AMD’s site to be sure.  On their site they advised against using AMD Catalyst Suit on Windows 10 and said that using the Windows 10 generic divers was the best option.  So I uninstalled the originally installed AMD Catalyst Suit thinking the Windows 10 generic offer would be up to date and better, it worked … or did it?  The properties for all of drivers reported that they are working properly, but this isn’t consistent with Device Manager which now displays the warning triangles mentioned in my previous post. (November 08, 2018, 09:37:28)  Why is that?

Four groups of drivers show a triangular warning symbol even though each driver said it was working fine.  They were;
-Display adaptors — AMD Radeon HD 6520G and HD 7400M Series
-IDE ATA/ATAPI controllers — AMD SATA Controller, ATA Channel 0 & 1, and Standard Dual Channel PCI IDE Controller
-Sound, video and game controller — AMD High Definition Audio Device
-Storage controller — Microsoft Storage Spaces Controller

Also Boggin can you, or anyone else, tell me the meaning of these items listed in the C:$Windows.~BTPanthersetuperr.log which is created when I try running Windows MediaCreationTool1803.exe that i mention two posts ago. (November 08, 2018, 06:40:07)

Here’s the setuperr.log contents:
2018-03-04 05:29:11, Error                 MOUPG  CInstallUI::GetDefaultLanguage(1785): Result = 0x80070002[gle=0x00000002]
2018-03-04 05:41:30, Error                 MOUPG  CSetupManager::GetDUSetupResults(5499): Result = 0x80070490
2018-03-04 05:41:38, Error                 MOUPG  CDlpTask::Cancel(979): Result = 0xC1800104
2018-03-04 05:41:38, Error                 MOUPG  CDlpTask::Cancel(979): Result = 0xC1800104
2018-03-04 05:41:38, Error                 MOUPG  CDlpTask::Cancel(979): Result = 0xC1800104
2018-03-04 05:41:38, Error                 MOUPG  CDlpTask::Cancel(979): Result = 0xC1800104

Я просто попытался обновить машину с Windows 7 до Windows 10, и она не удалась без видимой причины. Произошел сбой как Windows 10 Upgrade Assistant и Media Creation Tool первый с 0xc1900200 а второй с кодом ошибки 0x800704DD-0x90016 .

Когда это происходит (с помощником по обновлению), в средстве просмотра событий появляются следующие три события. Почему они упоминают Китай ?! Машина (и всегда была) из Figgin ‘Central Europe и, кажется, отвечает требованиям (я получаю противоречивые утверждения от Nagger об обновлении, как также показано ниже, заметил это сегодня, не помню, чтобы когда-либо видел его раньше).

Машина одновременно «Good to go» и «Unable to».

Fault bucket 568497307, type 29
Event Name: WinSetupDiag02
Response: Not available
Cab Id: 0

Problem signature:
P1: 1
P2: 2
P3: X
P4: 3
P5: 0xC1900200
P6: 0x40008
P7: 7601
P8: win7sp1_gdr
P9: X
P10: X

Attached files:
C:$WINDOWS.~BTSourcesPanthersetupact.log
C:$WINDOWS.~BTSourcesPantherdiagerr.xml

These files may be available here:
C:ProgramDataMicrosoftWindowsWERReportArchiveNonCritical_1_8a6ccaa215c554b926ec248ab1adcd15b9e934_083572ce

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2cb21a52-41ef-11e6-9881-005056c00008
Report Status: 0

Fault bucket 2047321030, type 29
Event Name: Win10UpgradeProgramInChina
Response: Not available
Cab Id: 125216112230

Problem signature:
P1: Win10UpgradeChina
P2: Failed
P3: Setup execution result failed!
P4: 6.1 (7601),Service Pack 1,1, 256
P5: {E52ABFC2-76BB-4908-883F-CA581FDD83F9}
P6: -1047526912
P7: 1.4.9200.17332-[URL:9194:<1.4.9200.17332>:<1>]
P8: Undefined
P9: true
P10: Undefined

Attached files:
C:$GetCurrentdownlevel_2016_07_04_21_49_14_168.rpt
C:$WINDOWS.~BTSourcesPanthersetupact.log
C:$WINDOWS.~BTSourcesPanthersetuperr.log
C:$GetCurrentLogsdownlevel_2016_07_04_21_49_14_168.log

These files may be available here:
C:ProgramDataMicrosoftWindowsWERReportArchiveNonCritical_Win10UpgradeChin_a1a3d0aaa1e724b4e6a2355b30d3e1285fdb8950_cab_048582b6

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2ecc1150-41ef-11e6-9881-005056c00008
Report Status: 8

Fault bucket , type 0
Event Name: Win10UpgradeProgramInChina
Response: Not available
Cab Id: 0

Problem signature:
P1: Win10UpgradeChina
P2: Failed
P3: Setup execution result failed!
P4: 6.1 (7601),Service Pack 1,1, 256
P5: {E52ABFC2-76BB-4908-883F-CA581FDD83F9}
P6: -1047526912
P7: 1.4.9200.17332-[URL:9194:<1.4.9200.17332>:<1>]
P8: Undefined
P9: true
P10: Undefined

Attached files:
C:$GetCurrentdownlevel_2016_07_04_21_49_14_168.rpt
C:$WINDOWS.~BTSourcesPanthersetupact.log
C:$WINDOWS.~BTSourcesPanthersetuperr.log
C:$GetCurrentLogsdownlevel_2016_07_04_21_49_14_168.log

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: 2ecc1150-41ef-11e6-9881-005056c00008
Report Status: 0

Вот меньший setuperr.log:

2016-07-04 15:53:47, Error                 MOUPG  CSystemHelper::CheckConnectedStandby(642): Result = 0x80070057
2016-07-04 15:53:51, Error                        CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2016-07-04 15:53:51, Error                        CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2016-07-04 15:53:51, Error                 MOUPG  CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Suspend(1066): Result = 0xC1800104
2016-07-04 15:53:51, Error                 MOUPG  CSetupManager::ExecuteInstallMode(724): Result = 0x800705BB
2016-07-04 15:53:51, Error                 MOUPG  CSetupManager::ExecuteDownlevelMode(389): Result = 0x800705BB
2016-07-04 15:53:52, Error                 MOUPG  CSetupManager::Execute(232): Result = 0x800705BB
2016-07-04 15:53:52, Error                 MOUPG  CSetupHost::Execute(371): Result = 0x800705BB
2016-07-04 15:53:52, Error                 MOUPG  CSystemHelper::CheckConnectedStandby(642): Result = 0x80070057
2016-07-04 15:56:59, Error                 MOUPG  CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class ICompatAction> > > >::Suspend(1066): Result = 0xC1800104
2016-07-04 15:56:59, Error                 MOUPG  CSetupManager::ExecuteInstallMode(730): Result = 0xC1900200
2016-07-04 15:56:59, Error                 MOUPG  CSetupManager::ExecuteDownlevelMode(389): Result = 0xC1900200
2016-07-04 15:56:59, Error                 SP     CSetupPlatform::ResurrectNewSystem: Cannot resurrect new system.: Win32Exception: \?C:$Windows.~BTSourcesNewSystem.dat: The system cannot find the file specified. [0x00000002] __cdecl UnBCL::FileStream::FileStream(const class UnBCL::String *,enum UnBCL::FileMode,enum UnBCL::FileAccess,enum UnBCL::FileShare,unsigned long)[gle=0x00000002]
2016-07-04 15:57:01, Error                 MOUPG  CDlpTask::Cancel(979): Result = 0xC1800104
2016-07-04 15:57:01, Error                 MOUPG  CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class ICompatAction> > > >::CheckInitialized(228): Result = 0x8000000A
2016-07-04 15:57:01, Error                 MOUPG  CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class ICompatAction> > > >::Cancel(154): Result = 0x8000000A
2016-07-04 15:57:01, Error                 MOUPG  CDlpTask::Cancel(1030): Result = 0x8000000A
2016-07-04 15:57:01, Error                 MOUPG  CDlpManager::Reset(1672): Result = 0x8000000A
2016-07-04 15:57:01, Error                 MOUPG  SetupManager: Reset WinDlp State failed with error [0x8000000A]
2016-07-04 15:57:01, Error                 MOUPG  SetupManager: Failed requested cleanup: [0x8000000A]
2016-07-04 15:57:01, Error                 MOUPG  CSetupManager::Execute(232): Result = 0xC1900200
2016-07-04 15:57:01, Error                 MOUPG  CSetupHost::Execute(371): Result = 0xC1900200