none
IE11 installation from WSUS - crashes immediately and repeatedly RRS feed

  • Question

  • After importing IE11 into WSUS and rolling it out to our workstations, Internet Explorer crashes immediately on all workstations that have been upgraded to IE11. Our WSUS does not keep updates locally, and all workstations download directly from Microsoft.

    When opening, the user can close the app, but then it keeps prompting.

    All workstations log the following two events;

    Faulting application name: IEXPLORE.EXE, version: 11.0.9600.16428, time stamp: 0x525b664cFaulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000Exception code: 0xc0000005Fault offset: 0x00000000Faulting process id: 0x1a14Faulting application start time: 0x01cf3111555b3916Faulting application path: C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXEFaulting module path: unknownReport Id: 93136ae6-9d04-11e3-8916-00dbdf11c280


    Fault bucket , type 0Event Name: BEXResponse: Not availableCab Id: 0Problem signature:P1: IEXPLORE.EXEP2: 11.0.9600.16428P3: 525b664cP4: StackHash_a7aaP5: 0.0.0.0P6: 00000000P7: 00000000P8: c0000005P9: 00000008P10: Attached files:Analysis symbol: Rechecking for solution: 0Report Id: 93136ae6-9d04-11e3-8916-00dbdf11c280Report Status: 0

    To work around this, I have to run a system restore on the workstation.

    Any previously updated workstations exhibit the same crash even if they are manually updated after a system restore.

    Monday, February 24, 2014 4:17 AM

Answers

    When booting into safe mode - the web browser starts and runs OK.

    That's your clue that whatever is causing the crashes is in your Startup list.  So now use selective startup changes, e.g. via msconfig.exe to identify a culprit.  Tip: you may also look at the list of loaded modules at a crash prompt for clues.  E.g. use ResMon or ProcExp to help with that.  So, if there is an intersection between those two lists, they would be good candidates for testing to avoid first.   ; )



    Robert Aldwinckle
    ---

    Tuesday, February 25, 2014 12:22 AM
    Answerer

All replies

  • A bit more information;

    • When booting into safe mode - the web browser starts and runs OK.
    • Performing a reset in Internet Control Panel has no effect.
      Running without Add-Ons has no effect.
      On one workstation I was able to get a tab to open, and it said on the tab;

    "Windows Data Execution Prevention detected an add-on trying to use system memory incorrectly. This can be caused by a malfunction or a malicious add-on"

    • When viewing task manager to end the cycle of crashes, there are two IExplorer.exe executables running - *32 and x64 versions (even though I only opened the x64 .EXE)
    Monday, February 24, 2014 4:34 AM

    When booting into safe mode - the web browser starts and runs OK.

    That's your clue that whatever is causing the crashes is in your Startup list.  So now use selective startup changes, e.g. via msconfig.exe to identify a culprit.  Tip: you may also look at the list of loaded modules at a crash prompt for clues.  E.g. use ResMon or ProcExp to help with that.  So, if there is an intersection between those two lists, they would be good candidates for testing to avoid first.   ; )



    Robert Aldwinckle
    ---

    Tuesday, February 25, 2014 12:22 AM
    Answerer