Hi @Duncker, Leisa ,
While an official fix is not yet available, the issue can be bypassed by launching Edge with the following command line argument:
--disable-features=msEEPicl,msEEPiclProactive
Then, you should no longer be impacted by this issue.
If you still can't solve the issue with the solution above, please try:
- Make sure your Edge version is the latest 126.0.2592.61, or above.
- If you have met the version requirement but the issue persists, use the command line argument: --disable-renderer-accessibility
Note: For all command line argument configuration, all msedge.exe instances have to be closed (according to the named processes on the Task Manager > Details tab view) before attempting to launch a new instance with any custom command-line parameters.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Best Regards,
Shijie Li