azure role not starting after windows update 10February

Question

After installation of windows update on 10th February 2016, the azure roles are not starting in emulator (Full/Express). The logs show below

[00005748:00006624, 2016/02/14, 12:03:24.391, FATAL] Role process exited with exit code of -2147024809
[00005748:00006624, 2016/02/14, 12:03:24.397, INFO ] Stopping role: deployment25(0).AzureCloudService2.WebRole1_IN_0. Notify: False  Recycle: False  StopTimeout: 30
[00005748:00006624, 2016/02/14, 12:03:24.398, IMPRT] State of deployment25(0).AzureCloudService2.WebRole1_IN_0 changed from RoleStateBusy to RoleStateStopping.
[00005748:00006624, 2016/02/14, 12:03:24.398, IMPRT] State of deployment25(0).AzureCloudService2.WebRole1_IN_0 changed from RoleStateStopping to RoleStateStopped.
[00005748:00006624, 2016/02/14, 12:03:24.398, ERROR] <- WapGetEnvironmentVariable=0x800700cb
[00005748:00006624, 2016/02/14, 12:03:24.398, WARN ] (Ignoring) Reading environment variable CleanupFirewallOnRoleRestart failed with HR: 800700cb
[00005748:00006624, 2016/02/14, 12:03:24.398, INFO ] The value of cleanupFirewallOnRoleRestart is set to True
[00005748:00006624, 2016/02/14, 12:03:24.398, WARN ] Attempting to recover role deployment25(0).AzureCloudService2.WebRole1_IN_0.
[00005748:00006624, 2016/02/14, 12:03:24.399, ERROR] Failed to create FSRM quota manager instance.

Update 14 Feb 2016

Looks like if i use full IIS (not IIS Express) and Full Emulator it works but if i select Express emulator (i can only select IISExpress) it does not*

Answer 1

As I have run into the same issue, I tried to uninstall the updates one by one and came down to the one causing the issue: KB3126593.

To verify, I installed all the updates again, except this one, emulator still started properly. After installing the problematic one, emulator stopped working, resumed after uninstalling it again.

I am using quite old Azure Tools v2.6, maybe this is fixed for the newer versions, cannot try this for myself unfortunately.

On my side, both Full and Express emulators were failing, both tried with IIS Express (not using full IIS).

Hope this helps!

Update 18 Feb 2016

I tried to contact Microsoft Azure Support to report this problem, also leading them to this StackOverflow question for more detailed information. They did not seem to care so much, because I don't have an appropriate paid support plan (quite frustrating). If there is anyone who would report this with a valid support plan, I am free to provide any info needed.

Update 22 Feb 2016

Microsoft Azure Support finally started to solve it, it has been reproduced and dispatched to the production team! The only workaround they presented is to use Full IIS in the meantime.