- Downloaded
- 510.5 GB
- Uploaded
- 24.5 TB
- Ratio
- 49.16
- Seedbonus
- 27,587
- Upload Count
- 1 (1)
Member for 6 years
Glad you solved it. For future reference and for others to know, the solution was easy.
All you had to do is change that registry value to either 4.6.20042 or greater, or make VS not check for the version of .net by deleting the "RequiredNDPVersion"="4.6" line in the pkgdef file.
Alternatively, you run VS studio setup, and before installing, click modify, and remove under ASP.NET the .net framework(s) and wait for VS to remove them. After that, close and re-run VS Setup and again, click modify and add both .nets (4.6 and 4.6.2) and that would solve the problem.
The issue pops because of some .net installers (especially the preinstallation ones) install the key NOT in
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\XXX]
but in
[HKEY_LOCAL_MACHINE\WOW6432Node\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\XXX]
and so VS cant find them.
Either way, enjoy coding
All you had to do is change that registry value to either 4.6.20042 or greater, or make VS not check for the version of .net by deleting the "RequiredNDPVersion"="4.6" line in the pkgdef file.
Alternatively, you run VS studio setup, and before installing, click modify, and remove under ASP.NET the .net framework(s) and wait for VS to remove them. After that, close and re-run VS Setup and again, click modify and add both .nets (4.6 and 4.6.2) and that would solve the problem.
The issue pops because of some .net installers (especially the preinstallation ones) install the key NOT in
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\XXX]
but in
[HKEY_LOCAL_MACHINE\WOW6432Node\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\XXX]
and so VS cant find them.
Either way, enjoy coding
Last edited:
