Reply to thread

Message

<blockquote data-quote="Mat Walker" data-source="post: 1302546" data-attributes="member: 148753">100% my bad - as expected <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /> So, I had disabled the Windows Update service.&nbsp; Not a wise move, until MP all installed and working nicely.&nbsp; 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.&nbsp; W10 has V4.0 but not 3.5.&nbsp; 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'.&nbsp; And dont frig with W10 until MP is installed and happy.</blockquote>

[QUOTE="Mat Walker, post: 1302546, member: 148753"] 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. [/QUOTE]

Verification