Then it's almost certainly caused by some incorrect registry setting(s) in your user-profile.
There may be a clue in the article linked by
@dacrone. Looking at the contextmenuhandler key in HKCU would seem like a good starting point, but that's not necessarily where the problem lies.
Sometimes running a
repair install (which keeps your apps and data) will fix certain user profile problems and, if that works, will likely take less time overall.
However, this issue does sound like something we should be able to fix directly. It just may take some trial and error. The PowerShell script in that SuperUser article doesn't look right though (it generates errors for me). If you like, you could export your HKEY_CURRENT_USER key and send that to me via
WormHole. You can message me for my email or find it in the WinSetView manual.