Skip to main content
N
Nikolay_Ch1-Visitor
1-Visitor
January 9, 2026
Question

Creo+ 13.1.0.1 crash related to "search_path" values containing space

  • January 9, 2026
  • 2 replies
  • 113 views

Hello, everyone

When adding the "search_path" option in the Configuration Editor, if the path contains spaces, Creo+ crashes with a “fatal error encountered”. The crash results in EXCEPTION_ACCESS_VIOLATION. The Creo-generated traceback log file is attached for reference.

Paths containing spaces are expected to be supported. This behavior worked correctly in Creo 7.0 and is consistent with PTC official documentation, where examples of "search_path" usage also include paths with spaces.

In our environment, removing spaces from folder names is not a viable workaround, as we are using corporate directories managed via OneDrive, and the space is part of the root-level folder name.

As a result, this issue causes significant difficulties when manually defining paths for multiple subassemblies (up to 10 in our case) and standard components. Since I work with multiple projects daily, repeatedly locating missing components is inefficient and negatively impacts productivity.

 

I would like to know:

  • Is this a known defect in Creo+ 13.1.0.1

  • Has PTC issued any hotfix, patch, or workaround for this issue?

  • Are there specific path or config restrictions that can prevent this crash?

 

Thank you for your guidance.

Best regards, Nikolay

2 replies

M
MartinHanak24-Ruby III
24-Ruby III
January 9, 2026

Hi,

tip no.1: Open Case at PTC Support

tip no.2: Enclose path into quotation marks

tip no.3: Use subst command to define "virtual path"

Eg.:

real path ... C:\Program Files\Internet Explorer

subst Q: "C:\Program Files\Internet Explorer"

... now Q:\ shows contents of C:\Program Files\Internet Explorer

 

    N
    Nikolay_Ch1-VisitorAuthor
    1-Visitor
    January 9, 2026

    Thank you, Martin.
    However, the second tip regarding quotation marks does not work — I tried it right away.
    The third tip is good, but it is also not entirely suitable. The point is that in this case the problem would remain for the rest of the team. This is more of a temporary workaround for one user, rather than a comprehensive solution.

    K
    KenFarley21-Topaz II
    21-Topaz II
    January 9, 2026

    Giving a traceback log here is useless, because we are users and those files mean nothing to us.

    If this is a problem other users of Creo+ 13 are experiencing, I would expect there would be a lot of messages here about it, but this is the first I've seen. Unless this version of Creo just came out , this likely means there's something not quite right with your setup. I've never seen an error in search path definitions trigger a fatal crash, it usually just means you don't get the paths defined. A silent fail, so to speak.

    If I were you I'd put in a support case with PTC and/or bring up the problem with the company that supplied you with your licenses for Creo.

     

    Terms & ConditionsCookie settingsAccessibility statement