Instead of replying you should just try the decrypter, i am beginning to remember we went thru this in the past.
I tried it with success but which option should I choose to get a less bigger ISO? Yes, thanks to the other user who told me to follow a different path that made me spent hours when following this one I can get things to work in a matter of minutes.
As I said before: The problem here lies between the computer and the chair (i.e. you). Funny how you, yet again, play the victim here in your response. And every instruction you're given works perfectly fine; however, it's no one's fault but your own that a) you do not make backups to revert to a previous point in case you have a problem, and b) you try a bunch of hokey methods for doing what you want instead of the actual proper way to do something.
Actually, like before I did the exact same thing and now it worked so why is it my fault? How can I update a Windows 10 Enterprise 1607 x64 to a Windows 10 Enterprise 1703 x64 since it doesn't appear as an update in Windows Update and Windows 10 Upgrade Assistant doesn't support Enterprise? I've been waiting for months for Windows Update to show it as an update it and to install it and nothing happened. Also, I tried running directly setup.exe from a Windows 10 Enterprise 1703 x64 ISO and it asked me if I wanted to remove everything or keep the personal files but not the settings and apps when I want to keep not only the personal files but also the settings and apps and I can't choose that option. What settings is the setup talking about? EDIT: Now I can't activate my Windows and Office. When I open KMSpico it says: "Key no found" "Error: You need reinstall Office 2010 or Open It the firts time" EDIT 2: I successfully reactivated Windows and Office by using KMSAuto Net.
Someone here made me spend extra hours customizing my install.wim image because they reported that DISM Scan/RestoreHealth bug related to TestRoot package was fixed in the latest Cumulative Update, but it was not! What is interesting is that ScanHealth reported no corruption when my custom images were scanned offline, but once OS was installed, DISM would fail every time. I only realized that it was still that TestRoot package that was the problem when I installed original age and updated it - DISM failed in that case too! It also failed when separately mounted source image directory was used as the reference image. Is MS staff out of their minds? Just about every issue reported on MS Tech support forums gets replies from MS staff that recommends running SFC ScanNow and DISM Scan/RestoreHealth to resolve problems... How can they not be aware of the major issue related to that package and not fix it?
As shown here, the /restorehealth command works: https://forums.mydigitallife.net/th...te-final-15063-pc.73650/page-175#post-1347909
RestoreHealth did not work for me - I tried that in with/without scratch directory and with/without reference image specifications. Once TestRoot package was removed - ScanHealth reported 0 problems.
The install i tested it on is a fully uptodate 15063.332, it only has dotnetfx3 pre-enabled and MS DaRT integrated, not any other tweak or modification done on it, it works...
Greetings to all, please someone could help me find a site to download these isos ... in advance grateful with those who collaborate ... SW_DVD5_Win_Pro_10_1703_32BIT_Spanish_MLF_X21-36771.ISO SW_DVD5_Win_Pro_10_1703_64BIT_Spanish_MLF_X21-36772.ISO
Enthousiast Thank you very much for responding ... please could you help me convert .esd to iso ... some manual that you have ... grateful for your collaboration ...
Abbodi1406's ESD>ISO v28 converter can be found at the OP, https://forums.mydigitallife.net/threads/windows-10-esds-repository.59082/#post-992731 Just drag the .esd file and drop it on the "decrypt.cmd" and follow the screens, it's really all self explanitory.
Don't you know anything, everything said here in MDL, it's just LAW? All M$ products are reliable and trouble-free, do you agree? Okay?