Fun fact: If you speak out a certain word (no matter which one) many times, it starts to lose sense and sounds silly, eventually. Lol.
I created an .iso that combines v1803 retail editions (Home & Pro x86-64) and VL editions (Education & Enterprise x86-64) -- combined to a single .wim image. During Win10 setup, I get the following error only when I attempt to install the Education or Enterprise editions. Research leads me to believe this is caused by the installer not seeing the "license" in the .wim image for VL Education & Enterprise. Does anyone know a way to get around this issue? If this is the wrong thread, please point me in right direction
My initial ei.cfg file had this... Code: [Channel] Retail I have since adjusted it to your code above and still get the same error only when I attempt to install Enterprise or Education (Home & Proffesional work fine).
Yes I figured that obviously would be the case but was worried it would negatively affect the retail Ed. images. But I have since figured my issue out. Thnx
I got it by using some of the previous IP range ISO's (uup>iso) and when using original MSFT MVS iso's at clean install. Restarted the install (clean install) and it didn't occur at the re-install.
I have no idea about what you are saying. What i'm basically trying to do is create a Windows 10 Pro en_us x64 Volume edition ISO.
You were talking about an OOBEREGION error, i responded it not occuring when i restarted the install. OOBEREGION error occurs during installation, not during iso creation.
I know the issue doesn't happen when creating iso. The steps you mentioned to fix the error was not clear for me. I thought the issue is with the ISO itself.
I was going to ask for help with this error but I figured it out. I remembered that I had similar issues with handbrake. For whatever reason some programs don't like my storage spaces mirror. Anyways, I thought I would just add this in case anyone has the same problem. Thanks for the tool. ============================================================ Creating ISO... ============================================================ CDIMAGE 2.53m CD-ROM and DVD-ROM Premastering Utility Copyright (C) Microsoft, 1993-2007. All rights reserved. For Microsoft internal use only. Scanning source tree (500 files in 33 directories) Scanning source tree complete (972 files in 86 directories) Computing directory information complete Image file is 4740612096 bytes (before optimization) Writing 972 files in 86 directories to 17134.112.180619-1212.RS4_RELEASE_SVC_REFRESH_CLIENTBUSINESS_VOL_X64FRE_EN-US.ISO 0% complete ReadFile failed (\\?\E:\PROGRAMS_TOOLS\Microsoft\SVF\esd-decrypter-wimlib-39\ISOFOLDER\autorun.inf, off=0 len=800 status=103) Error 87: The parameter is incorrect. Errors were reported during ISO creation. Press any key to exit.
Could anyone please explain the difference between Windows install ISO made from .ESD and the one directly downloaded from these tools? Apart from one fits on a DVD and the other (ESD) doesn't. Which method is preferred for end users? I notice that those .ESD files are a few months old, unlcear if they contain recent Windows updates? How about the ones downloaded from ISO DL tools? Are they up to date? Thanks, and sorry if this has already been explained somewhere, I don't know how to find the answer.
At the second post of this thread, where the ESD download links are listed, @abbodi1406 also publishes what updates are integrated. ISO's (with install.wim) don't fit DVD5 for many builds now, the ESD>ISO converted ones with install.esd will fit DVD5. Depending on the release or refresh ESD or not, the content will differe, also listed at the second post of this thread. For more info about the content, info about and download options, you can read the specific build thread, all listed here: https://forums.mydigitallife.net/threads/index-windows-10-builds.58404/
@abbodi1406 Your esd-decrypter seems to require a small update for naming .107 isos created from the new 17763.107 refresh .esds. Edit: Btw, what does adguard's decrypt-ESD.cmd actually do different to yours when it offers the option to "economy the iso" after selecting to create an install.esd compressed iso? Thanks! Update: At least on a consumer pt-pt .107 esd with all indexes the resulting iso file is about 28KB smaller with that option enabled.
esd-decrypter-wimlib v40 Updated label for 17763 refresh ESDs replaced cdimage.exe with oscdimg.exe (renamed)
Just one page back: https://forums.mydigitallife.net/threads/windows-10-esd-repository.59082/page-101#post-1481213 and probably at the second post of this thread And it's 17763.107 The current CU = 17763.134 https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-339#post-1481203