Skip to main content
5-Regular Member
Oct 29, 2026 9:38 PM UTC
Solved

Creo Parametric not loading config.pro from Login directory

I’ve been following this Creo documentation article about how Creo Parametric loads config files on startup.

I wanted to have Creo load a custom user specific config.pro file that, according to the doc, should be stored in the user’s Login directory, described to be the home directory for my login ID. In this case, I placed it in C:\Users\<current_login_id>\config.pro

However, Creo Parametric would not load my config.pro file in any of the following locations:

  • C:\Users\<current_login_id>\
  • C:\Users\<current_login_id>\OneDrive\
  • from HOME env variable set to C:\Users\<current_login_id>\

Any help as to how to load a config.pro file from a user specific directory? I can’t just add the config option to one of the config.pro files in the C:\ drive because this is on a shared virtual desktop environment with multiple other users.

MikeBennett
17-Peridot
Nov 4, 2026 12:35 PM UTC

Hi @LS_10938759,

 

The documentation states that HOME is used, not HOMEPATH.  Have you attempted to load a config.pro from what is shown as your HOME location, C:\Creo?

12 replies

tbraxton
22-Sapphire II
Oct 29, 2026 10:13 PM UTC

How and where (which directory) Creo is launched matter in this context. I don’t think you have provided enough information to troubleshoot this. As a quick test determine what directory Creo is starting in when launched and then place your config.pro file in this directory. This may resolve your issue.

If you are using a network administered by an organization talk to the admin that owns the Creo install if you are still having problems troubleshooting this.

 

You can get some insight into what is being loaded by looking at the file(s) listed in the options UI as shown below.

 

 

Translate
21-Topaz I
Nov 2, 2026 8:22 AM UTC

Hi 
to add to ​@tbraxton the reference article from Tech Support is the following : https://www.ptc.com/en/support/article/CS28227

but it means you would use a location that Creo is designed with in the first place.
From your request you are looking for have Creo target a location of your choice. 
one way to check the HOME env var is to fire the prompt from Creo’s environment and check that it actually exists then.
if it is not there, one way to force it is to append the psf file.

Translate
5-Regular Member
Nov 3, 2026 4:36 PM UTC

Thank you both for your responses.

According to the articles, it looks like I should be able to create a HOME env variable and place my custom config.pro file at that path, but Creo is still not reading it upon launch.

For example, I created the HOME env variable in my root user profile path: 
 

and placed my config.pro file in C:\Users\LSun10, and it fails to read it. It only reads the default system level config files:
 

It just seems that the articles are stating a functionality that does not actually work as intended, but if I am doing something wrong, please let me know.

 

Translate
MikeBennett
17-Peridot
Nov 3, 2026 7:18 PM UTC

Hi ​@LS_10938759,

 

The articles and Help Center are correct.

 

Expanding on ​@remy’s suggestion to confirm HOME is defined and read by Creo, use Home > Utilities > Open System Window (or activate it from the command search tool)  Entering into the cmd.exe set home will respond with any variables from Creo’s context containing home.

 

My other thought is that perhaps the config.pro file is incorrect or has a bad name.  I’m thinking like file extensions are hidden in File Explorer so what looks like config.pro may be config.pro.pro or config.pro.txt

Translate
5-Regular Member
Nov 3, 2026 10:26 PM UTC

The config.pro file has the correct extension (no hidden extension at the end) and just one line in the file “enable_auto_regen no” to test setting a variable, so I don’t think that’s the problem.

 

Running the “set home” command returns the following variables:
 

My assumption was that Creo reads in any config.pro file located in the HOMEPATH location, but that doesn’t happen.

Translate
tbraxton
22-Sapphire II
Nov 3, 2026 5:53 PM UTC

Does your environment require that you access Creo through a network (networked drives?) or is everything running local on your computer? If you are working in a networked system that you don’t control, then you should consult an administrator.

As a quick test set Creo up to start in a specific directory you create to test. Try to change the start in directory if you have control of the installation and executable required to launch Creo. Using a newly created directory, place your config in that location and then start Creo to see if it reads the config.pro. This does not require manual setting of any environment variables.

 

 

Translate
5-Regular Member
Nov 3, 2026 10:28 PM UTC

I’m accessing Creo locally in a VM.

The quick test that you mentioned does work; I was able to load in a config.pro file that’s located in whatever “Start in” path I set in the shortcut. However, this isn’t ideal, since our users all share the VM and we’d like everyone to be able to load their own custom config.pro file specific to their user profile.

Translate
21-Topaz I
Nov 6, 2026 8:57 AM UTC

Then a workaround would consist in creating as many shortcuts as users / custom config.pro.

Translate