Forum Discussion
Ya this happened to us this morning, from the 113 Edge upgrade (Following what happened last week with Chrome, this must be some chromium based update that messes with NameMapping and how it hooks onto the browser through the Object Browser)
What has worked for me and my team has been disabling Edge from auto updating (Had problems doing the MS Policy add for this, just disabled both services edgeupdate and edgeupdatem)
Go grab a MSI of the previous stable release from 112
https://www.microsoft.com/en-us/edge/business/download?form=MA13FJ
Once you download this, open an admin cmd prompt, navigate to the directory that has this MSI, and run the downgrade
msiexec /I MicrosoftEdgeEnterpriseX64.msi /qn ALLOWDOWNGRADE=1
Reopen Edge, will say its pending, give it a few mins and restart the browser, should show 112.x
Then try your TC scripts again.