Microsoft .NET Framework 4.8 for Windows 7

[sweden8]

My bad luck. But I thought here was the right place to ask.

Thanx anyway

[MAXtoriX]

https://www.microsoft.com/en-us/download/details.aspx?id=50395

WMF 5.0 requires Microsoft .NET Framework 4.5 or above. You can install Microsoft .NET Framework 4.5 or above by following the instructions at Installing the .NET Framework.

Question is: If we have WMF4.0 integrated and addon added to the image, can WMF5 (PowerShell5) be integrated also in an offline image?

[abbodi1406]

Yes

but technically, WMF can be integrated without .NET 4.5, but will not function
 

[naifle]

После интеграции, есть надпись. Вы можете удалить его или нет?

Edited June 30, 2016 by naifle

[naifle]

After integration, there is such a record. You can delete it or not?

[abbodi1406]

Yes you can
 

[abbodi1406]

Updated

[nonspin]

I'll make it short:

DO NOT TOUCH THIS ADDON.

Why? For example, have look into "NDP461-KB3154529-x86-x64.reg"

This is just one sloppy piece which is capable of cross-contermining systems.

The .reg contains ABSOLUTE PATHs, "C:\windows\". Now what will happen if

you setup windows on D: -- next to your current one ?.
How long will it take to screw up BOTH systems, because trying to clean the

setup on D:\ also screws with c:\

Now what are the odds, since the author couldn't be bothered to use %windir%,

that everything else is as sloppy ?

 

I'll advice everyone to setup chocolatey at at startup batching everything

crucial - like "choco inst powershell" would deal with everything:

removing wMF4, insfalling WMF5, DOTNET4.5 and Powershell 5..

 

[bphlpt]

@nonspin,

The tone in your post is uncalled for.

While your point that it would always be better to use paths such as %windir% rather than absolute paths like "C:\Windows\" is valid, taking such an antagonistic tone will do nothing but get you banned if it continues.  abbodi1406 is an extremely well respected member of this and many other technical forums and he has many abilities and a willingness to help others.  Every application author, including MS I'm sure, has published product using absolute paths at one time or another.  It would have been much better if you had merely asked whether there was a particular reason why absolute paths were used and whether it would be possible to rewrite the addon to use paths such as %windir% instead.  In any case, I'm sure that abbodi1406 will respond when he sees these posts.

Cheers and Regards

[djtomdabomb]

I have a question.

Can i overwrite current framework addon with newly updated version? or does it have to be a fresh install?

 

Cheers,

[abbodi1406]

You can, but i think it would cause confliction issues
and you will have two entries in "Programs and Features"

------------

as for the absolute path "C:\Windows\" in addon, this is restriction be microsoft
already tested, you can change some to %windir%, but changing them all will cause the pack to have errors or fail
some REG_SZ values will not take variables

other than that, Windows OS always defaults and recommended to C:
whom want to force other drive letter, should expect errors
 

[naifle]

NET Framework 4.6.2 Final

[abbodi1406]

Updated

[sweden8]

Big thanx abbodi1406. I will try it out soon.

 

Forgot to ask..  Does the 4.6.2 Final addon replace any separate updates?

Edited August 3, 2016 by sweden8

[abbodi1406]

It should replace all .net 4.6.1 updates, but i didn't verify that online

[X-Force]

4.6.2 replace all 4.6.1+Updates. Tested, windows update not list any dotnet update.

[abbodi1406]

Updated .NE 4.6.1 addon

since no update for .NET 4.6.2 so far

[sweden8]

Thanx, will try it out this week.

 

Worked just fine!

Edited November 25, 2016 by sweden8

[naifle]

KB3205379 

[kansv]

Hi, can we expect in the near future to update KB3205379 for .NET 4.6.2 ?

[abbodi1406]

It's tiny update

nonetheless, i'll see if i have time to update both
 

[mario288]

Having some issues integrating the addon. I have an error stating that "Windows could not configure one or more system components....". Screenshot below. However looking at the setupact.log (again listed below), I cant seem to find the reasons why. Could you assist me in determining why I am getting this error?

Screenshot of error dialog

Error Log

[abbodi1406]

I did not find any error in the log either

did you integrated any updates? WMF?
 

[mario288]

Hello,

I have already slipstreamed windows updates from WUD update list located here  using the WUD downloader. Everything has been slipstreamed accordingly without errors. Once I attempt to integrate this addon there is this issue. I have also tried to use an original SP1 image as well and that has given me the same issue. The screenshot and error log is located below.

Screenshot of error dialog with cmd prompt

Error Log 2

Any ideas as to why? Thanks.

Edited January 22, 2017 by mario288
Wording

[abbodi1406]

Sorry, i never experienced such issue, and the log does not list any related error

i'll do a test install with updated image to see