New
#70
Last edited by wen; 13 May 2017 at 05:35. Reason: Update
Hello,
I have checked the bootmanager and boot menu issue you mentioned and from what I was able to see this is no longer an issue. I was able to boot into my three other boot menu entries (Windows 14393.1198, Windows 15063.296 and Macrium Reflect System Recovery) without any issue.
My intent when I made the post was to share with other members the fact that there is at least one other way to install Windows from a mounted ISO.
Whether this procedure that I outlined results in a clean install is still not totally clear to me. I doubt that MS would call it a clean install. That is why I went back and edited my original post. I am going to call the procedure I outlined a fresh install. People can call it whatever they want. It is what it is. I think the true sense of the term "clean install" gets lost in the semantics. But, man it sure acts and feels like a clean install.
Hi,
Yes, sure. It's a good idea which will serve its purpose for some I'm sure.My intent when I made the post was to share with other members the fact that there is at least one other way to install Windows from a mounted ISO.My intent when I made the post was to share with other members the fact that there is at least one other way to install Windows from a mounted ISO.
It is by all means a clean install. One with a twist but who cares ?doubt that MS would call it a clean install.
And thank you for bringing it up, it may be usefull to some of us.
Cheers,
You can apply with DISM (or IMAGEX) from any functional install.WIM (.ESD) to a clean formatted partition(x:) from within a running Windows 10, 8.x or 7 installation and add the applied volume to the Boot menu with BCDboot x:\windows. You can also remove the current boot menu entry with BCDEDIT so that only the newly applied volume will boot.
Then all that is needed is to remove (or format) the old Windows volume after rebooting.
For me, word Clean in clean install refers to primary OS on a clean disk, to start fresh with partitioning options. Wipe the disk and clean install.
It's true that running Windows Setup from ISO, be it self made, a WIM based ISO Microsoft offers to Insiders, or ESD based ISO made with Media Creation Tool has an option to delete everything and reinstall Windows but this option does not include partitioning options as a pure clean install does.
It is also true that you can install or deploy additional Windows to dual / multi boot system in addition to primary OS from mounted ISO. This, of course, is also a clean install but not in same sense.
OK, that now being said, booting my machine this morning my screenshot tool Screenpresso notified me about an update. Accepting it the installer told it needs to download .NET Framework 3.5:
This seems not work in 16193, WU failing when trying to install feature:
The error is shown also when trying to add .NET Framework 3.5 from Add or remove Windows features.
If you face the same issue, a legacy Win32 app requiring version 3.5, just mount Windows ISO (16193 in this case), open an elevated Command Prompt / PowerShell, and run following command to install 3.5 manually replacing drive letter with actual letter for your mounted ISO. In my case Windows 10 build 16193 ISO was mounted as drive H:
Dism /online /enable-feature /featurename:NetFx3 /All /Source:H:\sources\sxs /LimitAccess
This installs .NET Framework 3.5 without issues:
I was now able to update Screenpresso.
Kari