Right-clicking Vivaldi on task bar does not show any options
-
I recently updated Vivaldi to 3.4.2066.76, and had no issues. Shortly thereafter, I updated to Windows 10 version 2004. Once I did that, all the right-click options for Vivaldi in the taskbar - speed dial sites, new window, private window, etc. - disappeared. See image. This didn't happen to any other program on my taskbar, or to any other browser when I tried pinning it. What's really strange is that my laptop, which has the exact same version of Vivaldi and Windows, does not have this issue, which is where I captured what the task bar menu should look like here.
I've tried restarting my computer, reinstalling Vivaldi, re-pinning the program, etc. with no luck. As mentioned previously, Vivaldi 3.4.2066.70 (Official Build) (64-bit) on Windows 10 Version 2004 on two different computers, a laptop and a desktop. Only the Desktop has the issue.
-
Doing a bit more troubleshooting, this has to be an issue with the 3.4.2066.76 stable build. I had some browser issues a few months ago which required me to reinstall; as a result, I still had the installer for the 3.1.1929.34 build. I installed this version, and the right click jump menu worked as normal. When prompted, I updated to 3.4.2066.76, and this version once again did not show the right click jump menu. It still works on the laptop when following these same steps.
-
@TheFrozenSlime Try on a clean profile.
-
@TheFrozenSlime Works properly here, all versions, all platforms. What's happening with 3.4 is something local to you, so the resolution will probably be found Figuring out what exact thing in your install is doing it.
-
@TheFrozenSlime This happened to me as well when I installed Vivaldi 3.3 (and up).
Try this if it works for you:
- Unpin current Vivaldi icon from taskbar
- Open Vivaldi like you normally would (this should create a "normal" Vivaldi icon beside your usual unpinnned programs that are running)
- Right-click on that Vivaldi icon to pin it to taskbar
This should create a taskbar item that has the jump menu, and opening from that pinned item will also keep Vivaldi there instead of spawning unpinnned ones.
-
Thanks. Worked perfectly.
-
I'm back, this time I tried something new. I completely wiped Vivaldi from my computer, and reinstalled 3.3.2022.47 (x64), the last stable version where everything worked properly. Pinned it to the taskbar, jump menu is there, no problems. Instead of directly updating to 3.4.2066.86, I installed that version as a standalone install to see if anything in my old Vivaldi files was causing the issue. In a standalone install on a separate drive, the jump menu for 3.4 still did not appear. In this gif, 3.3 is on the left, and 3.4 is on the right. I have also tested with several versions prior to 3.3.2022.47, and all worked as expected. I'll continue using 3.3.2022.47 while installing future updates as a standalone install until one works.
@dbugz I tried this with the standalone install of 3.4, and the jump menu was still absent.
-
@TheFrozenSlime said in Right-clicking Vivaldi on task bar does not show any options:
I'm back, this time I tried something new. I completely wiped Vivaldi from my computer, and reinstalled 3.3.2022.47 (x64), the last stable version where everything worked properly. Pinned it to the taskbar, jump menu is there, no problems. Instead of directly updating to 3.4.2066.86, I installed that version as a standalone install to see if anything in my old Vivaldi files was causing the issue. In a standalone install on a separate drive, the jump menu for 3.4 still did not appear. In this gif, 3.3 is on the left, and 3.4 is on the right. I have also tested with several versions prior to 3.3.2022.47, and all worked as expected. I'll continue using 3.3.2022.47 while installing future updates as a standalone install until one works.
@dbugz I tried this with the standalone install of 3.4, and the jump menu was still absent.
I did the same and reported on this thread https://forum.vivaldi.net/topic/52073/vivaldi-pinned-to-the-task-bar-doesn-t-offer-any-option-eg-open-incognito-after-the-latest-update/9
I installed Vivaldi on a different computer that never had Vivaldi installed before and I got the same result.
-
I replied in the same thread.
I created an account just to reply to this.
I've had the same issues as others in this thread and unpinning and repinning the icon has never worked.
Then I stumbled across similar behaviour in an older version of Chrome: https://support.google.com/chrome/thread/14579131?msgid=14828542
From here, it points to the files in the location [C:\Users%USERNAME%\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations] OR [%AppData%\Microsoft\Windows\Recent\CustomDestinations]
Originally, I located the file with AppID 969fa00ceac8236d. Opening this file with notepad revealed the task list for New Tab, New Window and New Private Window.
I then installed Vivaldi on a new machine and noticed that the jump list tasks were present and working.
Checking the same directory, the AppID appears to be different - 158aa8c19981b864.
So like the instructions in the thread, I made a copy of 969fa00ceac8236d.customDestinations-ms in the same directory, and then renamed the new copy to 158aa8c19981b864.customDestinations-ms.Then just like that, the jump tasks appeared when I right clicked on the icon in the taskbar.
Not 100% sure if this bug is with Windows, or with the browser, but hope this might help others who have had the same issue.
-
Yup. That's the one.
If you want to be able to read the contents of these files, you'll need to use a Hex editor (I'd recommend "HxD", but that's just my preference).
I'm not sure how you find the app ID's.
It seems like those people who have been using Vivaldi for a long time are effected by this, as Vivaldi's App ID must have changed at some point, and the updates that get pushed out never actually updated this file.
Is there any reason that this file can't be checked for in future updates? And if it doesn't exist (as was the case for koalapigu and I), then it should be created? I would consider this a bug.
-
Looks like the App ID updated again, so the issue hasnt really been fixed.
Copying the old 969fa00ceac8236d.customDestinations-ms file and renamed the copy to 7e4212a4bc163a47
I generally just get the AppID by installing a fresh copy in a VM and checking the same path.