Procexp.exe 17.2.0.0 not starting

Run the portable Microsoft download of Process Explorer 17.2 outside C:\Program Files\WindowsApps; this isolates a damaged Store package from an application or operating-system compatibility failure.

1. Test the portable distribution

1. Download Process Explorer from the official page: Download Process Explorer.
2. Extract the ZIP completely to a writable local folder, for example: C:\Tools\ProcessExplorer
3. Run procexp.exe from that extracted folder. Do not copy it into or launch it from the protected WindowsApps directory.
4. If necessary, right-click it and select Run as administrator.

Process Explorer 17.2 officially supports Windows 11 and is designed to run directly as a portable executable; it does not require conventional installation.^1^

The event’s KERNELBASE.dll entry does not by itself prove that this Windows DLL is damaged. Exception 0xc06d007e matches the Visual C++ delay-load exception generated when a required module cannot be loaded (ERROR_MOD_NOT_FOUND).^2^

2. If the portable copy works

The failure is isolated to the Microsoft Store/MSIX copy under:

C:\Program Files\WindowsApps\Microsoft.SysinternalsSuite_2026.10.0.0_x64__8wekyb3d8bbwe

Repair that package:

1. Open Settings → Apps → Installed apps.
2. Find Sysinternals Suite.
3. Select … → Advanced options → Repair.
4. Test Process Explorer.
5. If it still crashes, return to the same page and select Reset.
6. If reset fails, uninstall the suite and reinstall it from Microsoft Store → Library.

Repair preserves app data where supported; Reset reinstalls the app and clears its app data. Microsoft also recommends reinstalling Store applications when repair/reset does not resolve the problem.^3^

Alternatively, keep using the portable distribution. Sysinternals tools are portable executables and do not need to be installed as individual Windows applications.^4^

3. If both Store and portable copies crash

That points away from Store-package corruption. Determine which dependency cannot be loaded:

1. Start Process Monitor.
2. Clear the existing capture.
3. Add a filter:
   • Process Name is procexp.exe → Include
4. Start capture, launch Process Explorer once, then stop capture.
5. Examine the final events for DLL operations returning:
   • NAME NOT FOUND
   • PATH NOT FOUND
   • BAD IMAGE
6. Export the filtered trace as a PML file.

Do not treat every NAME NOT FOUND result as an error—Windows routinely probes several locations. Focus on the final repeated DLL lookup immediately before procexp.exe exits. The exception indicates a load failure, but Event Viewer alone does not identify the missing module.^2^

There is no Process Explorer 17.2 startup failure listed among the documented Windows 11 26H2 known issues for the supplied build family, so an OS-wide repair should not be the first action.^5^

If Process Monitor identifies a missing Microsoft runtime or system component—or if several unrelated applications also fail—capture the missing DLL name and report it through the Process Explorer section of Microsoft Q&A linked from the official download page. Include the Event Viewer record, portable-versus-Store test result, and filtered PML trace.

References

1. Process Explorer v17.2
2. Error handling and notification
3. [Windows 10](https://support.microsoft.com/accounts-billing/fix-problems-with-apps-from-microsoft-store)
4. How to install SysInternals properly? - Microsoft Q&A
5. Windows 11, version 26H2 known issues and notifications