Network Status
Microsoft Edge & WebView2 Errors - Resolution in Progress
Last Update: 10/11/26 22:13
Affects: Managed IT
We are currently aware of issues affecting Microsoft Edge along with other applications which use WebView including Teams and Outlook. This is caused by a bad patch released by Microsoft which corrupts Microsoft Edge and requires a reinstallation.
We are working fast to automatically identify affected devices and remotely deploy a fix. This will not require any interaction from you.
Whilst you are welcome to call us to have the fix deployed via the phone, please be aware that the impact of this issue is widespread and we are receiving an exceptionally high number of calls at present.
Please distribute this information within your organisation as this will only be sent to primary razorblue contacts.
Update - 10/11/26 11:28
Investigations into the ongoing issues for Edge and WebView2 are still underway.
We are currently in the testing stage for an automated fix to be deployed to all affected devices, no ETA is currently available.
Further updates will follow once testing is completed and wider deployment begins.
Please distribute this information within your organisation as this will only be sent to primary razorblue contacts.
Update - 10/11/26 13:53
Testing of an automated remediation script has been completed and has been shown to resolve the issues as needed.
Deployment of this fix is now entering it's initial stages, as further confirmation of successful deployments are received we will continue to wide our scope to ensure all devices are updated in a timely manner.
We are also monitoring the rollout to ensure any failures are captured and actioned accordingly.
Update - 10/11/26 15:00
We are beginning a wider deployment of the fix for the Edge/WebView2 error currently being experienced by multiple users.
During the remediation process, users may receive several pop-ups advising that services are being stopped. Certain applications, including Edge, may also be temporarily unavailable while the fix is applied. Please can users be advised not to reboot devices during this process as this can cause the remediation to fail.
The process is currently taking approximately 10–15 minutes per device and, based on testing and deployments completed so far, is resolving the reported issues as expected.
We will continue to monitor the deployment and provide further updates as required.
Update - 10/11/26 22:13
Our engineering colleagues are continuing deployment and monitoring of remediation activities across all devices we have identified as impacted that are currently online and available for remote remediation.
Where devices are not currently online, and therefore can't be addressed at this moment, we are working to schedule automated remediation actions to run as soon as the device becomes available. Beyond leaving devices powered on and connected where possible, this should not require direct involvement of the end user.
We will continue to monitor the deployment and provide further updates as required.