Opera 40 still latched to Opera 39

  • Unsure if this is a bug or not so here goes. Received the auto update v40.0.2308.62 (with VPN) and this version clearly shows in default programs. Am running Windows 7 Professional. I always place the Opera icon on taskbar so removed v39 icon from taskbar. Then went to Start -> All Programs, and right clicked the Opera icon and placed a new Opera icon on the taskbar. NOTE: This is something I've done many times before without problem. THE PROBLEM: When I right click the new Opera icon on taskbar, then click "New Private Window", an error message pops up to say it cannot be found and refers to the previous version 39. Query: WHY is v40 still latched to v39, even though v39 has been deleted from my system. Importantly, when when I pin v40 to the tasbar, I should not be getting any reference to v39? Anyone else with this issue please, and how to fix it? I could uninstall, but that means I lose my bookmarks which I don't want to lose.

  • Have you tried a reinstall?

    You can also run launcher.exe from Opera's install folder and then, with Opera opened, right click on the task-bar icon to pin it.

    I could uninstall, but that means I lose my bookmarks which I don't want to lose.

    No, it doesn't.

  • leocg - so if I uninstall Opera from programs, then reinstall v40, my bookmarks and speed dial will remain intact? Sorry for not quite understanding and appreciate your help. I will try launcher.exe as you suggest.

  • If it concerns you simply make a copy of the Bookmarks file inside your Opera profile. Then, no matter what, you will have a backup of it. It's generally a good idea to have one anyway.

  • so if I uninstall Opera from programs, then reinstall v40, my bookmarks and speed dial will remain intact?

    Yes, as long as you don't check the option to delete your data in the un-install dialog.

    And, as said, you can always do a backup just in case.

  • This happens when pinning Taskbar shortcuts in Windows 7 involving any program. There is an internal OS data list associated with pinned Taskbar shortcuts wherein Win7 creates a unique entry for each differently-named Taskbar shortcut at the time of its pinning. Subsequent unpinning of a shortcut does not delete its data entry from that list - it still remains, indexed by its shortcut name. If a shortcut is unpinned and a new shortcut of the same name is later manually pinned to the Taskbar (regardless of the other details that shortcut contains), it will automatically inherit the shortcut details from the previously unpinned (but still internally-listed) shortcut of that same name, instead of bringing in new shortcut data.

    If one creates a fresh shortcut on the desktop with altered shortcut details but the same name as an earlier Taskbar-pinned shortcut, it is necessary to also alter the shortcut name before pinning the new shortcut to the Taskbar. Otherwise the resulting Taskbar shortcut will revert to whatever data remained in the Taskbar's list from the previous shortcut of that same name. For example, a desktop shortcut named 'Opera' pointing to some filename/location must be renamed to something like 'Opera40' before pinning it to a Taskbar that previously hosted a pinned shortcut named 'Opera' that pointed to some other filename/location.

    If one allows a properly-designed program updater to 'tweak' the Taskbar shortcut's listed data rather than manually unpinning/re-pinning shortcuts, this kind of problem doesn't arise. The problem exists because of how Windows 7 (at least) is designed and how that affects the manual Taskbar unpinning and re-pinning of different shortcuts with the same name.

Log in to reply
 

Looks like your connection to Opera forums was lost, please wait while we try to reconnect.