Opera executable stored in different folder for each version update
A Former User last edited by
There must a very good reason for this but I puzzle to myself what that reason is. I use Agnitum Outpost Firewall Pro 9.3 on Windows 8.1 and will be doing so until April 2023 when Windows 8.1 support ends. Outpost provides a protection called Application Guard which protects application data from being accessed by unauthorized processes. Since the executable folder changes at each version update, I have to manually update the Application Guard list for the entry for the new Opera version's executable. The Google Chrome executable is always in the same folder.
To be truthful, this is just an irritant but the old folders remain after version updates so it seems to be necessary to delete them manually.
Apart from this, I am extremely pleased with Opera Chrome, having had a four year gap between using Opera 12.17 and the new Chrome version.
Thank you for reading this.