Windows 10 Right Click Properties not appearing

[dark_blitz]

Yesterday an Update for Windows 10 was installed and now I noticed that my Properties option on the Right Click Context menu isn't working. I've tried SFC scannow and it said that the corrupted files has been fixed but the issue still persist. It doesn't work on folders, files, shortcuts and local disks. So far it's still working when I click properties on My Computer.

Thanks!

 

[little_me]

Really? I start to dread rebooting now since I've not done it yet. :S
In any case, you tried "dism /online /cleanup-image /restorehealth" which should fix what sfc /scannow cannot?

 

[dark_blitz]

Really? I start to dread rebooting now since I've not done it yet. :S
In any case, you tried "dism /online /cleanup-image /restorehealth" which should fix what sfc /scannow cannot?

Nope, problem still persist, but after that I tried to restart and it just got stuck to Restarting loop and I had to hit the reset button... What's dread Rebooting?

 

[little_me]

it's nothing, I just said I start to dread (definition, to fear, be afraid, fancy words) rebooting myself since Computer downloaded and started nagging about windows 10 updates for me too.
Raising the possibility that I might in theory, run into same problems.

In any case, you tried safe mode yet? or uninstalling said two updates? (for me, it is two)
If that fixes it, I think there was a "stop specific update from auto-reupdating" thing
https://support.microsoft.com/en-us/kb/3073930?utm_source=twitter
which would allow you to stop said update from happening, in theory.

Edit, seems one of the updates is "almost" service pack, https://support.microsoft.com/en-us/kb/3140768
which is also offered as offline download. In any case, uninstalling and/or reinstalling it might fix what has gone wrong.

Edit2: For me, rebooting did not include odd right clicking hiding properties problems.

 

[dark_blitz]

it's nothing, I just said I start to dread (definition, to fear, be afraid, fancy words) rebooting myself since Computer downloaded and started nagging about windows 10 updates for me too.
Raising the possibility that I might in theory, run into same problems.

In any case, you tried safe mode yet? or uninstalling said two updates? (for me, it is two)
If that fixes it, I think there was a "stop specific update from auto-reupdating" thing
https://support.microsoft.com/en-us/kb/3073930?utm_sour...
which would allow you to stop said update from happening, in theory.

Edit, seems one of the updates is "almost" service pack, https://support.microsoft.com/en-us/kb/3140768
which is also offered as offline download. In any case, uninstalling and/or reinstalling it might fix what has gone wrong.

Uninstalled, Restarted and still no dice... good that it didn't happen to you, but I can't blame the update because that Start Menu issue with windows 10 was pretty much random too. I'm not sure if this is HDD related because mostly I can't check the properties of nearly all the files. (haven't found others that would open the properties)

update: I can't do a system restore because for some reason the System Restore Protection was off for all drives (I don't even remember turning them off)

update 2: Ok so I tried creating a new User and checking if the properties would work there and it didn't..

 

[little_me]

the reason for the problem might be that possible corruption, hinted by sfc /scannow that for some reason was not fixable by the dism.
To recap, what parts are unfixable by sfc?

Also according to https://support.microsoft.com/en-us/kb/929833
you might have to run sfc /scannow in safe mode.

at above site, they also mention how to get a more easily readable error log of the result:
"findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt""

All in all, that site should have a good read for getting said file corruption fixed.
Said file corruption could also be a result from breaking hard disk, crystaldiskinfo can tell more about that.
http://crystalmark.info/software/CrystalDiskInfo/index-e.html

 

[dark_blitz]

the reason for the problem might be that possible corruption, hinted by sfc /scannow that for some reason was not fixable by the dism.
To recap, what parts are unfixable by sfc?

Also according to https://support.microsoft.com/en-us/kb/929833
you might have to run sfc /scannow in safe mode.

at above site, they also mention how to get a more easily readable error log of the result:
"findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt""

All in all, that site should have a good read for getting said file corruption fixed.
Said file corruption could also be a result from breaking hard disk, crystaldiskinfo can tell more about that.
http://crystalmark.info/software/CrystalDiskInfo/index-...

Thanks for the response but I have already tried that SFC /Scannow twice in safemode (one last night) and still it says that there were no integrity files needed to be replaced or fixed (something like that) I also tried to get a that readable error log but gave me a File Directory Not Found (I replaced Userprofile with my username but even without changing it, still said not found)

The good news is that it seems to be working fine during safe mode and that there's this weird app that prevents the pc from shutting down. The app is called Program Manager. it only happens when I'm not on safemode.

UPDATE:

FIXED! The issue that caused is was a registry from a VPN Software called Easy Hide Ip, deleted the remaining registries using autoruns by sysinsternals and the properties was restored!

Thank you for your help little_me!

 

[colinian]

I discovered I had the same problem with right-click context menus in Windows 10 File Explorer but nowhere else. I checked to see what I'd installed most recently (I use Revo Uninstaller Pro which lets me view programs by installation date); it was WinZip 21.5. I uninstalled it, restarted Windows 10, and my right-click context menus in File Explorer work like they should.

I'm not sure if the problem was caused by WinZip or if I had too many programs that added themselves to the context menus. I don't have time to experiment, and my problem is solved, so all is good.