Let us help you tackle any Software issues and optimize your accounting workflow. 

Sage 50 crashes when saving transactions

How to Fix Sage 50 Terminal Server Install Mode Errors During Remote Installation

Installing or upgrading Sage 50 through a Remote Desktop Connection can sometimes stop with the message “Failed to switch Terminal Server to INSTALL mode.” The installer may ask you to switch the mode manually before continuing. If you are connected to a Windows Server through Remote Desktop, you might try the suggested command but receive another message stating that install mode does not apply to a Remote Desktop Session Host configured for remote administration.

This error can be confusing because Sage 50 may not actually require you to change the server’s operating mode. According to Sage’s troubleshooting guidance, the problem can occur because Windows Remote Desktop does not recognize the installer’s automatic run function. Instead of launching the main installation package again or repeatedly attempting to switch modes, the recommended solution is to locate the extracted installation files and run the internal _setup.exe file directly with administrator privileges.

This guide explains how to fix the Sage 50 Failed to Switch Terminal Server to Install Mode error when installing or upgrading through Remote Desktop. It covers the correct installation file, where to find it, how to use the Windows Temp folder, how to access network installation files, and what to check if the direct installer method does not work. The instructions focus on Sage 50 U.S. Edition’s documented installation procedures.

Why Does Sage 50 Fail to Switch Terminal Server to Install Mode?

Sage 50 displays this message when its installation package attempts to use an automatic Windows Terminal Server mode-switching function that is not recognized in the current Remote Desktop environment.

Windows Server provides installation and execution modes for certain Remote Desktop Services application-installation scenarios. Traditionally, administrators could use commands such as change user /install before installing an application and change user /execute afterward. However, these commands are not appropriate for every Remote Desktop Session Host configuration.

Sage’s specific troubleshooting article identifies the cause of this error as Windows Remote Desktop not recognizing the installer’s auto-run function. Its recommended resolution is to bypass that automatic launch process and run _setup.exe directly from the extracted Sage 50 installation files.

Common situations that trigger the error:

SituationWhy the error may appearRecommended approach
Installing Sage 50 through RDPThe automatic installer function is not recognizedRun the extracted _setup.exe directly
Upgrading Sage 50 on Windows ServerThe upgrade package encounters the same Remote Desktop behaviorLocate the upgrade’s internal installer
Installing from a downloaded packageThe downloaded executable launches an extraction process before setupOpen the extracted Peachw\Install folder
Installing from Windows TempThe extracted files are stored in a temporary directoryLocate the appropriate RarSFX folder
Installing through a network setupThe installation files are stored in the server’s program pathOpen the PeachtreeInstaller folder if it exists
Using a Remote Desktop Session Host for remote administrationThe server may not support the traditional install-mode command in its current configurationAvoid forcing the mode change and use Sage’s direct installer procedure

The error does not necessarily indicate that Sage 50 is incompatible with Windows Server or that the installation package is damaged. First, determine how the installer was launched and whether the extracted installation files are available.

How to Fix Sage 50 Failed to Switch Terminal Server to Install Mode?

The most important troubleshooting step is to bypass the automatic installer launch and run Sage 50’s internal _setup.exe file. Sage documents several locations where this file may be stored, depending on how the installation package was downloaded or prepared.

Before proceeding, sign in to the server using an account with administrator privileges. Close unnecessary applications and make sure no other user is performing an installation or upgrade on the same server.

1. Run the Extracted Sage 50 _setup.exe File Directly

This is Sage’s primary documented solution for the Failed to Switch Terminal Server to INSTALL mode error. When you download Sage 50, the initial installer extracts the installation files into a folder. Running the original downloaded package through Remote Desktop may trigger the automatic mode-switching error. Launching the internal _setup.exe bypasses that problematic step.

Follow these steps:

  1. Open File Explorer on the Windows Server.
  2. Navigate to the Sage installation folder. The default extraction location is generally C:\Sage.
  3. Open the folder corresponding to your Sage 50 release, such as Sage50_2026.
  4. Open the Peachw folder.
  5. Open the Install folder.
  6. Locate _setup.exe.
  7. Right-click _setup.exe and select Run as administrator.
  8. Follow the installation wizard to complete the installation or upgrade.

The folder structure will generally resemble:

C:\Sage

   └── Sage50_2026

       └── Peachw

           └── Install

               └── _setup.exe

The release-specific folder name may differ depending on the Sage 50 version and downloaded package. Use the actual extracted folder on your server rather than copying the example path without checking it.

Important: Run the internal _setup.exe, not the original downloaded extraction executable. If you cannot find the extracted folder, use the Windows Temp folder method below.

2. Locate Sage 50 _setup.exe in the Windows Temp Folder

If Sage 50 was downloaded or updated through the program and the extracted files are not available in the expected C:\Sage location, they may be stored in the current Windows user’s temporary folder. Sage’s official instructions specifically describe locating the installer inside a RarSFX folder.

To find the installation file:

  1. Press Windows + R on the server.
  2. Enter %temp% in the Run box.
  3. Press Enter.
  4. Find the folder named RarSFX0.
  5. If that folder is unavailable, look for the RarSFX folder with the highest number.
  6. Open the folder.
  7. Open Peachw.
  8. Open Install.
  9. Locate _setup.exe.
  10. Right-click the file and select Run as administrator.

The typical folder structure is:

%temp%

   └── RarSFX0

       └── Peachw

           └── Install

               └── _setup.exe

If multiple RarSFX folders exist, do not automatically select an older folder. Choose the folder associated with the installation package you most recently downloaded or extracted. Check the contents and timestamps where necessary.

If the expected installation files are no longer present, download a fresh Sage 50 installer and allow it to extract the files. Then return to the extracted Peachw\Install directory and run _setup.exe directly.

3. Run _setup.exe from the Sage 50 Network Installation Folder

If Sage 50 was originally installed using a network installation, the server may contain a separate folder holding the installation files. Sage documents this location as another way to launch the internal installer. This option applies only when the corresponding network installation folder exists. It should not be assumed to be available on every server.

To use the network installation files:

  1. Sign in to the server with an authorized administrator account.
  2. Locate the Sage 50 program path.
  3. Find the PeachtreeInstaller20XX folder, replacing 20XX with the applicable release-year folder name.
  4. Open the Peachw folder.
  5. Open the Install folder.
  6. Locate _setup.exe.
  7. Right-click the file and select Run as administrator.
  8. Follow the installation wizard.

The folder structure may resemble:

Sage Program Path

   └── PeachtreeInstaller2026

       └── Peachw

           └── Install

               └── _setup.exe

If the PeachtreeInstaller folder does not exist, your original installation may not have used the network installation method. In that case, use the extracted download folder or Windows Temp folder instead. Do not create a new PeachtreeInstaller folder manually or copy files into an arbitrary location to imitate this structure. Use the installation files prepared by the Sage installer.

4. Download a Fresh Sage 50 Installation Package

If _setup.exe is missing, the extracted folder is incomplete, or the available installation files do not correspond to the release you want to install, download a fresh copy of Sage 50. Sage’s troubleshooting instructions recommend downloading a new installer when the existing installation files are unavailable or cannot be used.

Follow these steps:

  1. Confirm the Sage 50 edition and release you need.
  2. Obtain the installer through the official Sage 50 U.S. Edition download portal.
  3. Save the downloaded file to the server.
  4. Run the downloaded package to extract its installation files.
  5. Open the extraction destination, usually under C:\Sage.
  6. Navigate to the release folder.
  7. Open Peachw\Install.
  8. Right-click _setup.exe and select Run as administrator.

If the downloaded package extracts to a different location, use that location instead of assuming the default path. A fresh download is particularly useful when the previous extraction was interrupted or the required installer file cannot be located. However, downloading the package again will not resolve a Remote Desktop auto-run issue if you continue launching the original executable. The essential step remains running the internal _setup.exe.

5. Install Sage 50 Using the Correct Remote Desktop Procedure

Sage’s network installation instructions specifically address installations performed through a Remote Desktop Connection or virtual machine. They direct users to locate the extracted installation files through the Windows Temp folder and run _setup.exe with administrator privileges. This is important when installing Sage 50 on a hosted Windows Server or a virtual machine accessed remotely.

Use this procedure:

  1. Establish a Remote Desktop Connection to the server.
  2. Sign in using an account authorized to install Sage 50.
  3. Open the Windows Run dialog with Windows + R.
  4. Enter %temp%.
  5. Open the appropriate RarSFX folder.
  6. Navigate through Peachw and then Install.
  7. Right-click _setup.exe.
  8. Select Run as administrator.
  9. Complete the Sage 50 installation wizard.

Do not assume that a remote installation must begin by running change user /install. Sage’s error-specific instructions provide the direct _setup.exe method to bypass the automatic mode-switching problem. If you are installing on a cloud-hosted Windows Server, such as an AWS EC2 Windows instance, the same distinction is important: the fact that you are connected through RDP does not mean you should force an unsupported mode change. Follow the applicable Sage installation procedure for the server’s configuration.

6. Confirm That You Are Using the Correct Installation Files for an Upgrade

The error can also appear when upgrading an existing Sage 50 installation through Remote Desktop. In this situation, the upgrade package may extract its files successfully but fail when the automatic installation process attempts to start. Use the internal installer belonging to the specific upgrade package you downloaded.

To avoid using the wrong installer:

  1. Confirm the Sage 50 release currently installed on the server.
  2. Confirm the release you intend to install.
  3. Locate the extracted files for that upgrade package.
  4. Open its Peachw\Install folder.
  5. Run the corresponding _setup.exe as administrator.
  6. Follow the upgrade instructions and wait for the installation to finish.
  7. Verify the installed release before allowing users to open the company in the upgraded version.

Do not run _setup.exe from an older RarSFX folder or a different Sage release simply because it is easier to find. The installer must match the update or upgrade you intend to apply.

Also, remember that opening a company in a newer Sage 50 release may convert its data to the newer format. Sage’s upgrade guidance warns that data converted for a newer release may not remain compatible with the previous release. Maintain a current backup and confirm your rollback requirements before proceeding.

Why Does “Install Mode Does Not Apply to Remote Desktop Session Host” Appear?

A related message may appear when you try to run the command:

change user /install

Windows may respond that install mode does not apply to a Remote Desktop Session Host configured for remote administration. This does not necessarily indicate a problem with Sage 50. The command is associated with a particular Terminal Services application-installation workflow. A server configured for remote administration may not support that mode-switching operation.

Sage’s specific troubleshooting instructions for the failed-switch error recommend running _setup.exe directly instead of repeatedly attempting the automatic mode change.

It is important to distinguish two situations:

  • Sage 50 installation through a Remote Desktop connection: Use the extracted _setup.exe method described in the troubleshooting steps above.
  • A genuine Terminal Server application-installation configuration: Follow the Windows Server installation workflow appropriate to that server configuration. Sage documents both a graphical installation method and a command-line method for Terminal Server mode.

For an environment that genuinely requires Terminal Server installation mode, Sage documents the following command-line sequence:

change user /install

After the application installation:

change user /execute

The graphical alternative is the Windows Install Application on Remote Desktop Server option, where available. Do not use these commands as a blanket fix for the original Sage 50 error. First establish whether the server actually requires Terminal Server installation mode. If it is configured for remote administration and Windows rejects the command, use Sage’s direct installer procedure instead.

How to Verify That Sage 50 Installed Successfully?

After the installer finishes, verify the application before allowing other users to access the upgraded environment.

A. Check the Sage 50 release

  1. Open Sage 50 on the server.
  2. Select Help > About Sage 50 Accounting.
  3. Review the displayed product and release information.
  4. Confirm that it matches the version you intended to install.

If the release has not changed after an upgrade, do not assume that the installation completed successfully just because the wizard closed.

B. Test the company data

Open the appropriate company using the normal Sage 50 login procedure. Confirm that the company opens without an installation or version-related error.

If the company is being upgraded to a newer release, allow the required data conversion to complete. Use a current backup if recovery becomes necessary.

C. Check workstation access

If Sage 50 is installed on a server for network access, verify that the relevant workstations can open the application and access the shared company data.

Follow Sage’s network installation instructions for updating workstations. Do not assume that a successful server installation automatically completes every workstation update.

How to Prevent Sage 50 Terminal Server Installation Errors?

A consistent installation process can help prevent the same error during future upgrades and software installations.

  1. Keep the extracted installation files available: After downloading Sage 50, confirm where the installer extracts its files. Knowing the location of the Peachw\Install folder makes it easier to run _setup.exe directly if the automatic installation process fails.
  2. Use an administrator account: Make sure the Windows account used for installation has the necessary administrative privileges. If your organization manages server permissions centrally, arrange for an authorized administrator to perform the installation.
  3. Follow the correct Remote Desktop installation procedure: When installing through RDP, use Sage’s documented procedure for locating and launching the internal installer. Avoid repeatedly running the original extraction package if it triggers the Terminal Server mode error.
  4. Confirm the Sage 50 release before upgrading: Keep a record of the currently installed release and the version you plan to install. Use the correct installer for that upgrade, and avoid selecting an older extracted installation package.
  5. Back up company data before upgrading: Create and verify a current company data backup before major upgrades or changes to the Sage 50 server installation. This provides a recovery option if an unrelated issue occurs during the upgrade.
  6. Test the server before reconnecting users: After installation, open Sage 50, verify the release, and test access to the company data. Then check the workstations that use the shared installation and follow any required workstation update instructions.

Conclusion

The Sage 50 Failed to Switch Terminal Server to Install Mode error commonly occurs because Windows Remote Desktop does not recognize the automatic run function used by the installation package. It does not necessarily mean that Sage 50 is incompatible with Windows Server or that the entire installation is damaged.

The most important solution is to locate the extracted Sage 50 installation files, open the Peachw\Install folder, and run _setup.exe directly as administrator. Depending on how the package was downloaded, the files may be located under C:\Sage, inside a Windows Temp RarSFX folder, or in the server’s PeachtreeInstaller directory.

If the installation still fails, confirm that you are using the correct release, have the required Windows permissions, and are following the appropriate Remote Desktop installation procedure. Avoid forcing Terminal Server mode changes when the server is configured for remote administration and Windows does not support that operation.

Following Sage’s documented installation procedure helps avoid unnecessary configuration changes and makes Sage 50 installations and upgrades more reliable on Windows Server environments.

FAQs of Sage 50 Failed to Switch Terminal Server to Install Mode:

How do I fix Sage 50 Failed to Switch Terminal Server to Install Mode?

Locate the extracted Sage 50 installation files, open the Peachw\Install folder, and right-click _setup.exe. Select Run as administrator and follow the installation wizard. Sage recommends this method because Windows Remote Desktop may not recognize the installer’s automatic run function.

Where can I find Sage 50 _setup.exe?

The file is generally available in one of three locations, depending on the installation method:
C:\Sage\Sage50_[Version]\Peachw\Install
%temp%\RarSFX0\Peachw\Install
The PeachtreeInstaller20XX\Peachw\Install folder in the Sage program path, if the original installation used the network installation method.
The folder name may vary by release and extraction location.

Why does Windows say Install Mode does not apply to Remote Desktop Session Host?

This message can appear when the server is configured for remote administration and does not support the traditional Terminal Server installation-mode command in that configuration. For the specific Sage 50 failed-switch error, use the extracted _setup.exe file directly instead of repeatedly running change user /install.

How do I install Sage 50 through Remote Desktop Connection?

Connect to the Windows Server, sign in with an authorized administrator account, and locate the extracted Sage 50 installation files. Open the Peachw\Install folder, right-click _setup.exe, and select Run as administrator. Complete the installation wizard and verify the installed release afterward.

Can I install Sage 50 on an AWS EC2 Windows Server through RDP?

Yes, Sage 50 can be installed on supported Windows Server or virtual-machine environments when the applicable product and system requirements are met. When using Remote Desktop, Sage’s documented procedure is to locate the extracted installation files and run _setup.exe as administrator. Confirm that the Windows Server configuration and Sage 50 release meet the applicable requirements.

What should I do if Sage 50 _setup.exe is missing?

Check the extracted installation directory under C:\Sage, the current user’s %temp% folder, and the PeachtreeInstaller program-path folder if it exists. If the installation files cannot be found, download a fresh Sage 50 installation package and allow it to extract. Then locate Peachw\Install\_setup.exe and run it as administrator.

Does the Sage 50 Terminal Server Install Mode error affect company data?

The failed mode-switch message itself does not indicate that company data has been damaged. It relates to the installation process. However, an upgrade can involve changes to the company data format when the company is opened in a newer release. Maintain a current backup before upgrading and verify company access after installation.

Related Articles