- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
10-10-2025 02:09 AM
Hi,
We are using the latest version of CyberArk PSM and are trying to install it into a 😧 location and as it stands the install is default to installing to C:\ and not adding any config into the C:\.
Is there a limitation PSM can only be installed on C:\?
Thanks for any ifnormation.
10-10-2025 02:15 AM
Hi @Stephen Clarke There is no limitation on installation drive.
10-10-2025 02:15 AM
Hi @Stephen Clarke There is no limitation on installation drive.
10-10-2025 02:21 AM
Ok, with that in mind and despite us putting a different location d:... in the various *Config.xml stage files we still end up with what looks like a PSM install in C:Progra*... and nothing into the directory we have requested in install config files?
Outcome result seems to ignore file locations in config files.
We are currently testing the install via standard setup.exe to see if that yields a different outcome versus the PowerShell automation route.
10-12-2025 04:48 PM
Hello @Stephen Clarke
I hope you changed PSM folder location during installation.
10-12-2025 04:48 PM
Hello @Stephen Clarke
I hope you changed PSM folder location during installation.
10-12-2025 04:53 PM
@Stephen Clarke You can install in D drive, when you run the installation wizard, please ensure that while performing manual installation using setup.exe wizard, all the steps requiring drives, you mentioned as D drive.
During Hardening/app locker script, you need to verify that its showing D drive once you have finished installation in D drive. There may be some instances where you need to change the drive letters manually from C drive path to D drive path.
10-12-2025 04:53 PM
@Stephen Clarke You can install in D drive, when you run the installation wizard, please ensure that while performing manual installation using setup.exe wizard, all the steps requiring drives, you mentioned as D drive.
During Hardening/app locker script, you need to verify that its showing D drive once you have finished installation in D drive. There may be some instances where you need to change the drive letters manually from C drive path to D drive path.
10-13-2025 12:58 AM
To date the only way we have found to enable a D:\ install is via the standard steup.exe and specifying the appropriate drive in the manual install, the automated scripts seem to want to install to C:\ irrespective of the definitions in the various config files within the execute stages.
We never got to the hardening stage just the installation step.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

