Hi everyone, I’m encountering an issue while trying to update one of my servers from Windows Server 2022 build 20348.3091 to 2025 Standard. I have two servers, and the first one updated smoothly without any issues. However, the second server keeps throwing the error: “Windows Server installation has failed.” I’ve double-checked the basic requirements and ensured everything is in order, but the issue persists. Has anyone experienced this before or know how to resolve it? I’m looking for troubleshooting tips or guidance on what might be causing this problem. Any help would be greatly appreciated!
change registry keys in: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion to correspond to 2025 Standard. Then upgrade.
It is possible that there is some program in the background that is holding it back. The only thing to try is the "clean installation" option. It used to help me because the classic upgrade couldn't go through. The only downside is that it will wipe everything, so you'll have to back up your data and install everything again.
its a domain controller in a lab and i cannot just go out and delete everything. i have updated multiple Domain controllers and al went fine. the log i can find are 2025-02-12 20:22:48, Info Already stored original correlation vector [3w/QApSOdUeYrZpO.18] in config file 2025-02-12 20:22:48, Info Input correlation vector is [3w/QApSOdUeYrZpO.31] 2025-02-12 20:22:48, Warning Get a different correlation vector 2025-02-12 20:22:48, Info Copy telemetry file: source folder: C:\$WINDOWS.~BT\Sources\Panther, destination folder: C:\ProgramData\Microsoft\Diagnosis\ETLLogs 2025-02-12 20:22:48, Info Copy etl files: source: C:\$WINDOWS.~BT\Sources\Panther\DlTel-Merge.etl, destination: C:\ProgramData\Microsoft\Diagnosis\ETLLogs\DlTel-Merge.etl 2025-02-12 20:22:48, Info pCopyTelemetryFile: Wrote CV 3w/QApSOdUeYrZpO.31 to ETL C:\ProgramData\Microsoft\Diagnosis\ETLLogs\DlTel-Merge.etl:$ETLUNIQUECVDATA 2025-02-12 20:22:48, Info Copy etl files: source: C:\$WINDOWS.~BT\Sources\Panther\DlTel-Merge00001.etl, destination: C:\ProgramData\Microsoft\Diagnosis\ETLLogs\DlTel-Merge00001.etl 2025-02-12 20:22:48, Info pCopyTelemetryFile: Wrote CV 3w/QApSOdUeYrZpO.31 to ETL C:\ProgramData\Microsoft\Diagnosis\ETLLogs\DlTel-Merge00001.etl:$ETLUNIQUECVDATA 2025-02-12 20:22:48, Info Diagtrack service is running 2025-02-12 20:22:49, Info Successfully Forceuploaded the telemetry data. 2025-02-12 20:22:49, Info Upload files successfully so we can remove all etl files. 2025-02-12 20:22:49, Info SP Closing Panther Logging 2025-02-12 20:22:49, Info MOUPG MoSetupPlatform: Setup Platform object released! 2025-02-12 20:22:49, Info MOUPG Finalize: Leaving Execute Method 2025-02-12 20:22:49, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2004] 2025-02-12 20:22:49, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2003] 2025-02-12 20:22:49, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2001] 2025-02-12 20:22:49, Info MOUPG ProgressHandlerAction: Sending final progress message for action [0]. 2025-02-12 20:22:49, Info MOUPG ProgressHandlerAction FinalUpdate: 0x0, 0x0 / 0x0, 0x0 2025-02-12 20:22:49, Info MOUPG ProgressHandlerAction: Sending final progress message for action [0]. 2025-02-12 20:22:49, Info MOUPG ProgressHandlerAction FinalUpdate: 0x0, 0x0 / 0x0, 0x0 2025-02-12 20:22:49, Info MOUPG Signalling actions thread to shut down. 2025-02-12 20:22:49, Info MOUPG Waiting for actions thread to exit. 2025-02-12 20:22:49, Info MOUPG Actions thread has exited. 2025-02-12 20:22:49, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2004] 2025-02-12 20:22:49, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2000] 2025-02-12 20:22:49, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x3000] 2025-02-12 20:22:49, Info MOUPG DlpTask: Leaving Execute Method 2025-02-12 20:22:49, Info MOUPG SetupManager::ExecuteCustomScript: Type = [0x3] 2025-02-12 20:22:49, Info MOUPG SetupManager::ExecuteCustomScript: No scripts found. Finished type [0x3] 2025-02-12 20:22:49, Info MOUPG SetupNotify: Specifying extended data [0x50016] for error [0x8007042B]. 2025-02-12 20:22:49, Info MOUPG CSetupUIManager: Showing error message 2025-02-12 20:22:49, Info MOUPG CInstallUI::ShowErrorMessage: Posted MSG_INSTALLUI_SWITCH_TO_ERROR_PAGE 2025-02-12 20:22:49, Info MOUPG SetupHost: Reporting error event -> [0x8007042B, 0x50016] 2025-02-12 20:22:49, Info MOUPG CInstallUI::CInstallUIMessageWindow::SwitchToErrorPage 2025-02-12 20:22:49, Info MOUPG CInstallUI::SwitchToErrorPage 2025-02-12 20:22:49, Warning MOUPG SetupNotify::ReportEvent - Report ID or Event Reporter not available. 2025-02-12 20:22:49, Info MOUPG SetupManager: FailureCount = [15] 2025-02-12 20:22:49, Info MOUPG SetupManager: Requesting cleanup level [0x2] from parent process. 2025-02-12 20:22:49, Info MOUPG Setup phase change: [SetupPhaseError] -> [SetupPhaseUnpack] 2025-02-12 20:22:49, Info MOUPG SetupManager: Deleting task: [Prepare]... 2025-02-12 20:22:49, Info MOUPG SetupManager: Deleting task: [Install]... 2025-02-12 20:22:49, Info MOUPG SetupManager: Deleting task: [Exit]... 2025-02-12 20:22:49, Info MOUPG SetupManager: Found unpack task! Restarting layout action... 2025-02-12 20:22:49, Info MOUPG CInstallUI::ShowMessageBox: Showing MessageBox 2025-02-12 20:22:51, Error MOUPG CSetupManager::Execute(345): Result = 0x8007042B[gle=0x0000007f] 2025-02-12 20:22:51, Error MOUPG CSetupHost::Execute(517): Result = 0x8007042B[gle=0x0000007f] 2025-02-12 20:22:51, Info MOUPG SetupHost: Using Diagnostic tool: ["C:\$WINDOWS.~BT\Sources\SetupDiag.exe" /Scenario:Upgrade /ZipLogs:False /Format:xml /Output:C:\WINDOWS\logs\SetupDiag\SetupDiagResults.xml /RegPath:HKEY_LOCAL_MACHINE\SYSTEM\Setup\SetupDiag\Results] 2025-02-12 20:22:51, Info MOUPG SetupHost: Diagnostic results location: [C:\WINDOWS\logs\SetupDiag\SetupDiagResults.xml] 2025-02-12 20:22:51, Info MOUPG SetupHost: Diagnostic Analysis timeout value: [90000] ms 2025-02-12 20:22:51, Info MOUPG SetupHost: Diagnostic Analysis - START 2025-02-12 20:22:51, Info MOUPG CSetupDiagnostics: Tracing Data [TIME] -> [DiagnosticAnalysisStart]=[2025-02-12 20:22:51] [32103957-cdea-42f6-bd5b-fc4e2fec913b][5f87448e-104f-4cb2-b65f-fc45b2f4e597][][0x1] 2025-02-12 20:23:30, Info MOUPG SetupHost: Diagnostic tool execution result: [0x0] 2025-02-12 20:23:30, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [DiagnosticAnalysisResult]=[0x0] [32103957-cdea-42f6-bd5b-fc4e2fec913b][5f87448e-104f-4cb2-b65f-fc45b2f4e597][][0x1]
Also, when I check the target editions, it shows: "The current edition cannot be upgraded to any target editions." I have already converted it to Retail, but I'm still getting the same error. Your support is greatly appreciated.
Of course it'll say cannot be upgraded from 2022 to 2022. Change the registry values and try. All it'll do is say you can't upgrade if it fails. But I'm betting it'll will.