Skip to main content
S
23-Emerald III
StephenW23-Emerald III
23-Emerald III
March 18, 2026
Question

clearing .wf but lost window customization

  • March 18, 2026
  • 2 replies
  • 167 views

I needed to do a good cleanout, so I cleaned up all my workspaces then deleted my .wf folder. Not to  unusual but may be the first time since moving to creo 10 (late last year)  that I have done this.

I run config.pro option to load my ui customization from my run directory  -  load_ui_customization_run_dir yes

I was surprised that after deleting my .wf, I lost my settings even tho I had checked prior to deleting that the one in my startup directory customization ui file was dated recently, which i thought confirmed my location.

 

What did I miss?

2 replies

R
remy21-Topaz I
21-Topaz I
March 19, 2026

hi can you simplify and break down the steps to replicate your issue ?

S
23-Emerald III
StephenW23-Emerald IIIAuthor
23-Emerald III
March 19, 2026

@remy 

 

I have set in my config.pro the option  load_ui_customization_run_dir yes

Prior to deleting my .wf folder, I verified I had the file creo_parametric_customization.ui within my start in directory

I deleted un-needed workspaces (part of my needed "cleanup")

I deleted the .wf folder located in \AppData\Roaming\PTC\ProENGINEER\wildfire\Creo10WF\.wf

Upon re-opening  creo 10, my creo window settings (quick access toolbar, etc) was back to the default, out of the box state.

 

K
21-Topaz I
kdirth21-Topaz I
21-Topaz I
March 19, 2026

Just got to say the first thing done wrong was to delete the folder.  Always rename it to retain it then delete when you have everything working. 😁

S
23-Emerald III
StephenW23-Emerald IIIAuthor
23-Emerald III
March 19, 2026

LOL, you know, I typically do that. Actually, your comment reminded me that when I checked, I had the .wf from when we upgraded creo versions late last year that I had renamed, which at that point i deleted that one.

BUT, I've done this tons of times, after the first 100 or so, I learned about the config setting. I don't remember having this problem in a good while.

Terms & ConditionsCookie settingsAccessibility statement