Unable to start Powershell Terminal since latest update

Hello,

Thank you for reaching out with this question. We’re not currently aware of a general issue with the PowerShell terminal in RDM 2025.3.27.0, but we’ll need a bit more information to investigate further.
Could you please confirm:

• Which version of RDM you were using before updating to 2025.3.27.0
• Which PowerShell is being used (Windows PowerShell or PowerShell 7)
• How the PowerShell terminal is being launched (embedded terminal in RDM or external)
• What data source RDM is connected to (e.g. local, SQL Server, Devolutions Server, etc.)
• Whether this occurs for all users or only specific users
• Whether this happens for all endpoints when opening a PowerShell terminal, or only specific endpoints
• If any error message appears briefly before the terminal closes

These details help us to better understand what’s happening.
Thank you.
Elevate your learning - Join the Devolutions Academy !
Kind regards,
Kelly

• Which version of RDM you were using before updating to 2025.3.27.0 => Version 2025.2.5.0
• Which PowerShell is being used (Windows PowerShell or PowerShell 7) => Both version 5 and 7 are not working
• How the PowerShell terminal is being launched (embedded terminal in RDM or external) => all default settings
• What data source RDM is connected to (e.g. local, SQL Server, Devolutions Server, etc.) => Devolutions Server
• Whether this occurs for all users or only specific users => All users
• Whether this happens for all endpoints when opening a PowerShell terminal, or only specific endpoints => it's local powershell so no endpoints configured
• If any error message appears briefly before the terminal closes => Unable to execute the application

Thank you for the detailed answers.
To help clarify the scope of this issue, I’ve tested the PowerShell Terminal (Local) entry in the following environments:

• DVLS 2025.2.21.0 with RDM 2025.2.30.0
• DVLS 2025.3.12.0 with RDM 2025.3.28.0

In both cases, I was able to create a new PowerShell Terminal (Local) entry (without configuring a host/endpoint), open the terminal, and run commands successfully.
To better understand what may be different in your environment, could you please help confirm the following:

1. Can Windows PowerShell 5 be launched normally outside of RDM on the affected machine (for example, from the Start menu)?
2. Is PowerShell 7 installed locally, and if so, is it installed for all users?
3. Can PowerShell 7 be launched successfully outside of RDM?
4. If you create a new PowerShell Terminal (Local) entry in RDM (rather than using an existing entry created prior to the update), does the behavior change?
5. When the terminal closes, do you see any relevant messages in:
6. the entry logs for the PowerShell terminal entry
7. the Devolutions Server data source logs
8. or the Windows Event Viewer (Application or Security logs)?

These checks should help determine the scope of the issue. Based on the results, we can then decide if additional logs are required for further investigation.

Thank you for your patience.

Elevate your learning - Join the Devolutions Academy !
Kind regards,
Kelly

1. Can Windows PowerShell 5 be launched normally outside of RDM on the affected machine (for example, from the Start menu)? => Yes
2. Is PowerShell 7 installed locally, and if so, is it installed for all users? => Yes
3. Can PowerShell 7 be launched successfully outside of RDM? => Yes
4. If you create a new PowerShell Terminal (Local) entry in RDM (rather than using an existing entry created prior to the update), does the behavior change? No, also not working with a complete new entry
5. When the terminal closes, do you see any relevant messages in: No
6. the entry logs for the PowerShell terminal entry: No
7. the Devolutions Server data source logs: No
8. or the Windows Event Viewer (Application or Security logs)? Application eventlog gives an error:

Naam van toepassing met fout: WindowsTerminal.exe, versie: 1.20.11271.0, tijdstempel: 0x6661c6ae
Naam van module met fout: ucrtbase.dll, versie: 10.0.22621.3593, tijdstempel: 0x10c46e71
Uitzonderingscode: 0xc0000409
Foutmarge: 0x000000000007e008
Id van proces met fout: 0x0x670C
Starttijd van toepassing met fout: 0x0x1DC7F03CB70EAD6
Pad naar toepassing met fout: C:\SnapVolumesTemp\MountPoints\{000028E1-0000-0000-0000-100000000000}\{67b427fa-1c9f-4745-8959-27e3b775d322}\SVROOT\Program Files\Devolutions\Remote Desktop Manager\runtimes\win-x64\native\wt\WindowsTerminal.exe
Pad naar module met fout: C:\WINDOWS\System32\ucrtbase.dll
Rapport-id: 9ba220a2-531b-4520-b885-e8c64354eee2
Volledige pakketnaam met fout:
Relatieve toepassings-id van pakket met fout:

Thanks for sharing the Event Viewer entry.
The event shows an Application Error involving WindowsTerminal.exe, with the fault occurring in ucrtbase.dll (Microsoft Universal C Runtime) and exception code 0xc0000409. This indicates a runtime-level failure rather than a PowerShell script error.
One detail that stands out is the execution path shown in the event:
C:\SnapVolumesTemp\MountPoints\...

This is an unexpected execution path compared to a typical local installation.
To help clarify what’s happening, could you please confirm:

1. Whether you’ve tried repairing or reinstalling the Microsoft Visual C++ Redistributables on the affected system
2. Whether any users are running Remote Desktop Manager from a standard local installation path, and if so, whether they see the same behavior or different errors
3. The exact Windows version and build in use

@hjbos Do you have Microsoft PowerToys installed by chance? There is a known issue with Windows Terminal, I just ran into this issue and updating the version 0.96 fixed the crashes for me.

https://github.com/microsoft/terminal/issues/19482

We don't use PowerToys. It looks like there is something wrong in the image we use (we use VDI).

Hello,

Thank you for mentioning VDI in your response and thanks again for sharing the Event Viewer entry. The event shows an Application Error involving WindowsTerminal.exe, with the fault occurring in ucrtbase.dll. This indicates a runtime level failure. One detail that causes concern is the execution path, which is listed as C:\SnapVolumesTemp\MountPoints\...
There is some concern that RDM may not be managing this path.
Are you familiar with the Portable RDM version? Would it be possible to set up this RDM portable version in a regular file system path on such a host to see if it performs any differently?
https://docs.devolutions.net/rdm/kb/how-to-articles/portable-rdm-installation/

Elevate your learning - Join the Devolutions Academy !
Kind regards,
Kelly