Forum Discussion
AnthonyB_AUS
Mar 10, 2021Brass Contributor
90.0.818.0 or March monthly updates - Edge processes spawning and crashing. Can no longer open Edge.
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 launch...
- Mar 11, 2021Carbon Black Cloud: MS Edge Failure to launch after 89.0.774.48 updateEnvironment
- 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
CauseThere was a change in the behavior of the latest version of Microsoft EdgeResolutionAs 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 NotesEnterprise EDR only orgs will not be affected with this issueRelated Contenthttps://community.carbonblack.com/t5/Knowledge-Base/Carbon-Black-Cloud-What-are-the-differences-between-API-Bypass/ta-p/75758
https://community.carbonblack.com/t5/Knowledge-Base/Carbon-Black-Cloud-MS-Edge-Failure-to-launch-after-89-0-774-48/ta-p/101461#U101461 - Carbon Black Cloud Sensor: All Supported Versions
AnthonyB_AUS
Mar 10, 2021Brass Contributor
Totally agree.
VRStudio
Mar 11, 2021Copper Contributor
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
https://community.carbonblack.com/t5/Knowledge-Base/Carbon-Black-Cloud-What-are-the-differences-between-API-Bypass/ta-p/75758
https://community.carbonblack.com/t5/Knowledge-Base/Carbon-Black-Cloud-MS-Edge-Failure-to-launch-after-89-0-774-48/ta-p/101461#U101461
https://community.carbonblack.com/t5/Knowledge-Base/Carbon-Black-Cloud-MS-Edge-Failure-to-launch-after-89-0-774-48/ta-p/101461#U101461