Skip to main content
L
lulu950110-Marble
10-Marble
March 1, 2018
Solved

Creo 2.0 does not open

  • March 1, 2018
  • 2 replies
  • 7327 views

Hello,
I am a student and I have Créo 2.0 M130 with a valid student license.
Since some time, all Créo software do not open (even as administrator)
And there is nothing in the task manager

Some ideas?

Thank you

(Sorry for my English)

Best answer by lulu9501

Hello,


I solved my problem that came from windows
I reinstalled windows and creo and it works!


Thank you everybody !

 

Ludovic

2 replies

D
dschenken1-Visitor
1-Visitor
March 1, 2018

Perhaps this: https://community.ptc.com/t5/PTC-Academic-Program-Discussions/Renew-Creo-3-0-student-license/m-p/164830

    L
    lulu950110-MarbleAuthor
    10-Marble
    March 5, 2018

    Thank you for your answer dschenken

    It is'nt a license problem !

     

    Ludovic

    M
    Mahesh_Sharma22-Sapphire I
    22-Sapphire I
    March 1, 2018

    You mentioned nothing in task manager, still check for xtop under processes. If not, check xtop.exe in <Install _location>\Common Files\<Datecode>\x86e_win64\obj.

    Also check the size of file, sometimes Anti-virus application quarantines the executable. 

     

     

      L
      lulu950110-MarbleAuthor
      10-Marble
      March 5, 2018

      Hello,

       

      xtop.exe is not in the task manager, and when I try to execute it, there is a message saying that the application failed to start correctly (0xc000007b).

      Tank you

      Ludovic

      D
      dschenken1-Visitor
      1-Visitor
      March 7, 2018

      Something does happen. The OS tries to load and run the application and some part of the OS or the application fails. The problem is there are too many places for the process to fail to list all that might apply to your computer. If this was a common failure it would have been fixed. I'm guessing that this failure has occurred before any part of Creo is actually running, otherwise you would have mentioned the presence of log files that are typically created.

       

      You may have a better time with Stackoverflow, where diagnosing this type of problem is a more frequent activity.

       

      Here's a link to Stackoverflow questions already asked about that error:

      https://stackoverflow.com/search?q=0xc000007b ( the first result also suggests using dependencywalker utility, just like on the page I suggested before, and further that there is a mismatch in some dll type, which you will only find with dependency walker or some similar tool set such as the Windows Sysinternals utilities https://docs.microsoft.com/en-us/sysinternals/downloads/ )

      Terms & ConditionsCookie settingsAccessibility statement