What’s odd is that I know I had WebView2 installed at some point already because it had like nine instances running while Edge was off. Oh ko! An error string that is searchable? I can work with that. Shortly after I put the PC into its new home, I remoted into the box and said “ah, lemme try Widgets now” and lo! I get an error message: Given how I planned to use this machine, I shrugged and turned off the Widgets and Chat buttons on the taskbar and continued the rest of my installs. Additionally, I’ve been running on Windows 11 for a long, long time and have never seen this issue before (and we’re talking ~300 clean installs over a period of 18 months) which left me perplexed. Most of the reports online were calling out issues from the pre-release versions but most of it didn’t apply to the released builds of Windows. There was never an error message or anything in the Event Log calling out the issue – it just didn’t work. Chat would sometimes open with a “We ran into an issue” or just ignore the click entirely.Widgets did not open when I clicked on the button: the icon would animate and then restore itself.

On a recent clean install of Windows 11 on a brand-new machine, I ran into an issue with two core parts of the Windows 11 experience:

Microsoft edge webview2 runtime install