Unfortunately, with this update they propagated this error 0x8000405 that was not happening in 22621.160.
Now it happens on every build that was updated after 6/13/2022. 😜😜
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
Unfortunately, with this update they propagated this error 0x8000405 that was not happening in 22621.160.
Now it happens on every build that was updated after 6/13/2022. 😜😜
thanks CK and will try to install it tonight.
Well it looks like I'm stuck with 22621.290 --- It changed to 22622 later in the day