Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FatalExecutionEngineError after Windows 10 Anniversary Update #1766

Closed
dmarklein opened this issue Sep 22, 2016 · 4 comments
Closed

FatalExecutionEngineError after Windows 10 Anniversary Update #1766

dmarklein opened this issue Sep 22, 2016 · 4 comments

Comments

@dmarklein
Copy link

After installing the Windows 10 Anniversary Update (and re-installing IIS, since the update removed it), we are unable to run our local development websites in IIS 10.

Now, whenever we attempt to access on our local dev websites through a browser, we see the following:
screen shot 2016-09-22 at 11 14 17 am

In the event log, we see corresponding errors like the following:

Log Name: Application
Source: Application Error
Date: 9/22/16 10:57:46 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DANIELKLEIN232E
Description:
Faulting application name: w3wp.exe, version: 10.0.14393.0, time stamp: 0x57899b8a
Faulting module name: clr.dll, version: 4.6.1586.0, time stamp: 0x575a1507
Exception code: 0xc0000005
Fault offset: 0x0000000000099a99
Faulting process id: 0x1270
Faulting application start time: 0x01d214ea0ede0a43
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 2b14898a-5bcc-4fb6-a8aa-8fa9fe16f6d2
Faulting package full name:
Faulting package-relative application ID:
Event Xml:

Furthermore, I have debugged one of the web sites -- watching in the debugger, we make it through the Application_Start just fine, but then immediately thereafter the exception is thrown. We originally thought this was related to #1583, so we tried installing/repairing .NET Core as well as repairing VS2015, to no avail.

We are at a complete loss -- any help and/or a workaround would be greatly appreciated. Until then, we are all going to roll back to prior to the Anniversary update.

@pranavkm
Copy link
Contributor

watching in the debugger, we make it through the Application_Start just fine

Is this a WebForms\ Mvc 5 application?

@dmarklein
Copy link
Author

dmarklein commented Sep 22, 2016

Yes -- our sites use WebForms and MVC5 in conjunction.

@pranavkm
Copy link
Contributor

@DamianEdwards where should we track this issue?

@DamianEdwards
Copy link
Member

Adding @csharpfritz

Bugs in .NET Framework and ASP.NET can be reported via MS Connect. Business support is via MS Support and community support (aka free support) is available on the ASP.NET Forums.

See .NET Platform Support for more details.

ryanbrandenburg pushed a commit that referenced this issue Nov 27, 2018
…1766)

- Change websockets and the POST end point to send data unbuffered.
- Update tests to handle partial frames
@dotnet dotnet locked as resolved and limited conversation to collaborators Dec 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants