TestComplete issues with Chrome 113

I want to provide an update to my experience on this issue. Google has issued a third release of Chrome 113. The latest version is now 113.0.5672.127. Some people on my team were having issues with Chrome 113 (all subversions) being very slow. This turned out to be due to our browsers being partially managed by our organization, which caused the 113 update / installation to not complete properly. If, however, we rebooted our machines right after doing the Chrome update, this seem to cause the update to be completed, and Chrome 113 started working properly after that. So, we have been able to update from Chrome 112 to Chrome 113 successfully. The original Chrome 113 issue with TestComplete (TC not being able to find the browser at all) does appear to be fixed by the latest Chrome 113 update, which is what others have already reported.

However, there does seem to be some other TC 15.51 issues that predated the initial Chrome 113 release. The biggest one for us is in another post in this forum.

Re: The tested window (or control) has been delete... - SmartBear Community

This issue has not yet been addressed for us, and we are still unable to update to TC 15.51 because of it. It does seem to be unrelated to the Chrome 113 issue, as we also experience that issue with Chrome 112.

However, that issue is keeping us from accessing fixes in TC 15.51 to other interoperability issues with Chrome 113, such as dropdown lists not working, so it will still be an issue for us until SmartBear puts out a TC 15.51 update that we can actually use.