[SOLVED] Why Windows 10 doesn't want to install .Net Framework 3.5?

[mrtech9]

I have windows 10 64 pro and it just doesn't want to install .net framework 3.5...

I tried offline with dism in cmd, without a luck,
I tried enabling windows update, I also tried something in regedit but basically nothing works. I feel like every windows update I try to install is rather so slow or stuck! I ran out of ideas and solutions...

Dism first time showed some error code and now it's just stuck at "Enabling feature(s)"

 

[britechguy]

If you're having issues even with DISM, the time has come to try:

Doing a Windows 10 Repair Install or Feature Update Using the Windows 10 ISO file

 

[mrtech9]

If you're having issues even with DISM, the time has come to try:

Doing a Windows 10 Repair Install or Feature Update Using the Windows 10 ISO file

Can you please take a look on my dism log file ? https://pastebin.com/fis0KxbK

 

[Calvin7]

Enable the .NET Framework 3.5 through the Windows Control Panel. This option requires an Internet connection.

1. Press the Windows key Windows on your keyboard, type "Windows Features", and press Enter. The Turn Windows features on or off dialog box appears.
2. Select the .NET Framework 3.5 (includes .NET 2.0 and 3.0) check box, select OK, and reboot your computer if prompted.

Then use Windows Update as the source for installing the .NET Framework 3.5.

 

[mrtech9]

Enable the .NET Framework 3.5 through the Windows Control Panel. This option requires an Internet connection.

1. Press the Windows key Windows on your keyboard, type "Windows Features", and press Enter. The Turn Windows features on or off dialog box appears.
2. Select the .NET Framework 3.5 (includes .NET 2.0 and 3.0) check box, select OK, and reboot your computer if prompted.

Then use Windows Update as the source for installing the .NET Framework 3.5.

Nope... Still getting stuck at "downloading required files". It takes forever!!!

 

[Colif]

Have you received this?

https://support.microsoft.com/en-au...kb4522738-cumulative-update-for-net-framework - I only got it 3 days ago even though its dated September.

 

[Colif]

I would try the repair install, it is likely fastest fix. All it removes are any patches released since 1903 was released, so you only have to download 5 things max to hopefully have a working version of win 10 again.

The newest version of win 10 due out in next few weeks so it might fix the .net problem.

 

[mrtech9]

Have you received this?

https://support.microsoft.com/en-au...kb4522738-cumulative-update-for-net-framework - I only got it 3 days ago even though its dated September.

I have received it, I installed it manually but for some reason it's still in my Windows Updates.

I would try the repair install, it is likely fastest fix. All it removes are any patches released since 1903 was released, so you only have to download 5 things max to hopefully have a working version of win 10 again.

The newest version of win 10 due out in next few weeks so it might fix the .net problem.

Yeah, I'm currently downloading with MediaCreationTool so we will see...

 

[mrtech9]

I started Windows 10 Setup and guess what! It freeze at "Checking for updates:46%", WINDOWS 10 IS A JOKE MAN.

 

[britechguy]

No, it's not a joke. Any operating system can end up with a corrupt installation. If a repair install is choking that's strongly suggestive of a particularly serious corruption in the existing installation.

When that's the case I take a full system image backup (because you want that just in case), separate backup(s) of user(s) data, then doing a completely clean reinstall (options a & b are downloadable PDF files):

a) Completely Clean Win10 (Re)install Using MCT to Download Win10 ISO File

b) Completely Clean Win10 (Re)install Using MCT to Create a Bootable USB Drive

c) How to do a CLEAN Installation of Windows 10 (Tom’s Hardware Forums, with screen shots)

I never choose the “thermonuclear option,” the completely clean reinstall, until it's clear that this is the only viable option. I hate having to go through all the work of reconfiguring a machine from scratch if that can reasonably and safely be avoided.

This appears to be an instance where "reasonably and safely be avoided" is simply not the case. If you start with a stable clean installation of Windows 10 then updates are generally very smooth. I've not had a permanent hitch with any of them on my systems, though there have been occasions where a given update will fail on the first try (sometimes even a second) but eventually goes through.

 

[Colif]

I started Windows 10 Setup and guess what! It freeze at "Checking for updates:46%", WINDOWS 10 IS A JOKE MAN.

you could always run the setup when not attached to the internet, it will skip the update phase then.

 

[britechguy]

you could always run the setup when not attached to the internet, it will skip the update phase then.

Indeed. Or one can answer the question near the very outset that asks if you want to check for updates now in the negative. I do that when I want to complete a repair install or Feature Update with all possible speed. Windows Update fetches the rest later.

In this case, though, I'd still be far more inclined to "tear off the band-aid" and go with a completely clean reinstall. All the indicators are that this will make life much easier, and Windows 10 on this machine more reliable, going into the future.

 

[Colif]

I don't know exactly when 1909 is due out, it could be a few days to x months, depending if any problems found. I mention that as this feels like de ja vu what i am about to suggest. I would hold off until 1909 is released and use the new ISO created for it to install win 10. Main reason I delay is if you put 1903 on now, knowing MS the update will come out a few days later and you will have to sit through update process again. I have been told its much faster now, I am just not sure how much by.

Its up to you, I suggested that last time and Microsoft delayed it and it took a month for guy to install. I don't have a crystal ball, I don't know what is going to happen tomorrow.

Any other time I wouldn't argue about a clean install being best fix. It can be time consuming if you not prepared for it.

 

[britechguy]

Well, my counterpoint to waiting is that virtually any Feature Update has a "shake out" period, even if what's being shaken out is fairly insignificant, and on the whole 1903 is well past that period.

I generally advise people who have working systems explicitly not to force any Feature Update, but to wait for Windows Update to present it. This is a sort of "reverse version" of that. I'd rather install a Windows 10 version that's known to be stable overall with the occasional "patch update bug" introduced here and there than with the brand new Feature Update that's more of an unknown quantity.

This is, however, strictly a matter of personal preference. There is no "wrong way" and a lot of it depends on the individual's tolerance for potential risk (or, more likely, inconvenience). As a now deceased friend of mine used to say, "You pays your money and you takes your chances!"

 

[mrtech9]

you could always run the setup when not attached to the internet, it will skip the update phase then.

So I did what you said, It skipped updates... I waited for about an hour and basically nothing changed. .Net Framework still doesn't want to install, Windows Updates still show some updates for some reason and they are stuck at 0%.

No, it's not a joke. Any operating system can end up with a corrupt installation. If a repair install is choking that's strongly suggestive of a particularly serious corruption in the existing installation.

When that's the case I take a full system image backup (because you want that just in case), separate backup(s) of user(s) data, then doing a completely clean reinstall (options a & b are downloadable PDF files):

a) Completely Clean Win10 (Re)install Using MCT to Download Win10 ISO File

b) Completely Clean Win10 (Re)install Using MCT to Create a Bootable USB Drive

c) How to do a CLEAN Installation of Windows 10 (Tom’s Hardware Forums, with screen shots)

I never choose the “thermonuclear option,” the completely clean reinstall, until it's clear that this is the only viable option. I hate having to go through all the work of reconfiguring a machine from scratch if that can reasonably and safely be avoided.

This appears to be an instance where "reasonably and safely be avoided" is simply not the case. If you start with a stable clean installation of Windows 10 then updates are generally very smooth. I've not had a permanent hitch with any of them on my systems, though there have been occasions where a given update will fail on the first try (sometimes even a second) but eventually goes through.

So you are saying that only option here is to completely reinstall whole system?

 

[mrtech9]

So I did what you said, It skipped updates... I waited for about an hour and basically nothing changed. .Net Framework still doesn't want to install, Windows Updates still show some updates for some reason and they are stuck at 0%.

So you are saying that only option here is to completely reinstall whole system?

Update: I finally fixed it by standalone installing latest kb4517389 and kb4524100 updates. Thanks for help everybody!