If VB Migration Partner fails to run Microsoft Visual Studio, chances are that your registry is corrupted. At any rate, you can specify the exact path of the Visual Studio executable (devenv.exe) by editing the VisualStudioPath setting in VBMigrationPartner.exe.config file, as in the following example:

        <applicationSettings>
            …
            <VBMigrationPartner.My.MySettings>             
                <setting name="VisualStudioPath" serializeAs="String">
                    <value>c:\Visual Studio 2005\bin\devenv.exe</value>
                </setting>
                …
            </VBMigrationPartner.My.MySettings>
        </applicationSettings>

This setting affects also the VBMP and AxWrapperGen command-line tools.