I managed to fix the context menu issue once again, this proves Winamp is anything but stable, we see it for years and it's been ignored for some reason.
Here is the fix:
If everything in Windows ''Default apps'' and Winamp Options > Shell Options is set right and the file context menu is still not present, try right-clicking the file (you need to do this same thing for EVERY file type you want the Winamp context menu to be showed) > properties > opens with > select the program the context menu was showing (it was Cyber Link for me this time) > apply < OK. Then revert this by clicking ''properties'' once again and selecting Winamp from the ''opens with'' list. Everything should work now.
One more thing, what may happen is your file type icon is now changed. This is fixed in exactly the same way shown above. Really annoying but also fixable.
It's all fairly simple and works every time for me but it's really frustrating having to do this every single time you update Winamp.
Besides, on every Winamp update, I never know which program will be shown in the file context menu, so it's clearly a Windows 10 issue also.
Here is the fix:
If everything in Windows ''Default apps'' and Winamp Options > Shell Options is set right and the file context menu is still not present, try right-clicking the file (you need to do this same thing for EVERY file type you want the Winamp context menu to be showed) > properties > opens with > select the program the context menu was showing (it was Cyber Link for me this time) > apply < OK. Then revert this by clicking ''properties'' once again and selecting Winamp from the ''opens with'' list. Everything should work now.
One more thing, what may happen is your file type icon is now changed. This is fixed in exactly the same way shown above. Really annoying but also fixable.
It's all fairly simple and works every time for me but it's really frustrating having to do this every single time you update Winamp.
Besides, on every Winamp update, I never know which program will be shown in the file context menu, so it's clearly a Windows 10 issue also.
Comment