Showing results for 
Search instead for 
Did you mean: 
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Stay updated on what is happening on the PTC Community by subscribing to PTC Community Announcements. X

Installation NIGHTMARE


Installation NIGHTMARE

It just keeps getting better and better.....

First the History lesson.

1. Two weeks ago I used the "Upgrade" option from to update from M050 to M100. Only to find out, instead of an overwrite of M050 with M100, I got M100 files only and it did not remove and replace M050. Even though M100 was pulled down from, Creo was still launching M050. Lived with it until I had time to deal with it.

2. For a couple weeks I asked question on the exploder why the upgrade did what it did. I received a couple suggestions about changing date codes, psf files, etc.... why should


Instead of using the PTC upgrade or uninstall, try this:

* Rename your current PTC/Creo folder to something else
* Do a fresh install of M100

That way you
* don't need to wait for uninstall / upgrade
* have an easy rollback if needed (simply rename the folder back to how
it was names before you started).

Don't worry too much about registry settings or stuff like that; Creo
is still very portable, i.e. independent of registry settings.

Also: make sure you have already downloaded the installation media
before starting. That way you won't rely on internet connection
stability of your provider and the PTC site.

Part of your problem is probably that System Restore is something that
belongs to Microsoft Windows. It has nothing to do with PTC software.
(I'm surprised it brought back your PTC folder at all).

I agree it should all be easier, but unfortunately Creo is a fancy high
end CAD system and that has historically been an excuse for complicated
installation and setup. Hopefully PTC will fix this soon, because one
day this excuse will no longer be accepted. (Your email is clear
evidence of that).

Best regards,
Patrick Asselman

There was a bug in early versions of Creo 2 what would not allow you to uninstall. This might be your problem.

* SPR 2123373
- Uninstall doesn't work
- Work around
* Delete pimuninstall.exe from:
* Go to <load point=">\Parametric\Bin
Remove the Read Only property from uninstall.exe
* Uninstall program from Control Panel
- Script to do this:
attrib -R "%USERPROFILE%\AppData\Local\Temp\pimuninstall.exe"
del %USERPROFILE%\AppData\Local\Temp\pimuninstall.exe
attrib -R "C:\ptc\Creo 2.0\Parametric\bin\uninstall.exe"

Adjust the path to your environment. Appwiz.cpl brings up the add/remove programs wizard.

Also in Creo, you can script the uninstall process from the command line. I've found that the best way to install a new version. There were problems like you describe in the first several releases of Creo 2.0. Don't remember which version this actually got fixed on. See the attached pdf for details.

David Haigh

One other issue you may have.

* Changing software configuration
- Reconfigure licensing for new .psf & .bat files
* <loadpoint>\Parametric\bin\reconfigure.exe
* <loadpoint>\Simulate\bin\reconfigure.exe

* Reconfigure looks at the registry!
- Registry path must match location of reconfigure
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PTC\Creo Parametric\2.0\2012060]
"DisplayName"="Creo Parametric"
"InstallLocation"="C:\\ptc\\Creo 2.0\\Parametric"
"InstallDir"="C:\\ptc\\Creo 2.0\\Parametric"
"InstallSource"="E:\\Creo Parametric 2.0\\F000"
"CommonFilesLocation"="C:\\ptc\\Creo 2.0\\Common Files\\F000"

- Save some .reg files to change this easily

The paths in red must match the reconfigure you are running.

I came across this issue because on one of our networks I have a centralized install of Creo on a network drive. After testing that out I couldn't reconfigure the software that was installed on my local machine.

David Haigh

Latest Update....and maybe no surprise to the SysAdmins,

Started a case with PTC and had some attention to this issuethis morning. I am at a 50% solution at the moment. The weirdness with multiple installs,inability to uninstall and crossed executablesis still a PITA and separtate.


It turns out my graphics card, while not on the aproved list(it did run M050 fine with no issues) cannot run Creo2 past M080 without OpenGL being disabled. This was apparently the primary issue for the M100 hang. The PTC AE created a temporary startup pointing to M100 with OpenGL diabled. It works but I am nervous to run forward with it setup like this. I need to make a decision to either 1. run M080 with OpenGL enabled...2. run higher builds with OpenGL disabled....or 3. buy a new machine with an approved graphics card (more $$$$) in prep for late Creo2 builds and Creo3 coming soon to a theater near you.

Top Tags