Cannot open Windows Troubleshooting (Error 0x80131700)

Hello, I recently had to reinstall Windows 7 and now I cannot open any aspect of Windows Troubleshooting or DiagPackage, including Program Compatibility. I get an error message of 0x80131700. I read another site saying to go into Program Compatibility to fix this, but it will not allow me into it! I also cannot open the Diagpackage file at all due to this error. Can you help please, dont know how to fix this, thanks much!

Hello there, welcome to Seven Forums.

Option 1: Check in Default administrator account.

1. Login into Windows using your account.
2. Click Start.
3. Type cmd in the start search.
4. Right click on the cmd option from the list and select Run as Administrator.
5. Now type the following command:
net user administrator /active:yes
6. You should see a message that the command completed successfully.
7. Log out of your account using the Log off option.
8. Now you will be able to see the Administrator account with your account at the Windows Logon screen.
9. Login to Windows using default administrator account.
10. Check if you are still facing with the issues.

Option 2: Run SFC Scan
1) Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow
2) Type "sfc /scannow" (without quotes) and then press ENTER
The sfc /scannow command scans all protected system files and replaces incorrect
versions with correct Microsoft versions.


Here's the complete thread:
my troubleshooter in upgraded windows 7 does not work

I will try that out and let you know what happens! Thank you.

These two steps unfortunately did not resolve anything with the Troubleshooter error. Still getting the same message both when I log on as Administrator and as me. Should I attempt the Windows Repair Installation as mentioned in the full thread?

You should first try a system restore, to a point where the troubleshooter worked.
If that doesn't do it, do a repair install(read the tutorial & back up important files first).

It turns out this error is related to the Microsoft .Net Framework 3.5.1 and 4. I read on another forum that you should go into Windows and Features, turn off the 3.5.1, restart, then enable it again. Well because my Windows updates had already downloaded the .Net Framework 4, my 3.5.1 was showing only partially enabled and I could not change it. So I uninstalled the Net Framework 4 and now the Troubleshooter works again. Don't know what the resolution is to be able to keep the important Net Framework update AND the Troubleshooter, but it doesnt want to work with the .Net Framework 4 installed. They should come up with a patch or something to fix both. Thanks for your suggestions.

.NET 3.5 is a component of Windows 7, in other words, it was already included in the Operating System. .NET Framework 4 is an optional runtime update that benefits developers who code programs, applications, or web sites.

If no program, or application that you've installed nor any web site that you frequent informs you that .NET Framework 4 must be installed in order for the program/app/site to function, then you have no need for it.

The .NET Frameworks are notoriously brittle and updating them is a hit & miss proposition, mostly miss. The Microsoft Windows Update 'answers' forum is populated with scores of threads about .NET Framework installation and updating issues.

And, as happened with Sun's, now Oracle's, Java runtimes that were troublesome and slow to update, the cybercriminals become aware of the fact that a significant segment of Users will give up trying to update them. As a result, the cyberthugs will eventually start pushing out exploits for .NET vulnerabilities that have been patched by MS but not by their .NETWeary Users.

Perhaps MS will prevent that scenario before it occurs ? :banghead:

What's more likely is, I'll be dating Lady Gaga next week.