Windows 10: Which context menu item broke my task scheduler & event viewer?

I get a "mmc could not load snap-in" error for those after using Windows 10 Manager's Context Menu manager to clean up my context menu.

I disabled about a dozen items and didnt notice it broke anything until after a restart.

I tried to backtrack my steps and had little luck so i simply re enabled everything. The problem is at that point even after re enabling them all and restarting, task scheduler etc stay broken.

Any idea which items in the context menu would be linked to something like that and why after re enabling said item it doesnt fix the issue?

Ive dug through tons of microsoft forum posts, messed with registry settings, re installed .nets etc.

I went ahead and did a restore which managed to mess up my dropbox pretty good (didnt consider that angle as dropbox runs at windows start for me) and id like to deter and further havoc.

The ideal result would be to return to the latest restore point where everything would be as it should EXCEPT my dropbox (hopefully fixable) and the choice mmc snap-ins (assuming i can find out why they arent starting/working properly)

Anyone able to offer anything I may not have ran across on google?

:)

 

Help me fix my MMC Snap-ins please! (disabled context menu entry and it broke them)

I used a piece of software called Windows 10 Manager which is a collection of tools one of which is a Context Menu Manager.

I disabled a half dozen items but the problem didnt present itself until after I had restarted several days later. I used a restore point and went through a process of elimination to determine it was the "Send-To" context menu entry being disabled which
caused the "MMC could not create the snap-in" error for things like event viewer and task scheduler.

These are both important softwares to me and the restore point is too old to be a viable solution.

I went ahead and re enabled the "Send-to" entry in Context Menu Manager which DID return said context menu entry to my context menu. It unfortunately DID NOT return my snap-ins to their previous functioning behavior however.

What is the disabling of this menu entry tied to that is potentially not re-enabled? I need to fix this urgently.

I've ran sfc's, gone through all existing threads i could find ala google, re installed .NET frameworks... I'm at a loss hence the posting.

This one is gonna take one of the pros i imagine

 

Context menu items not working in Start and Desktop

Good morning,

recently I found out that my Start menu & context menu items on desktop are not working correctly. For example:

When I right-click on Start menu, context menu appears (Programs and Features, Power Options, Event Viewer,...), but only 2 items are working (Desktop & Shut down or sign out). When I right-click on any icon on desktop and choose "Run as Administrator",
nothing happens.

I wanted to do integrity check, but when I run sfc /scannow, I get "Windows Resource Protection could not start the repair service" error. Any help, please?

 

I figured it out!

Disabling the Send-To menu does it. NOw the more important question is how to fix it? considering re checking the box to enable send-to again doesnt seem to revert the behavior. what is not getting "turned back on?"

Just to be clear, re enabling the send-to context menu item does return send-to to the context menu, however it does not revert my broken snap-ins to functioning.

 

For anyone with a similar issue in the future.

It seems modifying anything related to the send to menu (doesnt have to be removal of the send-to menu itself, but evne using context menu manager to modify (aka disable) any of the items under it (things like bluetooth ill never use on my desktop for example) will break the mmc snap-ins.

The only way to do it without breakage is simply deleting the shortcuts in shell:sendto folder. The tie-in/relation via mmc and the other method or the menu itself is above my pay grade

 

Hi, an important key to playing with the context menu is never to disable anything MS related.

Shellexview and Shellmenuview are useful tools; both allow you to hide standard or MS items, so you are then relatively safe.