Asked by:
Upgrade failure: MSG_INSTALLUI_SWITCH_TO_ERROR_PAGE Reporting error event -> [0x80070241, 0x50014]
Question
-
How do you troubleshoot a failed Windows upgrade with this setuperr.log?
2018-09-29 01:32:42, Error CONX Windows::Compat::Appraiser::IsMeteredConnection (178): Failed to get NetworkCostType assuming metered network [0x80004005].[gle=0x80004005]
2018-09-29 01:33:20, Error CONX 0xd0000034 Failed to add user mode driver [%SystemRoot%\system32\DRIVERS\UMDF\uicciso.dll]
2018-09-29 01:33:34, Error CONX Windows::Compat::Appraiser::WicaApplicationInventory::AddItemProperty (514): App Inventory returned duplicate file c:\program files (x86)\hewlett-packard\hp support solutions\modules\sudf\detect_deviceadded.exe.[gle=0x8007000d]
2018-09-29 01:33:34, Error CONX Windows::Compat::Appraiser::WicaApplicationInventory::AddItemProperty (514): App Inventory returned duplicate file c:\program files (x86)\hewlett-packard\hp support framework\resources\hpperformancetuneup\hpperformancetuneup.exe.[gle=0x8007000d]
2018-09-29 01:33:34, Error CONX Windows::Compat::Appraiser::WicaApplicationInventory::AddItemProperty (514): App Inventory returned duplicate file c:\program files (x86)\hewlett-packard\hp support framework\resources\hpprintspooler\hpprintspooler.exe.[gle=0x8007000d]
2018-09-29 01:33:34, Error CONX Windows::Compat::Appraiser::WicaApplicationInventory::AddItemProperty (514): App Inventory returned duplicate file c:\program files (x86)\hewlett-packard\hp support framework\resources\hpwarrantycheck\hpwarrantychecker.exe.[gle=0x8007000d]
2018-09-29 01:33:34, Error CONX Windows::Compat::Appraiser::WicaApplicationInventory::AddItemProperty (514): App Inventory returned duplicate file c:\program files\intel\intel(r) rapid storage technology\iastordatamgrsvc.exe.[gle=0x8007000d]
2018-09-29 01:33:34, Error CONX Windows::Compat::Appraiser::WicaApplicationInventory::AddItemProperty (514): App Inventory returned duplicate file c:\program files\intel\intel(r) rapid storage technology\iastorui.exe.[gle=0x8007000d]
2018-09-29 01:33:34, Error CONX Windows::Compat::Appraiser::WicaApplicationInventory::AddItemProperty (514): App Inventory returned duplicate file c:\program files (x86)\intel\intel(r) management engine components\lms\lms.exe.[gle=0x8007000d]
2018-09-29 01:33:34, Error CONX Windows::Compat::Appraiser::WicaApplicationInventory::AddItemProperty (514): App Inventory returned duplicate file c:\windows\syswow64\windowspowershell\v1.0\powershell_ise.exe.[gle=0x8007000d]
2018-09-29 01:33:34, Error CONX Windows::Compat::Appraiser::WicaApplicationInventory::AddItemProperty (514): App Inventory returned duplicate file c:\$windows.~ws\sources\setuphost.exe.[gle=0x8007000d]
2018-09-29 01:54:27, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{52776FBF-403C-49cc-b7cb-dd557f36096A} already loaded __cdecl Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)
2018-09-29 01:55:31, Error [0x080389] MIG Failure while calling IDiscovery->Gather for Plugin={ServerPath="Microsoft-Windows-AppX-Deployment-Server\AppxUpgradeMigrationPlugin.dll", CLSID={AE27C1A6-25F2-45FD-9A28-081B81F29E0A}, ThreadingModel=Apartment}. Error: 0x87AF000B
2018-09-29 01:55:31, Error MIG Error 0x87AF000B while executing critical action Action,CMXEPlugin,C:\$WINDOWS.~BT\Sources\ReplacementManifests,Microsoft-Windows-AppX-Deployment-Server\AppxUpgradeMigrationPlugin.dll,{AE27C1A6-25F2-45FD-9A28-081B81F29E0A},Apartment. Migration will abort[gle=0x000000cb]
2018-09-29 01:55:32, Error Gather failed. Last error: 0x00000000
2018-09-29 01:55:32, Error SP pSPDoMainGather: Gather operation failed. Error: 0x0000002C
2018-09-29 01:55:33, Error SP CGatherData: Migration phase failed. Status: 44[gle=0x00000002]
2018-09-29 01:55:34, Error SP Operation failed: Gather data, scope: EVERYTHING. Error: 0x8007042B[gle=0x000000b7]
2018-09-29 01:56:09, Error CSetupAutomation::Resurrect: File not found: C:\$WINDOWS.~BT\Sources\Panther\automation.dat[gle=0x00000002]
2018-09-29 01:56:09, Error SP CSetupPlatform::ResurrectAutomation: Failed to resurrect automation: 0x80070002[gle=0x00000002]
2018-09-29 01:56:24, Error SP CMountWIM::DoExecute: Failed to mount WIM file C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim. Error 0x80070241[gle=0x00000241]
2018-09-29 01:56:24, Error SP Operation failed: Mount WIM file C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim, index 1 to C:\$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount. Error: 0x80070241[gle=0x000000b7]
2018-09-29 01:56:24, Error SP ExecuteOperations: Failed execution phase Pre-Finalize. Error: 0x80070241
2018-09-29 01:56:24, Error MOUPG MoSetupPlatform: ExecuteCurrentOperations reported failure!
2018-09-29 01:56:24, Error MOUPG MoSetupPlatform: Using action error code: [0x80070241]
2018-09-29 01:56:24, Error MOUPG CDlpActionPreFinalize::ExecuteRoutine(545): Result = 0x80070241
2018-09-29 01:56:25, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Execute(441): Result = 0x80070241
2018-09-29 01:56:25, Error MOUPG CDlpTask::ExecuteAction(3259): Result = 0x80070241
2018-09-29 01:56:25, Error MOUPG CDlpTask::ExecuteActions(3413): Result = 0x80070241
2018-09-29 01:56:25, Error MOUPG CDlpTask::Execute(1644): Result = 0x80070241
2018-09-29 01:56:25, Error MOUPG CSetupManager::ExecuteTask(2367): Result = 0x80070241
2018-09-29 01:56:25, Error MOUPG CSetupManager::ExecuteTask(2330): Result = 0x80070241
2018-09-29 01:56:25, Error MOUPG CSetupManager::ExecuteInstallMode(867): Result = 0x80070241
2018-09-29 01:56:25, Error MOUPG CSetupManager::ExecuteDownlevelMode(381): Result = 0x80070241
2018-09-29 01:56:26, Error SP CDeploymentBase::CleanupMounts: Unable to unmount the directory C:\$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount. Error: 0xC142011C[gle=0xc142011c]
2018-09-29 01:56:30, Error MOUPG CSetupManager::Execute(273): Result = 0x80070241
2018-09-29 01:56:30, Error MOUPG CSetupHost::Execute(382): Result = 0x80070241
...
.
.
These are from the setupact.log:
2018-09-29 01:56:25, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [CompatBlockEncountered]=[0x0] [c40fa810-4e5a-43c9-bb89-7573aa7036c7][5dea7991-c222-4f52-8fe3-6c3758e7a330][][0x1]
2018-09-29 01:56:25, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [CompatHardBlockedProviders]=[0x0] [c40fa810-4e5a-43c9-bb89-7573aa7036c7][5dea7991-c222-4f52-8fe3-6c3758e7a330][][0x1].
.
.
2018-09-29 01:56:29, Info SP Closing Panther Logging
2018-09-29 01:56:29, Info MOUPG MoSetupPlatform: Setup Platform object released!
2018-09-29 01:56:29, Info MOUPG Finalize: Leaving Execute Method
2018-09-29 01:56:29, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2004]
2018-09-29 01:56:29, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2003]
2018-09-29 01:56:29, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2001]
2018-09-29 01:56:29, Info MOUPG ProgressHandlerAction: Sending final progress message for action [0].
2018-09-29 01:56:29, Info MOUPG ProgressHandlerAction FinalUpdate: 0x0, 0x0 / 0x0, 0x0
2018-09-29 01:56:29, Info MOUPG ProgressHandlerAction: Sending final progress message for action [0].
2018-09-29 01:56:29, Info MOUPG ProgressHandlerAction FinalUpdate: 0x0, 0x0 / 0x0, 0x0
2018-09-29 01:56:29, Info MOUPG Signalling actions thread to shut down.
2018-09-29 01:56:29, Info MOUPG Waiting for actions thread to exit.
2018-09-29 01:56:29, Info MOUPG Actions thread has exited.
2018-09-29 01:56:29, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2004]
2018-09-29 01:56:29, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2000]
2018-09-29 01:56:29, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x3000]
2018-09-29 01:56:29, Info MOUPG DlpTask: Leaving Execute Method
2018-09-29 01:56:29, Info MOUPG SetupManager::ExecuteCustomScript: Type = [0x3]
2018-09-29 01:56:29, Info MOUPG SetupManager::ExecuteCustomScript: No scripts found. Finished type [0x3]
2018-09-29 01:56:29, Info MOUPG SetupNotify: Specifying extended data [0x50014] for error [0x80070241].
2018-09-29 01:56:29, Info MOUPG CSetupUIManager: Showing error message
2018-09-29 01:56:29, Info MOUPG CInstallUI::ShowErrorMessage: Posted MSG_INSTALLUI_SWITCH_TO_ERROR_PAGE
2018-09-29 01:56:29, Info MOUPG SetupHost: Reporting error event -> [0x80070241, 0x50014]
2018-09-29 01:56:29, Info MOUPG CInstallUI::CInstallUIMessageWindow::SwitchToErrorPage
2018-09-29 01:56:29, Info MOUPG CInstallUI::SwitchToErrorPage
2018-09-29 01:56:29, Warning MOUPG SetupNotify::ReportEvent - Report ID or Event Reporter not available.
2018-09-29 01:56:29, Info MOUPG SetupManager: FailureCount = [185]
2018-09-29 01:56:29, Info MOUPG SetupManager: Requesting cleanup level [0x2] from parent process.
2018-09-29 01:56:29, Info MOUPG Setup phase change: [SetupPhaseError] -> [SetupPhaseUnpack]
2018-09-29 01:56:29, Info MOUPG SetupManager: Deleting task: [Prepare]...
2018-09-29 01:56:29, Info MOUPG SetupManager: Deleting task: [Install]...
2018-09-29 01:56:29, Info MOUPG SetupManager: Deleting task: [Exit]...
2018-09-29 01:56:29, Info MOUPG SetupManager: Found unpack task! Restarting layout action...
2018-09-29 01:56:29, Info MOUPG CInstallUI::ShowMessageBox: Showing MessageBox
2018-09-29 01:56:30, Error MOUPG CSetupManager::Execute(273): Result = 0x80070241
2018-09-29 01:56:30, Error MOUPG CSetupHost::Execute(382): Result = 0x80070241
2018-09-29 01:56:37, Info MOUPG CInstallUI::Quit: Posted MSG_INSTALLUI_FORCE_QUIT
2018-09-29 01:56:37, Info MOUPG CInstallUI::CInstallUIMessageWindow::ForceQuit
2018-09-29 01:56:37, Info MOUPG Force ending Message pump
2018-09-29 01:56:37, Info MOUPG CInstallUI::ExitInstance
2018-09-29 01:56:38, Info CONX Uninitializing compatibility provider wsc:setup:...
2018-09-29 01:56:38, Info CONX Uninitializing compatibility provider wsc:wica:...
2018-09-29 01:56:38, Info MOUPG SetupUI: Calling PowerClearRequest with type [0x1]...
2018-09-29 01:56:38, Info MOUPG SetupUI: Power request cleared!
2018-09-29 01:56:38, Info MOUPG **************** SetupHost Logging End ****************
- Edited by questionsformicrosoftproducts Saturday, September 29, 2018 7:35 AM
Saturday, September 29, 2018 7:04 AM
All replies
-
The problem could be related to available space on EFI system reserved partition on your computer's disk.
You can test the method provided here.
Answer by Booradley_oz.
- Edited by T. Kujala Sunday, September 30, 2018 7:17 AM
Sunday, September 30, 2018 7:16 AM -
There were error codes prior to this that were related to the free space on the EFI partition.
For example: We couln't upgrade the system reserved partition.
The MSR was enlarged to 2 GB.
The EFI deficiency was 11 MB.
The fonts and many of the languages were removed from the EFI partition.
At least 2x the need space was achieved by removing only the languages and then removing the fonts created a lot of extra space.
The partition deficiency disappeared from the logs and the new error code appeared:
MSG_INSTALLUI_SWITCH_TO_ERROR_PAGE Reporting error event -> [0x80070241, 0x50014]
The are no longer any size problems.
What do you see in the logs?
- Edited by questionsformicrosoftproducts Sunday, September 30, 2018 7:42 AM
Sunday, September 30, 2018 7:40 AM -
There is a Microsoft tool, setupdiag and it just worked displaying:
SetupDiag v1.00
Copyright (c) Microsoft Corporation. All rights reserved.
Searching for setup logs, this can take a minute or more depending on the number and size of the logs...please wait.
Found 1 setupact.logs.
Processing setupact.log 1 of 1
Found 3 setupact.logs.
Processing setupact.log 1 of 3
Processing setupact.log 2 of 3
Processing setupact.log 3 of 3
Found 1 setupact.logs.
Processing setupact.log 1 of 1
Found 1 setupact.logs.
Processing setupact.log 1 of 1
Found 3 setupact.logs.
Processing setupact.log 1 of 3
Processing setupact.log 2 of 3
Processing setupact.log 3 of 3
Found 1 setupact.logs.
Processing setupact.log 1 of 1
Found 1 setupact.logs.
Processing setupact.log 1 of 1
Found 3 setupact.logs.
Processing setupact.log 1 of 3
Processing setupact.log 2 of 3
Processing setupact.log 3 of 3
Found 1 setupact.logs.
Processing setupact.log 1 of 1
Found 1 setupact.logs.
Processing setupact.log 1 of 1
Found 3 setupact.logs.
Processing setupact.log 1 of 3
Processing setupact.log 2 of 3
Processing setupact.log 3 of 3
Found 1 setupact.logs.
Processing setupact.log 1 of 1
Found 1 setupact.logs.
Processing setupact.log 1 of 1
Found 3 setupact.logs.
Processing setupact.log 1 of 3
Processing setupact.log 2 of 3
Processing setupact.log 3 of 3
Found 1 setupact.logs.
Processing setupact.log 1 of 1
Gathering information from setup logs.
SetupDiag: processing rule: CompatScanOnly.
...No match.
SetupDiag: processing rule: BitLockerHardblock.
...No match.
SetupDiag: processing rule: VHDHardblock.
...No match.
SetupDiag: processing rule: PortableWorkspaceHardblock.
...No match.
SetupDiag: processing rule: AuditModeHardblock.
...No match.
SetupDiag: processing rule: SafeModeHardblock.
...No match.
SetupDiag: processing rule: InsufficientSystemPartitionDiskSpaceHardblock.
...No match.
SetupDiag: processing rule: HardblockApplication.
...No match.
SetupDiag: processing rule: HardblockDeviceOrDriver.
...No match.
SetupDiag: processing rule: HardblockMismatchedLanguage.
..No match.
SetupDiag: processing rule: HardblockFlightSigning.
..No match.
SetupDiag: processing rule: DiskSpaceBlockInDownLevel.
..No match.
SetupDiag: processing rule: DiskSpaceFailure.
..No match.
SetupDiag: processing rule: DeviceInstallHang.
..No match.
SetupDiag: processing rule: DebugSetupMemoryDump.
.No match.
SetupDiag: processing rule: DebugSetupCrash.
.No match.
SetupDiag: processing rule: DebugMemoryDump.
.No match.
SetupDiag: processing rule: FindDebugInfoFromRollbackLog.
.No match.
SetupDiag: processing rule: AdvancedInstallerFailed.
..No match.
SetupDiag: processing rule: FindSuccessfulUpgrade.
..No match.
SetupDiag: processing rule: FindSetupHostReportedFailure.
...
Matching Profile found: FindSetupHostReportedFailure - 6253C04F-2E4E-4F7A-B88E-95A69702F7EC
Error: SetupDiag reports down-level failure, Operation: Finalize, Error: 0x80070241 - 0x50014
SetupDiag found 1 matching issue.
SetupDiag results were logged to: .\SetupDiagResults.log
Logs ZipFile created at: .\Logs_3.zip
.
.
.
FindSetupHostReportedFailure - 6253C04F-2E4E-4F7A-B88E-95A69702F7EC- Gives information about failures surfaced early in the upgrade process by setuphost.exe
.
.
.
How do you troubleshoot the upgrade failures related to setuphost.exe?
What is the meaning of the characters in this: 6253C04F-2E4E-4F7A-B88E-95A69702F7EC
- Edited by questionsformicrosoftproducts Sunday, September 30, 2018 10:14 AM
Sunday, September 30, 2018 10:10 AM -
Hi,When searching log files, SetupDiag uses a set of rules to match known issues. These rules are contained in the rules.xml file which is extracted when SetupDiag is run.Each rule name and its associated unique rule identifier are listed with a description of the known upgrade-blocking issue. In the rule descriptions, the term "down-level" refers to the first phase of the upgrade process, which runs under the starting OS.29.FindSetupHostReportedFailure - 6253C04F-2E4E-4F7A-B88E-95A69702F7EC•Gives information about failures surfaced early in the upgrade process by setuphost.exeMore information, you can refer to the following link:
For error code 0x80070241, it indicates that the hash for the image cannot be found in the systemcatalogs. The image is likely corrupt or the victim of tampering.
I suggest you upgrading Windows using other image file to test.Hope it could be helpful.Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Monday, October 1, 2018 12:42 PM -
What other image options are available besides Windows 10 iso?
For 6253C04F-2E4E-4F7A-B88E-95A69702F7EC what do the numbers and letters refer to in the operating system or registry?
Is this meaningless or do you process this part of the message?
Do setuphost.exe problems always present with these characters or do the characters vary depending upon the setuphost.exe problem?
An iso that was identical was ran (1703).
The iso to upgrade to failed (1803) with the above setuperr/setupact logs.
Multiple software applications and drivers were uninstalled to see if there was any impact and there was none. Clean boot was used. Only one Microsoft antivirus was in use and Malwarebytes had been uninstalled.
What methods are available to allow upgrades with a setup.exe problem?
It appears that the setup.exe can occur even if the sfc /scannow reports no integrity violations and dism /online /cleanup-image /restorehealth did not find any integrity violations and an in place upgrade repair with the identical iso worked.
How come the setup.exe problems were not fixed by a successful 1703 iso?
What other image options are available?
What other troubleshooting steps are available?
Monday, October 1, 2018 1:54 PM
