3.2 installer mistakenly thinks VS2017 setup failed, no way to override this

I updated VS2017. It said I needed a restart and I restarted. Once restarted, it was already finished installing and ready to go.
At no point did any error message show up, nor was there any sign of failure.

So, after the restart, I ran the NCrunch 3.2 installer. It maintained that the VS install ended prematurely due to a failure and it is impossible to install.

To cope with this I tried modifying the VS2017 installation. I added a workload which I wanted. The installer completed successfully, no restart needed.
Tried NCrunch again. NCrunch still maintained that the last setup failed.

I'm currently trying a fullblown VS2017 repair.
I'll let you know if this works, however, I should not have to be doing this instead of getting work done.

Hi, thanks for sharing this issue.

Do you still have the error message that the NCrunch installer was giving you? The NCrunch installer is mostly just an xcopy MSI into the VS directory. The error you've described doesn't seem like any of the error checks that are manually coded into the MSI.

Since it is still in pre-release, the VS2017 installer is not especially reliable. I had problems with it myself. MSIs themselves are also not 100% reliable, which is why there is also a manual installation option for NCrunch (see http://www.ncrunch.net/documentation/manual-installation-instructions).

Yes, I'm still having the problem. I didn't think of manual installation. I will do that, thanks!

This is a brand new installation of Windows. I needed to build for net20, so I went to "Turn Windows features on or off" and checked the .NET Framework 3.5 box.
Then I restarted. Then on a whim I tried the NCrunch installer again and it worked fine.

I hadn't run the VS installer before or after restarting the computer this time, so I have no idea why this unblocked the installer.

jnm236 wrote:This is a brand new installation of Windows. I needed to build for net20, so I went to "Turn Windows features on or off" and checked the .NET Framework 3.5 box.
Then I restarted. Then on a whim I tried the NCrunch installer again and it worked fine.

I hadn't run the VS installer before or after restarting the computer this time, so I have no idea why this unblocked the installer.

Ahh. Ok, this all makes sense now.

This is a known problem with the v3.2 installer. It was built with a component in the MSI that has a dependency on .NET 3.5, so if you try to run it on a machine without .NET 3.5 installed, it fails to run. This problem is fixed in v3.3 and will also be fixed in all future builds.

Beautiful!