Mighty Desktop

Diagnose Start Problems

 

 

Share

 

Overview
Suspend-Resume
Permanent Apps
Quick Items
Installed Programs
Desktop
Toolbox
Devices
Intranet
File Copier
File Renamer
File Comparer
Duplicate Cleaner
File Scanner
Folder Analyzer
File Splitter
File Concatenator
Drive Speed
Dictionary Merge
File Stamper
Duplicate Truncator
String Hunter™
Watchdog
Calcuverter
DualTypeCalc™
Unit Converter
DateTime Calculator
Currency Converter
Scheduler
Actions
Text Expert
Text Converter
Clipboard Recorder
Window List
WindowBot™
Process List
ProcessBot
Open Files
Process Variations
Process Functions
System Safety Functions
Seed Enigma™
Verify Integrity
File Monitor
Binary File Viewer
File Protector
Backup
Data Refresher
Windows™ Extensions
Environment Variables
Command Shell
Locate Command
Error Codes
Diagnose Start Problems
Desktop Shortcut
Hotkeys
Process Queue
Explorer Integration
Settings
About
General Features
Download
Buy License
Help
3rd Party Reviews
 

 

 

 

 


Sometimes Windows applications don't start even without showing a window. The cause is usually an incompatibility with the rest of the system. As a developer you can get this if your app is missing a DLL or resource, or loads the wrong one (so called "DLL hell"). Finding the cause can be very complicated and time consuming. This tab (part of the 'Windows™ Extensions' tab) starts the application in a heavily supervised environment.

Each small step is protocoled. If another module is loaded this will also be supervised which will help to identify the culprit. Exceptions will be caught and displayed in full detail. The returned error code is automatically looked up in the list of all error codes (see tab 'Error Codes') and the explanation is displayed. This analysis will give you a hint what must be fixed.

This function can be used for .NET apps as well as Win32 apps and also for any standalone DLLs. It can therefor also be used as a tool to identify what kind of app an executable really is.

Notes:

  • If you experience locked EXEs or DLLs a restart of Mighty Desktop can sometimes fix it. Reason: Assemblies are loaded into a so called AppDomain but the .NET concept of an AppDomain doesn't support unloading EXEs or DLLs. So a restart might be the only solution.

  • Mighty Desktop itself is a x86 app (32-bit). This can have an influence on how 64-bit libraries are loaded.

 

 

Go to Homepage