How to uninstall a premise 2019 exchange that will not complete installation

Question

How to uninstall a premise 2019 exchange that will not complete installation

Mike Johnson 20

I have tried many times to remove an unwanted installation of Exchange 2019 causing problems in migration on a physical 2022 server. It cannot finish install or removal successfully. I have lots of logs and can't seem to figure it out. I have done it from the control panel as well as the elevated command line. Has anyone else managed to fight through this? I really need to make it go away, as It is causing problems in AD, DNS and the migration. It always says that the last installation didn't complete and it will continue it, but the last instance didn't make it past set 1 of 16 stopping services, sometimes it even goes all the way through and says it completes installation, but even after reboot, I cannot perform the uninstall. HELP Needed. MJ

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Mike Johnson 20 Reputation points

2025-05-06T20:02:25.2733333+00:00
G:>setup.exe /mode:uninstall

Microsoft Exchange Server 2019 Cumulative Update 13 Unattended Setup

Languages

Management tools

Mailbox role: Transport service

Mailbox role: Client Access service

Mailbox role: Mailbox service

Mailbox role: Front End Transport service

Mailbox role: Client Access Front End service

Performing Microsoft Exchange Server Prerequisite Check

Configuring Prerequisites COMPLETED Prerequisite Analysis 100%

MAPI over HTTP, the preferred Outlook desktop client connectivity with Exchange server, is currently not enabled. Consider enabling it using: Set-OrganizationConfig

-MapiHttpEnabled $true

For more information, visit: https://learn.microsoft.com/Exchange/plan-and-deploy/deployment-ref/ms-exch-setupreadiness-WarnMapiHttpNotEnabled?view=exchserver-2019

Configuring Microsoft Exchange Server

Preparing Setup COMPLETED Stopping Services 100%

The following error was generated when "$error.Clear();

& $RoleBinPath\ServiceControl.ps1 -Operation:DisableServices

-Roles:($RoleRoles.Replace('Role','').Split(',')) -SetupScriptsDirectory:$RoleBinPath;

& $RoleBinPath\ServiceControl.ps1 -Operation:Stop

-Roles:($RoleRoles.Replace('Role','').Split(',')) -IsDatacenter:([bool]$RoleIsDatacenter)

" was run: "System.Management.Automation.CommandNotFoundException: The term

'C:\Program Files\Microsoft\Exchange Server\V15\Bin\ManageScheduledTask.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program.

Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

at

System.Management.Automation.CommandDiscovery.LookupCommandInfo(String commandName, CommandTypes commandTypes, SearchResolutionOptions searchResolutionOptions,

CommandOrigin commandOrigin, ExecutionContext context)

at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String commandName, CommandOrigin

commandOrigin, Nullable`1 useLocalScope)

at System.Management.Automation.ExecutionContext.CreateCommand(String command, Boolean dotSource)

at

System.Management.Automation.PipelineOps.AddCommand(PipelineProcessor pipe, CommandParameterInternal[] commandElements, CommandBaseAst commandBaseAst,

CommandRedirection[] redirections, ExecutionContext context)

at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput,

CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)

at

System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)

at

System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)".

The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
Mike Johnson 20 Reputation points

2025-05-06T20:28:17.67+00:00

That's weird, I just copied the Command Prompt Dialog box.
Anonymous

2025-05-09T03:57:06.11+00:00

Hi Mike Johnson,

Just checking in to see if below information was helpful. If you have any further updates on this issue, please feel free to post back. If you think my reply is helpful to you, please remember to mark it as an answer. Warm thanks
Anonymous

2025-05-13T02:48:20.9866667+00:00

Hi Mike Johnson,

Is there any update on this thread? If the issue has been resolved, please mark the helpful replies as answers, this will make answer searching in the forum easier and be beneficial to other community members as well. Thanks for your understanding.
Mike Johnson 20 Reputation points

2025-05-13T12:52:06.3066667+00:00

I have engaged Microsoft Professional services with their $500 per incident cost. The Senior Engineer is still working Her way through it. So I don't feel bad that I wasn't sorting it out myself.

Accepted answer

0 additional answers

Your answer

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Mike Johnson 20 Reputation points

2025-05-06T20:28:17.67+00:00

That's weird, I just copied the Command Prompt Dialog box.
Anonymous

2025-05-09T03:57:06.11+00:00

Hi Mike Johnson,

Just checking in to see if below information was helpful. If you have any further updates on this issue, please feel free to post back. If you think my reply is helpful to you, please remember to mark it as an answer. Warm thanks
Anonymous

2025-05-13T02:48:20.9866667+00:00

Hi Mike Johnson,

Is there any update on this thread? If the issue has been resolved, please mark the helpful replies as answers, this will make answer searching in the forum easier and be beneficial to other community members as well. Thanks for your understanding.
Mike Johnson 20 Reputation points

2025-05-13T12:52:06.3066667+00:00

I have engaged Microsoft Professional services with their $500 per incident cost. The Senior Engineer is still working Her way through it. So I don't feel bad that I wasn't sorting it out myself.

Answer 1

Hi Mike Johnson,

Thank you for posting your question in the Microsoft Q&A forum.

Please check if the file ManageScheduledTask.ps1 exists under C:\Program Files\Microsoft\Exchange Server\V15\Bin.

If not, please try copying both the "ManageScheduledTask.ps1" and "ManageScheduledTask.Strings.psd1" files from the scripts folder (C:\Program Files\Microsoft\Exchange Server\V15\Scripts) to the Bin folder (C:\Program Files\Microsoft\Exchange Server\V15\Bin). Then use “setup.exe /mode:uninstall” command to uninstall again.

Also, if you have any third-party scan tool or software on current Exchange server, please remember to uninstall them to avoid any other interference.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Share via

How to uninstall a premise 2019 exchange that will not complete installation

0 additional answers

Your answer