UPDATE: It looks like the issue might be a managed code custom action failing in the MSI in question (.NET code that can’t run – for whatever reason 1, 2, 3).
Suggestion
I would first try to 1) do the reboot I recommend below – to clear the air and release any locks – then 2) disable security software / anti-virus and 3) try the install and enable logging as described below.
Core Deployment Problems
As deployment goes, problems tend to center around: 1) something is locked (in use – by other processes or other users logged on), 2) something is blocked (access / permissions denied), 3) dependencies are missing for your custom actions or the whole installer (runtime requirements not satisfied – for example missing .NET runtime version), 4) something is corrupted (data file, OS settings, malware is often the culprit here – or unwise tinkering), 5) there is an unexpected system state such as the disk being full, or more exotic the date and time is wrong, or there is a licensing issue or some other oddity, etc…
That is a very simplified list of causes – there are obviously many further issues, for example 6) localization errors: hard coded paths, erroneous parsing of dates and time, invalid characters in path names, etc… 7) file and path names are too long, 8) and the Microsoft specialty: weird and unexpected incompatibilities between products not thought to have a valid reason to conflict with each other (different versions of Visual Studio, etc…), etc…, but that is going way too far for your problem. Still, here is a generic “deployment problems” summary from some time back – just for reference.
Procedure
-
Reboot: The first thing I would do is to reboot and then try to invoke the install the regular way. This is just to rule out this “simple solution” (which sometimes works). There could be files in use that the installer must replace in order to complete.
-
Logging: In order to maximize the available debugging information you could log the install with verbose logging and debugging information (if you have access to the MSI itself).
- Open an elevated command prompt (right click and run as administrator)
- Change current directory (cd) until you get to:
C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualStudio.AspNetDiagnosticPack.Msi,version=15.0.40314.0\ - MSI Log: Run this command (adjusting paths as appropriate – especially for the log file):
msiexec.exe /i AspNetDiagnosticPack.msi /L*vx C:\Test.log- Enable All: You can enable logging for all MSI files (slows installs, but great for advanced users): http://www.installsite.org/pages/en/msifaq/a/1022.htm (section: “Globally for all setups on a machine“)
- Interpret: How to interpret an MSI log file: http://www.installsite.org/pages/en/msifaq/a/1045.htm
- Event Log: You can also have a look in the event log. Rather than repeating the procedure here, I will link to a similar, recent answer.
-
Different User: This is unusual advice (and I haven’t tried it), but sometimes you can succeed with difficult installs by creating a new local admin user on the machine, and then running the installer from there. It has to do with errors in the user profile. Not the first thing to try, but adding it as an option.