The Module DLL '%1' could not be loaded due to a configuration problem. The current configuration only supports loading images built for a %2 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see http://go.microsoft.com/fwlink/?LinkId=29349.
The module "%1" may not compatible with the version of Windows that you're running. Check if the module is compatible with ...
The module "%1" was loaded but the call to %2 failed with error code %3. For more information about this problem, search ...
The module "%1" was loaded but the entry-point %2 was not found. Make sure that "%1" is a valid DLL or OCX file and then ...
The module "%1" was loaded but the entry-point %2 was not found. Make sure that "%1" is a valid DLL or OCX file and then ...
The Module DLL '%1' could not be loaded due to a configuration problem. The current configuration only supports loading images ...
The module manifest '{0}' could not be processed because it is not a valid PowerShell restricted language file. Please remove ...
The module manifest member 'NestedModules' cannot be used if 'ModuleToProcess' member is a binary module. Please fix the ...
The module to process '{0}', listed in field '{1}' of module manifest '{2}' was not processed because no valid module was ...
The module(s) assigned to this handler mapping has the following preconditions that are not present in the handler mapping: ...