Win 10 Pro - 1.37 doesnt know .NET 4 already installed (1 Viewer)

[Mat Walker]

Just tried a new Client-only install on a clean Win10 Pro box. Installer doesnt realise .NET 4 Framework already 'installed' (part of Win10 afaik) and tries to install it - falling over as it is already installed.

Before I dive in to logs, is it a gotcha I've fallen into? Non-one else jumping up and down, so 99.9% sure it is something I've done, or not done! lol

(I made sure all OS updates fully installed b4 starting...)

 

[CyberSimian]

Just tried a new Client-only install on a clean Win10 Pro box. Installer doesnt realise .NET 4 Framework already 'installed' (part of Win10 afaik) and tries to install it - falling over as it is already installed.

I did a first-time install of MP 1.37 on my 64-bit Windows 10 laptop, and that succeeded. But that was for the server + client, and not client-only. However...

An update-install of MP 1.36 to MP 1.37 failed with a MariaDB error. Allegedly there is some way to fix the error, but it looked like too much effort to try to understand what was needed. So...

My recommendation to users who want a simple life is to perform a first-time install of MP 1.33 (32-bit or 64-bit, as you prefer), and then perform an update install from MP 1.33 straight to MP 1.37. In this way your MP installation will use the trouble-free MySQL, and not the troublesome MariaDB.

-- from CyberSimian in the UK

 

[CyberSimian]

Installer doesnt realise .NET 4 Framework already 'installed'

Just to clarify, installing MP 1.33 first will avoid a potential problem when at some future time you try to update MP 1.37 to MP 1.38.

Installing MP 1.33 first does not directly address the problem with NET 4 Framework, but it will probably avoid it (no guarantees).

-- from CyberSimian in the UK

 

[Mat Walker]

100% my bad - as expected

So, I had disabled the Windows Update service. Not a wise move, until MP all installed and working nicely. The reason it failed is because DotNetFrameworkChecker.cs looks in Registry HKLM SOFTWARE\\Microsoft\\NET Framework Setup\\NDP for v4/v4.0 AND v3.5. W10 has V4.0 but not 3.5. MP installer cleverly, quietly, tries to install 3.5 but the MS installer needs the Update service running - which it wasn't.

Enable to the Update service , and MP installer has a ball; all good.

Moral - Dont say it is a 'clean' W10 install when actually it is 'frigged'. And dont frig with W10 until MP is installed and happy.