Skip to main content
Participant
February 22, 2018
Question

Control Flow Guard

  • February 22, 2018
  • 1 reply
  • 1411 views

Starting with Windows 10, version 1703, when some users launch IE with Flash enabled, it crashes when interacting with a website that uses flash (i.e. abcnews.go.com) (see error message below).  After working with Microsoft, the issue is caused by Control Flow Guard (on Windows 10).  We are running the latest release of Flash (February 2018, as provided by Microsoft).  Error Pop-up = "Adobe Flash Player Utility has stopped working"  with Close the Program or Debug the Program as clickable options.

It appears to be compatibility issue with CFG.  Has Adobe seen this error and is there planned resolution for it?

    This topic has been closed for replies.

    1 reply

    jeromiec83223024
    Inspiring
    February 23, 2018

    It's a crash, and something we'd be happy to look into.  I need much more specific information to do the engineering work required.

    Here's a guide on providing a crash dump:

    Report a Flash Player crash or error

    As an aside, I would not describe this as a "compatibility issue with control flow guard".  Think of CFG like the airbags in your car.  It's protecting against an inappropriate write to memory.  You can't drive the car after the airbags are deployed because they obscure the windshield, but their job isn't to be compatible with driving.  In a similar vein, they're a symptom, not the problem, much like a telephone pole in the car analogy.  A crash dump is basically the black box in a car, and will tell me what events led up to the crash.

    Thanks!

    Participant
    February 27, 2018

    Thank you for the reply from Friday.  On Monday 2/26, we did create and submit a Bug ID: FP-4198779, which also included a zip file and multiple dump files.  At any point soon, can we engage a living, breathing Adobe contact to work with us, either over the phone or E-Mails?  Thank you!

    Participating Frequently
    February 27, 2018

    We have the same issue.  Not sure what it is that is causing it.  I do know that if I disable my computer GPO the problem goes away.  As soon as I put the GPO back it starts up again.  There has to be a setting in the GPO that is causing this but for the life of me I cannot find it.