Afaik, the update i mentioned removes flash from the CP, if it isn't integrated, flash will remain in CP.
Got an error just now trying to create a new 19042.746 from uupdump. I have done this a number of times before (not this version, of course), with no errors. Any ideas? ============================================================ Creating install.wim . . . ============================================================ [ERROR] "\Windows\WinSxS\amd64_microsoft-windows-gpowershell-exe_31bf3856ad364e35_10.0.19041.1_none_ee822d264112a470\ise.psm1": blob not found SHA-1 message digest of missing blob: da8001f3cefdf302679044f6cdfb33f6976cb0e4 ERROR: If this is a delta WIM, use the --ref argument to specify the WIM(s) on which it is based. ERROR: Exiting with error code 55: A file resource needed to complete the operation was missing from the WIM. Errors were reported during export. Press 0 to exit. ============================= update - successful on second try. The only change was to choose "Feature update" instead of "cumulative update"
i have downloaded "Feature update to Windows 10, version 20H2 (19042.746) amd64". operation finished after 2 hours. but here is no iso image file. here is my ConvertConfig.ini Code: [convert-UUP] AutoStart =1 AddUpdates =1 Cleanup =1 ResetBase =0 NetFx3 =0 StartVirtual =1 wim2esd =1 SkipISO =0 SkipWinRE =0 ForceDism =0 RefESD =0 [create_virtual_editions] vAutoStart =1 vDeleteSource=0 vPreserve =0 vwim2esd =1 vSkipISO =0 vAutoEditions=CoreSingleLanguage,ProfessionalWorkstation,ProfessionalEducation,Education,Enterprise,ServerRdsh,IoTEnterprise .
Here are last lines of screen output Code: ============================================================ Creating Edition: IoT Enterprise ============================================================ Setting the WINDOWS/EDITIONID property of image 10 to "IoTEnterprise". Setting the FLAGS property of image 10 to "IoTEnterprise". Setting the DISPLAYNAME property of image 10 to "Windows 10 IoT Enterprise". Setting the DISPLAYDESCRIPTION property of image 10 to "Windows 10 IoT Enterprise". ============================================================ Converting install.wim to install.esd . . . ============================================================ Using LZMS compression with 4 threads Archiving file data: 0 GiB of 10 GiB (4%) done Errors were reported during export. ============================================================ Removing temporary files . . . ============================================================ Press 0 to exit.
@cengizhan ISO creation is skipped when errors occurs during building or exporting maybe i can add exception for install.esd failure i.e. if converting to install.esd failed, ignore and create ISO with install.wim
thanks. i have tried 3 times, all failed. i have created lots of iso images with uupdump but never had any problems until this one. maybe the computer has some errors. i will try with another computer today.
And show all progress, not only the last lines, please. Make sure there is plenty of free work space too.
i have 16gb ram and at least 500gb free space. there was nothing wrong with previous lines. only wim2esd part failed. i found in windows event log that wimlib-imagex.exe crashed, process interrupted and files have been removed before iso creation. i have tried with another computer with same files, and iso creation was successfull.
Hello guys, I need your help. I just installed Windows 10 IoT Enterprise, but I can't activate it. I'm trying with HWID_Activation, but it does not work. Any help?
MAS 1.4 should do the trick, or when a hwid for normal enterprise is already established IoT would take that one too, afaik. Why are you using IoT, it's the same as normal Enterprise but with less activation options.
Thanks for answering Sorry, but I don't know MAS 1.4... I'm just doing tests. I would really like to have the 19042 Enterprise LTSC version that could come through IoT
MAS 1.4 == Massgravel: just google "massgravel github" (without the quotes). Easy to find, easy to use. I have no idea whether it works with IoT. There is no such thing as "19042 Enterprise LTSC". Does not exist, will not exist, sorry.
Oh yes it can be found as a franken build, but only cosmetic and some changes here and there, just look at nsane. But not a real Enterprise LTSC 19042.
Not all release branches have an LTSC Edition. The latest branch having LTSC is the rs5 one (1809 aka build 17763), called Enterprise LTSC 2019 (EnterpriseS). The 20H2 19042 branch does NOT have any LTSC, they are only released once every three years or so. Also, LTSC has nothing to do with IoT, nor can it be exported/extracted. LTSC ISOs are always separate downloads and not meant for the public. IoT itself is just the regular Enterprise (SAC) with different licensing options. There can be an IoT Enterprise LTSC (as confirmed by MS), but I've yet to see one in the wild.
@Carlos Detweiller, Thanks for the clarifications! I was just curious about that possibility. But I will continue with my normal versions.
Not sure if this is the right thread to ask, but does generating an ISO using this site (pro with virtual edition enterprise) and with options of "integrate net framework 3.5" and "run cleanup after windows integration" break the monthly cumulative updates ? I've reinstalled a clean ISO back in december that was generated with those options (I am unsure whether i also set resetbase in convertconfig to 1 too) and been trying for days to get the january cumulative update to install but it always fails (done sfc scannow, dism repair, tried wumt, nothing helps). I've read in the manual for uupconvert that using resetbase option may break windows update since 18362, which again I'm unsure whether I used or not. If it helps I can provide logs of attempts to install the update (via windows update or dism) Since I will be doing a clean install on another PC my question here is whether it's safe to check those two options on uupdump website and it won't break windows update or should I err on side of caution and leaved them unchecked ? Thanks for your help