INFO: Windows 10 Creators Update interrupts E-Prime’s ability to detect refresh rate [25326]

Follow

Comments

4 comments

  • Avatar
    David McFarlane

    Does the Fall 2017 Creators Update (version 1709) fix this for E-Prime 2?  Thanks.

  • Avatar
    David McFarlane

    Good news from Devon Struthers at PST Support:

    "We have done timing tests on the Fall Creators Update as well as having spoken to Microsoft at length about the original issue with Windows 10 Creators Update and can verify that the problem introduced in Windows 10 Creators Update has, in fact, been solved in Windows 10 Fall Creators Update. Windows 10 Fall Creators Update will solve the issue completely for E-Prime 2.0 as well as those users who choose not to update their version of E-Prime 3.0 to E-Prime 3.0 Update 1."

  • Avatar
    Mia Borzello

    I'm getting this error on Windows 7- what should I do?

  • Avatar
    An Longfei

    Win10 1803 also fixed this problem. Good news from Chris Kincak at PST Support:

    " I can confirm that E-Prime 2.0 can be run on Windows 10 Spring Creators/April 2018 Update without generating the "unable to detect a valid refresh rate." The issue was originally due to changes made to the Windows Display Manager in the Fall Creators Update. In addition to our own solutions (the workaround script for E-Prime 2.0 and E-Prime 3.0 Update 1), Microsoft actually worked with us and countless others to address the issue on their end. They successfully implemented their solution in the Fall Creators Update and we have confirmed this functionality is also restored in the Spring Creators Update (both on the Insider's Preview edition and the official update roll-out as of just this morning)."

Please sign in to leave a comment.

Powered by Zendesk