SOLVED

90.0.818.0 or March monthly updates - Edge processes spawning and crashing. Can no longer open Edge.

%3CLINGO-SUB%20id%3D%22lingo-sub-2198104%22%20slang%3D%22en-US%22%3E90.0.818.0%20or%20March%20monthly%20updates%20-%20Edge%20processes%20spawning%20and%20crashing.%20Can%20no%20longer%20open%20Edge.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2198104%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20not%20sure%20whether%20the%20trigger%20was%20the%20Edge%20Dev%26nbsp%3B90.0.818.0%20update%20release%2C%20or%2C%20the%20March%20Security%20Updates%2C%20but%20on%20multiple%20Dell%20laptops%20I'm%20now%20seeing%20identical%20behaviour%3A%3C%2FP%3E%3CUL%3E%3CLI%3EWithout%20actually%20launching%20Edge%2C%20Microsoft%20Edge%20processes%20spawning%20and%20crashing%20constantly.%20This%20can%20continue%20for%205-7%20mins%20before%20eventually%20giving%20up%20and%20then%20there%20are%20no%20Microsoft%20Edge%20processes%20loaded.%3C%2FLI%3E%3CLI%3EAttempting%20to%20launch%20Edge%20Dev%20or%20Edge%20Release%20(89.0.774.48)%20triggers%20the%20above%20process%20all%20over%20again.%3C%2FLI%3E%3C%2FUL%3E%3CP%3EI've%20tried%3A%3C%2FP%3E%3COL%3E%3CLI%3Emultiple%20reboots%3C%2FLI%3E%3CLI%3Euninstalling%20Edge%20Dev%3C%2FLI%3E%3CLI%3ESFC%20%2Fscannow%3C%2FLI%3E%3CLI%3EDISM%20with%20a%20bunch%20of%20parameters%3C%2FLI%3E%3CLI%3ETried%20to%20go%20into%20Apps%20%26gt%3B%20Microsoft%20Edge%20%26gt%3B%20modify%20but%20it%20just%20triggers%20the%20above%20symptoms%20again%3C%2FLI%3E%3C%2FOL%3E%3CP%3EThe%20March%20Security%20Update%20listed%20is%26nbsp%3BMarch%209%2C%202021%E2%80%94%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Ftopic%2Fmarch-9-2021-kb5000802-os-builds-19041-867-and-19042-867-63552d64-fe44-4132-8813-ef56d3626e14%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3EKB5000802%3C%2FA%3E%20(OS%20Builds%2019041.867%20and%2019042.867)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20laptops%20both%20have%20%3CSTRONG%3ECarbon%20Black%20Cloud%20Sensor%2064-bit%203.6.0.1979%3C%2FSTRONG%3E%20as%20the%20anti-malware.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EUninstalling%26nbsp%3BCarbon%20Black%20Cloud%20Sensor%2064-bit%20resolved%20the%20issue.%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EJust%20wanted%20to%20share%20the%20results%20of%20my%20lost%202%20hours%20of%20productivity%20this%20morning!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2198802%22%20slang%3D%22en-US%22%3ERe%3A%2090.0.818.0%20or%20March%20monthly%20updates%20-%20Edge%20processes%20spawning%20and%20crashing.%20Can%20no%20longer%20open%20E%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2198802%22%20slang%3D%22en-US%22%3EThanks%20for%20sharing%20the%20solution%2C%20that's%20important%20to%20know.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2199164%22%20slang%3D%22en-US%22%3ERe%3A%2090.0.818.0%20or%20March%20monthly%20updates%20-%20Edge%20processes%20spawning%20and%20crashing.%20Can%20no%20longer%20open%20E%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2199164%22%20slang%3D%22en-US%22%3E%3CP%3Ehad%20e%20same%20issue%2C%20couldn't%20uninstall%20it%20or%20roll%20it%20back.%20the%20only%20way%20that%20i%20succeeded%20to%20uninstall%20was%20(please%20don%60t%20laugh)%20with%20portable%20ccleaner.%3CBR%20%2F%3EAfter%20restart%20OC%20did%204%20forced%20restarts%20by%20it%20self%20without%20any%20prompt%20(a%20minute%20announcement)%20and%20than%20it%20started%20working%20back%20again%F0%9F%A4%B7%F0%9F%8F%BB%E2%80%8D%3Adizzy_face%3A%3CBR%20%2F%3EAlso%20have%20the%20CarbonBlack%20but%20it%20is%20not%20an%20option%20for%20to%20remove%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

I'm not sure whether the trigger was the Edge Dev 90.0.818.0 update release, or, the March Security Updates, but on multiple Dell laptops I'm now seeing identical behaviour:

  • Without actually launching Edge, Microsoft Edge processes spawning and crashing constantly. This can continue for 5-7 mins before eventually giving up and then there are no Microsoft Edge processes loaded.
  • Attempting to launch Edge Dev or Edge Release (89.0.774.48) triggers the above process all over again.

I've tried:

  1. multiple reboots
  2. uninstalling Edge Dev
  3. SFC /scannow
  4. DISM with a bunch of parameters
  5. Tried to go into Apps > Microsoft Edge > modify but it just triggers the above symptoms again

The March Security Update listed is March 9, 2021—KB5000802 (OS Builds 19041.867 and 19042.867)

 

The laptops both have Carbon Black Cloud Sensor 64-bit 3.6.0.1979 as the anti-malware.

 

Uninstalling Carbon Black Cloud Sensor 64-bit resolved the issue.

Just wanted to share the results of my lost 2 hours of productivity this morning!

5 Replies
Thanks for sharing the solution, that's important to know.

had e same issue, couldn't uninstall it or roll it back. the only way that i succeeded to uninstall was (please don`t laugh) with portable ccleaner.
After restart OC did 4 forced restarts by it self without any prompt (a minute announcement) and than it started working back again🤷🏻‍:dizzy_face:
Also have the CarbonBlack but it is not an option for to remove it.

Lots of 3rd party software out there corrupting Windows and its programs, getting users stuck scratching their head to figure out what's wrong.
Windows Defender is good on its own for personal use, enterprises and businesses have the ability to use Windows Defender Advanced Threat Protection and other high-end features.
https://www.microsoft.com/en-gb/microsoft-365/enterprise-mobility-security/compare-plans-and-pricing

best response confirmed by AnthonyB_AUS (Occasional Contributor)
Solution

@AnthonyB_AUS 

Carbon Black Cloud: MS Edge Failure to launch after 89.0.774.48 update 
Environment
  • Carbon Black Cloud Sensor: All Supported Versions
    • Endpoint Standard (was CB Defense)
  • Microsoft Windows: All Supported Versions
  • Microsoft Edge browser: v89.0.774.48

Symptoms
  • Updating MS Edge to 89.0.774.48
  • CPU Maxed out
  • Edge will not launch
  • Multiple Edge attempts to relaunch visible in task manager

Cause
There was a change in the behavior of the latest version of Microsoft Edge

Resolution
As of 9:55 PM EST on March 09, our Engineering team resolved the issue with the recent Microsoft Edge update by pushing the necessary changes to all production environments.  As of this time, it is safe to remove any bypass rules that were created in the interim.

Additional Notes
Enterprise EDR only orgs will not be affected with this issue

Related Content