3

I have Windows 10 Pro build 16299.492 completely up to date on a computer with an AMD FX 8350 CPU, 16 GB DDR3 RAM, an Asus M5A99X EVO R2.0 and an Nvidia Geforce GTX 1070 GPU (PNY Founders Edition). Every now and then, when I right click in the Windows Explorer, all my right click menu items suddenly disappear. Searching online has turned up two long, extensive threads at Microsoft's official tech support site here and here, where many other users report the same issue and with several Microsoft tech support representatives unsuccessfully trying to fix this issue.

Does anyone here have any idea of how to fix this?

(Please note: the folder items do not go missing, they have been removed for privacy but they display fine on my computer).

Right click menu items missing

Improve this question
7
  • Have you restarted the PC?
    – Moab
    Jun 25, 2018 at 23:58
  • 1
    Usually, a problem with the context menu indicates that some application has flubbed its attempt to register it's own context menu extensions. Is there any pattern to what you right-clicked on (files, folders, a specific file type, the desktop, etc) when the context menu malfunctions? What about when right-clicking in a browser window?
    – Cliff Armstrong
    Jun 25, 2018 at 23:59
  • 16299.492 is approximately 2 weeks old. I am not even including the fact, 1709, is no longer the current release branch.
    – Ramhound
    Jun 26, 2018 at 0:27
  • My system could have missed a recent update. I kinda have the suspicion that running VMware Player can block updates from being installed, since I always run a VM and I have almost never seen the pending restart window. I'm going to do that once I get home.
    – RAKK
    Jun 26, 2018 at 2:05
  • Also, this error goes away when I restart the computer but then it happens again. From what I gathered, sometimes it happens after a few hours, sometimes after just a few minutes.
    – RAKK
    Jun 26, 2018 at 2:07

1 Answer 1

Reset to default
0

A couple weeks after the question was posted, my system received an update to Version 1803 Build 17134.165. Since this update was installed, I haven't experienced this issue anymore.

I believe we can call it quits on this issue, and that the fix is to wait for the update to this build of Windows 10 to roll out for your system and geography.

Windows build that fixes the issue

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .