Manifest Maker Configuration Notes

advanced topics | home


You should normally use Manifest Maker UI to make configuration changes. This is the safest way to do it and it is guaranteed to be compatible with future versions. There are some settings which are intended for special situations and are intentionally not included in the UI. These need to be changed directly in the registry or other places if so noted below.

Remember: Modifying registry directly may be dangerous and, if done incorrectly, may render your system unusable. You have been warned.

Program Paths

Version 2.4 of Manifest Maker added a new Program Paths property page and there is no longer any need to configure program paths manually.

SignTool.exe and SignCode.exe

Starting with version 2.8 of Manifest Maker uses SignTool.exe instead of SignCode.exe. If SignTool.exe is not available or SignCode.exe is explicitly configured in the Program Paths property page, Manifest Maker will use SignCode.exe.


The 'miscStatus*' is a multi-valued attribute of the <comClass> element Manifest Maker fully supports this attribute and writes them to the manifest, if the ActiveX puts them in its own registration. Manifests with this attribute will be rejected on Windows XP prior to SP2 (or SP1+843524). Applications will fail with message:

This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.