Same here :-(

Haven't found a solution yet, rollback doesn't work for some reason either. So I'm not very happy currently. Working on a VM for now.

My event log has this error:

Faulting application name: iisexpress.exe, version: 10.0.14358.1000, time stamp: 0x574fb9e6
Faulting module name: IISUTIL2.dll, version: 10.0.14358.1000, time stamp: 0x574fba02
Exception code: 0xc0000005
Fault offset: 0x0000000000026d5e
Faulting process id: 0x2f7c
Faulting application start time: 0x01d34792db1bc678
Faulting application path: C:\Program Files\IIS Express\iisexpress.exe
Faulting module path: C:\Program Files\IIS Express\IISUTIL2.dll
Report Id: 4a20c658-682f-4e81-9b79-abb96368a3c1
Faulting package full name: 
Faulting package-relative application ID: 

This post also mentions there's no problems until a cookie is set, which corresponds with the behavior I'm seeing.

https://stackoverflow.com/questions/46785414/iisexpress-exe-started-crashing-with-access-violation-in-islocalrequest-call

Looks like it's been fixed for the next release :-)

https://developercommunity.visualstudio.com/content/problem/133462/iisexpress-crashes-on-build-17017-1400.html

I manged to roll back to 16299.15 and get back up and running...

Does seem that is was the cookie thing for me too, hopefully the corrupt component fix in the next preview solves iisexpress and iis!

Not too keen on iisexpress as seems to be something of an issue with viewport sizes not corresponding with Bootstrap breakpoints.. 767 kicks in around 844, same site running locally on the same box in iis 767 is where it kicks in.

FYI: I just received build 171020-1626 and I'm up and running again, IIS Express is fixed and this nasty issue which I also ran into after rebooting my machine last week is also fixed: https://www.hanselman.com/blog/RecoveringFromTheWindows10InsidersFast17017VolsnapsysRebootGSODBSOD.aspx

is working on a reply...