An error occurred while troubleshooting – 0x803c0107

When you run a Microsoft Troubleshooter pack, the following error may occur:

An error occurred while troubleshooting:

A problem is preventing the troubleshooter from starting.

Error code: 0x803C0107

0x803C0107-troubleshooter error


The error code 0x803C0107 (“SDIAG_E_TRUST”) means “Trust validation of the diagnostic package failed.”

This happens if the scripted diagnostics group policy “Configure Security Policy for Scripted Diagnostics” has been enabled.


To fix the error 0x803C0107 when running the troubleshooter pack, remove the ValidateTrust policy setting.

Method 1: Using the Registry Editor

Please open regedit.exe and go to the following branch:


Delete or rename all the values in the right pane. Especially delete the value named ValidateTrust.

Exit the Registry Editor.

Method 2: Using Local Group Policy Editor

If you’ve configured the above policy using the Group Policy Editor, you need to turn off the setting there.

Open the Local Group Policy Editor (gpedit.msc) and go to:

Computer Configuration → Administrative Templates → System → Troubleshooting and Diagnostics → Scripted Diagnostics

Set “Configure Security Policy for Scripted Diagnostics” to “Not configured”.

Equivalent registry setting:

Registry Path SOFTWARE\Policies\Microsoft\Windows\ScriptedDiagnostics
Value Name ValidateTrust
Value Type REG_DWORD
Enabled Value 1
Disabled Value 0

That should let you run the Microsoft troubleshooter packs.

One small request: If you liked this post, please share this?

One "tiny" share from you would seriously help a lot with the growth of this blog. Some great suggestions:
  • Pin it!
  • Share it to your favorite blog + Facebook, Reddit
  • Tweet it!
So thank you so much for your support. It won't take more than 10 seconds of your time. The share buttons are right below. :)

Ramesh Srinivasan is passionate about Microsoft technologies and he has been a consecutive ten-time recipient of the Microsoft Most Valuable Professional award in the Windows Shell/Desktop Experience category, from 2003 to 2012. He loves to troubleshoot and write about Windows. Ramesh founded in 2005.

Leave a Comment