Forced Start Menu Icon with version 154.0

If you are talking about the Windows task bar at the bottom of the screen this is a Windows feature, it list all the open programmes.

You mention the start menu which is different, could you show a screenshot.

Thanks

This has nothing to do with the taskbar, it is strictly the Start Menu where this is occurring.

Oddly enough, in spite of Windows 11 displaying multiple copies of the Firefox shortcut, there is only one such shortcut in the actual Start Menu folder, as in the 2nd screenshot here. That one shortcut is what I am trying to stop Firefox from creating.

OK I see, the Programmes menu :)

Just checked mine Win 11 Home Fx 154.0

All fine. Just the one instance of Fx plus one for Fx private

So where is the other list with all the Fxs

I don’t know, but that’s not what I’m talking about. Please read my original question again, as I was careful to be very precise with my wording. I do not want ANY icon in my Start Menu named "Firefox". I do not want it in the private Start Menu or the all users Start Menu. I have shortcuts in other places that I use for Firefox, so this new one that is being created by version 154.0 is REDUNDANT. No other version of firefox.exe in the past has EVER created Start Menu icons on my machine, so this is obviously a new feature that was introduced with this version for some reason that makes absolutely no sense whatsoever to me. So how do I stop Firefox 154.0 from creating this icon?

And just to be clear, I'm not talking about the Firefox setup file either. It's "C:\Program Files\Mozilla Firefox\firefox.exe" that is creating this unwanted icon.

Tracked: bugzilla.mozilla.org/2064836

This is extremely annoying behavior. I have Firefox in my taskbar, and I do not want it to keep putting itself in the start menu against my wishes. It is probably connected to Settings | Appearance | Browser Icon, which is a new setting in this version.

This is the sort of annoying behavior which makes me want to dump Firefox for another browser.

Based on what I can make out from the bug discussion forum referenced above by jbr, the developers have acknowledged that yes, Houston, we do have a problem, and there has apparently been a lot of complaining from end users about it.

They have also acknowledged that it needs to be fixed (although precisely “how” that fix will be implemented I have no idea), but the caveat is that it is not scheduled to roll out to the general public until Firefox 156 is released - which means that, apparently, those of us who do not like experimenting with beta-type releases are going to have to wade through the rest of 154’s life cycle as well as 155.x additionally.

I just wish they would decide to release a 154.x patch earlier, because I am going to spend today experimenting with another browser to check into the possibility of dumping Firefox altogether forever and ever.

With Mozilla historically making major GUI changes (such as “Quantum” with version 57) due to attempts to compete with Google Chrome’s dominance of browser market share, this is just the latest in a repeating pattern of changes that get foisted on end users who frequently do not want or like them.

For me, if the other browser that I am going to experiment with (not Chrome, just FYI) works out OK, then my days of using Firefox for the last 20 years will be over, once and for all.

Mozilla’s developers need to learn the meaning of, “If it ain’t broke, then DON’T FIX IT!!”