Exchange Server setup fails with error code 1619 if it's started from PowerShell by using Setup.exe

Applies to: Exchange Server


Consider the following scenario:
  • You plan to run an unattended setup to upgrade to Microsoft Exchange Server from PowerShell by using Setup.exe.
  • The setup media is located on D drive.
  • The unattended installation is started from PowerShell as "d:\setup.exe" instead of "d:\.\setup.exe."

In this situation, the installation process doesn't set up from the local folder. Instead, the process goes on searching for possible locations where it can find the Setup.exe file, and then starts the file from the first location. The setup process finally fails at the language pack file installation, as it's looking at a wrong source for the language pack. Additionally, you receive the following error message:

[DateTime] [1] [ERROR] Couldn't open package 'C:\Program Files\Microsoft\Exchange Server\VersionNumber\bin\Setup\ServerRoles\UnifiedMessaging\'. This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.


If you use PowerShell, the setup must be started as .\setup.exe.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


Learn about the terminology that Microsoft uses to describe software updates.