Or maybe those two values are somehow tied to the operating system. I say this, because when I installed the resulting valid standalone Chrome exe coming from the broken exe, the network was turned off, and there was no prior installation of Chrome on that system. 111), I assume, installation will finish successfully only if the appguid and iid contained in the exe itself, through computation during instalation, will yield a result that matches a value stored somewhere in the exe, or a value that also gets computed during installation. So, since the appguid and iid were coming from a later version of Chrome (appguid and iid taken from. If you use a firewall, please whitelist GoogleUpdate.exe" error. , which, during installation, got me "Unable to connect to the Internet. Each time I'd try running them, I'd get "unknown installer error".
None of the files downloaded by the script worked. So, after letting the script pile up Chrome versions, just a few days ago I got a big surprise when I tried installing an older version of Chrome. Right after running the script, I didn't check to see if the executables are running fine, because I was assuming there wouldn't be a problem with them. A couple of weeks ago I made a batch script, using curl, for downloading all Chrome executable files that I could find, for just in case Chrome gets messed up by an update.
0 kommentar(er)
