MSI Microsoft Visual Studio Installer Projects 2022 : Error 1001. InstallUtilLib.dll:CorBindToRuntimeHost

Anthony 0 Reputation points
2025-04-04T14:41:27.7366667+00:00

Hello everyone,

I hope you're doing well. I'm seeking advice regarding an issue I encountered after migrating my PC from Windows 10 to Windows 11.

The problem lies with a setup created using Microsoft Visual Studio Installer Projects 2022, which no longer works correctly post-migration. I’m receiving the following error message:

The description for Event ID 11001 from source MsiInstaller cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Product: MyProduct -- Error 1001. InstallUtilLib.dll:CorBindToRuntimeHost (hr=0x80070003): The specified path could not be found.

To provide more context:

  • The setup worked flawlessly prior to the migration.
  • I do not experience this issue on PCs that were originally delivered with Windows 11 pre-installed.

Has anyone encountered this issue before or knows what might be causing it? Any advice or potential solutions would be greatly appreciated.

Thank you in advance for your help!

Best regards,

Visual Studio Extensions
Visual Studio Extensions
Visual Studio: A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.Extensions: A program or program module that adds functionality to or extends the effectiveness of a program.
275 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Michael Taylor 58,526 Reputation points
    2025-04-04T15:10:24.2833333+00:00

    In general issues with a VS extension from MS should be posted in the Developer Community. You'll potentially get a response directly from the team.

    For your specific issue it appears you may have custom actions in your installer. Furthermore your custom action is using .NET and most likely the version of .NET that your installer needs isn't installed and hence it cannot bind to the runtime. Check your installer to determine what version of .NET it requires and then ensure that the version is a prerequisite for your installer.

    I'm going to guess that your previous machine had a version of NET that the newer OS doesn't have. Note that all versions of NET 4.x use the same runtime so you should be fine there. What you're looking for is older NET frameworks perhaps.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.