Install DPM 2022 Remote Administration on Win 2025 VM passes Requirements check but fails during install

The error code 1603 during the installation of the DPM 2022 Remote Administration console typically indicates a general installation failure. Since you mentioned that the setup passes all requirements checks but fails later, here are a few suggestions that might help you troubleshoot the issue:

1. PowerShell Version: Ensure that the version of PowerShell installed on your Windows 2025 server is compatible with DPM 2022. Although it detects a supported version initially, there might be issues with the installation environment or PowerShell configuration.
2. Administrative Privileges: Make sure you are running the installation with administrative privileges. Right-click on the installer and select "Run as administrator".
3. Check for Existing Installations: If there are remnants of previous installations of DPM or other related software, they might interfere with the new installation. Ensure that any previous versions are completely uninstalled.
4. Log Files: Review the installation log files for more specific error messages that might indicate what went wrong. Look for entries around the time of the failure that could provide more context.
5. Compatibility Mode: Since Windows 2025 is technically not supported, consider running the installer in compatibility mode for an earlier version of Windows that is supported by DPM 2022.
6. Windows Updates: Ensure that your Windows 2025 server is fully updated. Sometimes, missing updates can lead to installation issues.

If these steps do not resolve the issue, consider reaching out to Microsoft support for further assistance, especially since you are attempting to install on an unsupported version.

References:

• Prepare your environment for System Center Data Protection Manager
• Get DPM installed

Hello WCW65,

As you noted, installing the DPM 2022 Remote Administration console on Windows Server 2025 is not officially supported, which is why the setup may fail even though the prerequisites check initially passes. The error 1603 is a generic Windows Installer error, but in this case the log entries about _detectmonad suggest that the installer is unable to validate the required PowerShell environment during the final stage.

To troubleshoot, I recommend confirming that the latest version of PowerShell is installed and available in the system path. Running the installer with elevated permissions and ensuring that all pending Windows updates are applied may also help. If the error persists, the most reliable option is to install the console on a supported operating system version (such as Windows Server 2022) and manage DPM remotely from there.

Since this scenario involves unsupported configuration, Microsoft Support would not provide a fix, but they can confirm whether future updates may extend compatibility. For now, using a supported OS for the console installation is the safest path forward.

If my answer is useful for you, please hit ACCEPT THE ANSWER to support me!!

Thank you so much!!

Best regards,

QQ.