Skip to main content
4-Participant
January 27, 2023
Solved

Creo File version mismatching installed Student Edition

  • January 27, 2023
  • 2 replies
  • 1777 views

Hello,

 

I have been having problems with my Creo 9 (Student Edition) installation.

When I try to open the Surface Finish Gallery or the Hatching Configurator I keep getting the warning that the corresponding file "was created with a commercial version of Creo Parametric and is not compatible with the Creo Parametric Student Edition (for educational use only) you are running." after which the program shuts down completely.
I am sure this problem extends beyond the mentioned configuration files.

A re-installation of Creo did not fix this (neither did a second one).

There has not been any other version of Creo installed on my computer, nor have I uses any other license apart from the Student license I am currently using.
Is there a way to fix this problem?
Is it even wise to use the most recent version of Creo or are previous versions generally more stable?

 

Thanks in advance for any input.

 

Best answer by Alex_Cazacu

Hello,

 

Sadly these files that used to be in a neutral format got changed and your student edition can't open commercial files.

Simple solution is to simply run setup.exe again and choose reconfigure existing software. Use this product code: 

BE900908EDSTUDENTEDK12

and finish the reconfiguration process. This should fix this issue.

 

Thanks,

Alex

2 replies

24-Ruby III
January 27, 2023

@Alex_Cazacu 

please can you verify reported problem ?

4-Participant
January 27, 2023

image.png

24-Ruby III
January 27, 2023

Hi,

please be patient. I hope Alex will respond soon.

17-Peridot
February 9, 2023

Hello,

 

Sadly these files that used to be in a neutral format got changed and your student edition can't open commercial files.

Simple solution is to simply run setup.exe again and choose reconfigure existing software. Use this product code: 

BE900908EDSTUDENTEDK12

and finish the reconfiguration process. This should fix this issue.

 

Thanks,

Alex

4-Participant
February 15, 2023

Hello,

the problem seems to be resolved as far as I can see.

Thanks, Konrad