Forum Discussion
So far, the only method I've had ANY success with for stopping Chrome auto-update, is to delete it's "Update" folder.
See here: http://community.smartbear.com/t5/Functional-Web-Testing/Chrome-v-44/m-p/102713#U102713
But even that is no longer working in my VM. Although it has held up on my physical PC (just checked). No idea why it's holding on one and not the other.
And if you get an offline installer, be careful when you install with it. The first thing it does when the install completes is goes to the "About" page and looks for updates. So kill Chrome as soon as it starts after the offline installer completes.
I'm also curious why you want to go back to 45 from 46? My VM is running TC11.11 and works just as well with Chrome v46 as it did with v45?
First, thanks for link to the forum thread, I missed it when doing general web searches for disabling Chrome updates. It's not that I have any desire to test Chrome 45, but I do need to control the test process, and having Chrome update in the middle of a test suite mucks up the process. The move to TestComplete 11 is a whole other set of issues. Now that it's known that Chrome updates cannot be reliably stopped, the test process will be modified to adapt to it.
Related Content
- 12 months agoMW_Didata