Latest WACUP public preview for x86 & x64 is build #24626 (July 10th 2026) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #24626 (July 10th 2026) (x86 & x64 changelogs)

Author Topic: Disable creating Start menu items every time  (Read 8466 times)

butlnor

  • Newbie
  • *
  • Posts: 2
    • View Profile
Disable creating Start menu items every time
« on: May 26, 2026, 10:36:03 AM »
WACUP frequently (daily?) creates a Start menu folder in Windows. I don't like that, and I have to manually delete that stupid folder every day. How can I prevent that?

I am NOT using the default start menu, but "Classic Shell", because I want to have a control over the items in start menu, and I like it clean. I already have WACUP pinned to taskbar, so I don't need and don't like a start menu item as well.

dro

  • Admin / WACUP Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 5810
    • View Profile
    • WACUP (Winamp Community Update Project)
Re: Disable creating Start menu items every time
« Reply #1 on: June 26, 2026, 05:20:12 PM »
It's because that's what I've got to do to allow the OS toast support to be able to show the yes/no buttons for installing new wacup builds or to apply any post-release updates for the existing install. As the OS toast api requires a shortcut in the start menu to exist so if there's no indication of the normal wacup start menu folder group it'll attempt to make one in the root of the start menu (which I know sucks but it was the safest approach to go for when I was debugging the button failures).

I don't know if the alternate shell that you're using support's not showing shortcuts that have been given the hidden file property. As Win10's start menu handling appears to do support that from a quick test which is the only obvious workaround I can think off that doesn't then break the reason behind having to create it when I really would prefer to not do it anyway.

butlnor

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: Disable creating Start menu items every time
« Reply #2 on: July 10, 2026, 12:35:21 PM »
Why would I need a toast? I never update the software, I just need a simple audio player. But every day, I get back the entry in Start menu. So I am thinking of getting rid of WACUP just because of this. It is annoying, and making me angry. Winamp did not do this.

I would continue using 20 years old Winamp, but it does not support newer SSL protocols which the online radio I listen to, is using. This is the only reason why I had to switch to WACUP.

dro

  • Admin / WACUP Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 5810
    • View Profile
    • WACUP (Winamp Community Update Project)
Re: Disable creating Start menu items every time
« Reply #3 on: July 10, 2026, 02:06:32 PM »
I'll be clear on this, WACUP is not Winamp so I will do things differently to it based on what I feel needs to be done with it. If you (or anyone else reading this) are not happy with that then you are more than welcome to uninstall it & use something else that better suits your needs. Additionally if you've made a donation then let me know the details & I'll do what I can to get it refunded so you're not out of pocket.



There are a bunch of options to control how wacup will do update checks so you can always just disable all of that & stick on whatever version you've got installed. That is from preferences -> about|updates -> updates tab (with a never option also being added for the next interim build to the post-release updates dropdown at the bottom) or by going to preferences -> general -> internet | online & turning the option off - it still allows you to play streams but it won't then do any update checks, etc.

As I've already tried to explain it's not my fault that the OS has a shitty requirement to do something that I also don't like related to a mode that otherwise I find is beneficial for getting post-release updates installed sooner. I also made changes with the 24616 build that recently went up which tries to auto-hide the shortcut when the fallback handling (as described previously) has been triggered.

So I've done what I can & if you don't like that then there's nothing else I can do & yes you should just uninstall it & move on.
« Last Edit: July 10, 2026, 02:15:03 PM by dro »