New
#31
I didn't know you could specify an ESD as the repair source - I've always used a WIM.
If you don't know for certain, that might be why you're not getting good results.
If you know for a fact that Dism can use the ESD - cool, I learned another thing today.
You have two choices if you want to try again with a WIM.
- Use the Win10 Media Creation Tool (MCT) to download the Win10 ISO.
Select the proper bit-depth for your machine's architecture (MCT & ISO)
Select the OS that matches what is on your machine (Home, Pro, ...)
Select Create installation media for another PC
When the download completes (it took about 20-30 minutes on my average speed cable), press Finish - you don't need to put it to external media (DVD/Flash) yet.
You can burn it later or use Rufus for a flash drive.
Download the Windows 10 Media Creation Tool
More info: Installing Windows 10 using the media creation tool - Windows Help
- Convert the ESD to an ISO
See: ESD to ISO - Create Bootable ISO from Windows 10 ESD File - Windows 10 Forums
In both cases, you just want the ISO for now. You can mount the ISO and use that as the repair source.
There's no guarantees though since your machine seems to have issues with Dism.
I'm glad you waited, I was only trying to see what your machines had enabled, not suggesting to make any changes - thanks.
As essenbe said, you only need it enabled if software requires it. I don't know enough about your machine.
Leave ASP NET 4.6 disabled.
The image you posted answered the question I had - .NET 3.5 is enabled. The information I found, re: the original SFC error, points to .NET 3.5 - try disabling that as a test and running Dism without the source parameter.
- if you need .NET 3.5, you can re-enable it later.