Skip to main content
M
Mat16-Pearl
16-Pearl
August 11, 2016
Solved

Creo 3 M100 - Windows 10 unstable

  • August 11, 2016
  • 3 replies
  • 7046 views

Hi there,

I am struggling with Windows 10 (and therefore IE11) and Creo.

Using PDM Essentials through the embedded browser is like a minefield. Any user action (no matter, if activating a workspace or browsing common space) can cause Creo to stop.

Strangly enough, when Creo stopped responding to any input and I try to close it via right-click on Creo Symbol in taskbar -> "Close Window", Creo asks for confirmation instantly. But the dialog does not respond to any click.

I already tried "browser_limit_to_ie9_mode yes", but no success.

Does anyone have similar problems in this combination (Windows 10 & Creo 3 M100)?

    Best answer by Mat

    the bug seems to be resolved with version M140.

     

     

    3 replies

    M
    Mat16-PearlAuthor
    16-Pearl
    August 12, 2016

    I narrowed the problem to a script sequence of the browser's homepage.

    There are two lines, that do not work together:

    window.open("<weblink tool collection>.html", "", "width=1100, height=720");
    

    document.location.href = "http://<company windchill site>";

    I downgraded to Creo 3 M080 (last Version installed on my old Win7 system).

    Now, everything seems to run stable.

    So, seems like there is a bug in M100.

    M
    Mat16-PearlAuthor
    16-Pearl
    October 11, 2016

    I marked this thread as "unanswered" because the problem is still not fixed in M110.

    And keeping stuck in one Software version seems not quite being a solution.

    M
    MartinHanak24-Ruby III
    24-Ruby III
    October 11, 2016

    Hi,

    did you report the problem to PTC Support ?

    MH

    M
    mdebower18-Opal
    18-Opal
    October 11, 2016

    Have you tried setting the config option:

    windows_browser_type CHROMIUM_BROWSER

    We are on Creo 3.0 m100 and Windchill 10.1 m040 and that is what we had to do to get it to behave.

    M
    Mat16-PearlAuthor
    16-Pearl
    October 12, 2016

    Hi Marc,

    sure, I could try this, but my site uses weblink API, which is based on ActiveX (IE only).

    Meanwhile, I have got an answer from my reseller.

    PTC is already aware of the problem. A fix should be available with M120.

    https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS244548

    R
    RandyJones20-Turquoise
    20-Turquoise
    October 12, 2016

    Matthias Rehs wrote:

    Hi Marc,

    sure, I could try this, but my site uses weblink API, which is based on ActiveX (IE only).

    Actually weblink works good with the Chromium based embedded web browser.

    M
    Mat16-PearlAuthorAnswer
    16-Pearl
    August 1, 2017

    the bug seems to be resolved with version M140.

     

     

    Terms & ConditionsCookie settingsAccessibility statement