Windows 10: MMC snap-in bug. Not saving size, specifically Action panel

I've had this issue with my Windows 10 machine and now with my new Windows 11 machine. When I open MMC snap-ins, either built in eventvwr.msc or custom created/saved ones, the size of the Action panel keeps resetting to a very large value taking up a lot of screen real estate.If I open the MSC file I can see the XML that defines this and the ActionPanelWidth parameter is set to -1. Nothing I do can make that parameter save anything except -1. It keeps resetting.If I customize the snapin and simply choose to not show the action pane, it remembers that, but it won't remember the size. This

:)

 

MMC - Could not create the Snap-in

Having Windows 10 Version 1703 64-based on a HP Laptop.

Tried to install gpedit.msc, but continuously have error message

'MMC could not create the snap-in'

with 'CLSID: {8FCOB734-A0E1-11D1-A7D3-0000F87571E3}'

Have tried trolling Google with all suggestions

1) sfc /scannow - with no issues found

2) MMC could not create the snap-in - Google Suche

3) https://blog.multiplay.co.uk/2013/1...reate-snap-in-for-group-policy-object-editor/

4) http://computerstepbystep.com/group_policy_windows_xp.html

5) How To Fix MMC Could Not Create The Snap-in

Where one suggests to delete the 'CLSID: {8FCOB734-A0E1-11D1-A7D3-0000F87571E3}' in the registry to create a new clsid on reboot/restart, I cannot delete it as it returns as an error.

Have installed the gpedit.msc on my Tablet with no issues with same gpedit download.

Any clues

 

MMC detects error in a snap-in

Good morning,

It seems that some of you have fixed the "MMC has detected an error in a snap-in" by using the link shared by catspyjamas. I would like to give this fix a shot too but I want to make sure I really understand the proper steps.

It is my understanding that I go to C Drive > Microsoft > Event Viewer > Views. Right now in the 'Views' folder I have four entries. First is a folder called 'ApplicationViewsRootNode' which is empty. Then I have three of the XML view documents: View 0, View 1 and View 2.

I intend to copy the three views listed into a folder I will make and call it 'Event Viewer MMC fix' before I delete the same three views in the original folder.

Now for the heart of my question: Do I copy the 'ApplicationViewsRootNode' folder currently listed in the 'Views' folder and move it into my new folder with the copied three XML views and then delete it in the original folder like I did the three XML views or keep my hands off of it?

Sorry for such a detailed question but I don't want to screw up my computer.

Thanks and regards,

 

[Annoyance] *Actions* panel size on Hyper-V

Same issue here - Actions pane takes the lions share of the window on launch (on multiple Windows 10 PCs).

I can't say for sure if Sandro's issue was self-inflicted, especially since he/she is encountering other issues as well. But I can say that based on my experiences and the comments in this thread, this is not some isolated incident.

What I found interesting is that at some level, the Hyper-V MMC *does* remember the width you set the Actions pane to. Test it yourself as follows:

1. Open Hyper-V and set the size of the Actions pane as desired.
2. Go to View->Customize and Un-check the Actions pane to hide it, then click OK
3. Close and Re-open Hyper-V
4. Go to View->Customize and Re-check the Actions pane to show it, then click OK

You will notice that it is still at the size you set. So it CAN remember the width between sessions! It only "forgets" the assigned width if it is showing the pane on launch. Clearly this is an initialization issue within the MMC itself. (I would LOVE to say I am surprised, but alas, it is Microsoft after all).

If anyone has come up with a solution of how to fix or work-around this "feature", I would love to hear about it. About the best solution I've come up with is to not close the freaking Hyper-V window.