Question

Today I needed to re-install Microsoft Pex on my develop machine.

I'm using Windows 7, 32 bit, Visual Studio 2010, .NET 2/3.5

I launched the usual installer, but it stopped with a mysterious 2753 error.

How can I proceed with the installation?

Was it helpful?

Solution

The solution is:

  • From the command line launch "regsvr32 vbscript.dll".
  • After a few moments the message "DllRegisterServer in vbscript.dll succeeded." will appear

I hope this could be a solution for other people.

OTHER TIPS

Verify if OS version is compatible with SDK version.

Trying to install Windows SDK 8, I had the same error code. The problem occurred because my OS version is 8.1.

The documentation for error 2753 is fairly explicit:

"The File '[2]' is not marked for installation."

And typically you get it when you try to run a custom action based on a executable file that you're not installing or is absent for some other reason. If the file is in a feature or component that is not being installed and you call it as a CA you get this error. If the version of the file on disk is higher than yours in the MSI then yours won't be installed so you'll get this error because the exe you explicitly wanted to run as a CA didn't get installed.

I had a similar 2753 error when trying to install Windows SDK for Windows 8 on Windows 10.

Then I see from the above link this:

Supported operating systems

Windows 8, Windows 7, Windows Server 2012, Windows Server 2008 R2

So I decided not to hack around and use Windows SDK for Window 10.

The error is gone.

When updating "Microsoft Azure Information Protection" with the "Software Center", I had this error as detailed below:

The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2753. The arguments are: adxregistrator.exe

More precisely, the error was:

Error 2753: The File 'adxregistrator.exe' is not marked for installation.

To investigate this error, I downloaded Microsoft troubleshooting tool.

This allowed me to detect two instances of "Microsoft Azure Information Protection". I troubleshooted and uninstalled both.

After rebooting my PC, the application update succeeded with the Software Center.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top