ZiRiS

New Member
Joined
Feb 16, 2011
Messages
8
"MMC cannot open the file c:\windows\system32\secpol.msc

This may be because the file does not exist, is not an MMC console, or was created by a later version of MMC.This may also be because you do not have sufficient privileges to access the file"

is the error I receive when trying to "double click" to open any .msc file. I also receive it when trying to right click "My Computer" and then click "Manage".

I'm stumped, y'all. :confused: I am seasoned with over 13 years help desk support and Networking, and I'm Security+ Certified from CompTIA. So I searched the internet and found this link. It talks about WindowsXP and links to this page, which in turn talks about KB842773. So I searched that and found it on Link Removed. It speaks to several operating systems, but not Windows7, and talks about updating BITS to version 2 and HTTP Services to version 5.1. I have not checked, but also don't have the time to look up every single KB article that Windows Update has installed. I did look in Programs and Features, Installed Programs, and Show Installed Updates to see if anything was listed about BITS or HTTP Services. It was not.
I *can* run .msc's if I WIN-R>mmc then add/remove snap-in. But that is the *only* way to run any .msc.

Windows 7 Ultimate 6.1.7600
Intel "Wolfdale" E8400 @ 3.0 GHz
6 Gb RAM
4.41 Tb HDD space, with approx. 2.3 Tb free,
C:\ Drive has about 196 Gb free
1 drive is IDE, but it is not C:\ the rest, including C:\ are SATA @ 3Gb/s
System Protection/Restore turned off on all drives except C:\
virtual memory or page file is system managed

That's just some system specs that may or may not have anything to do with this. Like I say, I'm stumped. I really hope someone can help! Need more info just ask!
 

Solution
It seems like you're encountering an error where you are unable to open .msc files, such as secpol.msc, by double-clicking on them or using the "Manage" option for "My Computer." This issue can be frustrating, especially with your experience in help desk support and networking. Here are some steps you can take to troubleshoot and potentially resolve this issue: 1. Check File Existence and Permissions: - Verify that the secpol.msc file exists in the C:\Windows\System32 directory. - Ensure that you have sufficient permissions to access and open the file. 2. MMC Console Check: - Confirm that the file is indeed an MMC console file. If it's corrupted or not recognized as an MMC console, this could lead to the error message you're...
It seems like you're encountering an error where you are unable to open .msc files, such as secpol.msc, by double-clicking on them or using the "Manage" option for "My Computer." This issue can be frustrating, especially with your experience in help desk support and networking. Here are some steps you can take to troubleshoot and potentially resolve this issue: 1. Check File Existence and Permissions: - Verify that the secpol.msc file exists in the C:\Windows\System32 directory. - Ensure that you have sufficient permissions to access and open the file. 2. MMC Console Check: - Confirm that the file is indeed an MMC console file. If it's corrupted or not recognized as an MMC console, this could lead to the error message you're seeing. 3. MMC Version Compatibility: - Confirm if the .msc files you are trying to open were created by a later version of MMC that might not be compatible with your current MMC version. Updating MMC might help in this case. 4. System Updates: - While the KB842773 update you found may not specifically mention Windows 7, it could be related to the issue. Ensure that all essential Windows updates, especially related to BITS and HTTP Services, are installed. 5. System Health Check: - Perform a system scan to check for any potential system file corruption. You can use the System File Checker tool by running 'sfc /scannow' in an elevated Command Prompt. 6. Manage MMC Snap-ins: - As you mentioned, using the 'mmc' command and adding snap-ins manually works. This method bypasses the issue but is not a permanent solution. 7. Event Viewer Logs: - Check the Event Viewer logs for any relevant error messages that might provide more insight into the issue. 8. Restore Points: - Consider creating a system restore point before making any significant changes or modifications to your system. Given your experience and the complexity of this issue, it might require some in-depth troubleshooting. If these steps don't resolve the problem, feel free to provide more details or run additional diagnostics for further assistance.
 

Solution
Back
Top