I have been thinking about how to make `winemenubuilder` ignore these shortcuts, if that's desirable. So far I've mostly had ideas that I really don't like: * The shortcuts could be marked somehow with the fact they are built-in WINE shortcuts, but I would rather not add a special extension to the INF format for this purpose, or have to add special private APIs. That feels rather unclean. * I also would rather not use some side-channel to detect where the shortcut creation API calls have come from. That feels even worse. * `winemenubuilder` could of course look at `wine.inf` and compare the shortcuts to that, but that'd be a lot of code and I don't like the fact you now have two things processing the INF file that might disagree with eachother. * `winemenubuilder` could have a hardcoded list of exceptions, but that's even worse. The one promising one is to have `winemenubuilder` look at the shortcut target (i.e. the `.exe` file) and see if it has the WINE built-in or fake DLL signature in the MZ stub. That's pretty trivial to do and all the bundled WINE `.exe`s have that. I will try implementing that at some point. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10867#note_139688