The New Edge is a stand alone Product BUT Updates will be on Windows Update. It is NOT tied to any Windows 10 Version.
I had seen that it would be "integrated" in the next Windows (20h1) like Edge and IE It is therefore not possible to integrate it into ISO (1903/1909)
FYI When using W10UI_7.7 awhile ago to create an updated W10 LTSC 2019 iso using today's posted updates, when almost completed, Malwarebytes 4.0.4.49-1.0.14562 decided that W10UI_7.7 was RANSOMWARE and Quarantined it... This, of course, stopped DISM from completing its task... I subsequently made an EXCLUSION in Malwarebytes 4.0.4.49 to exclude the C: W10UI_7.7 folder and QUIT Malwarebytes to ensure it would NOT interfere on my 2nd attempt... After all was said and done, W10UI_7.7 completed and created an updated W10 LTSC 2019 iso... Last month on Patch Tuesday, I used W10UI_7.5 and the previous Malwarebytes 3.8.3.2965-1.0.613 release... Therefore, I don't know whether W10UI_7.7 or Malwarebytes 4.0.4.49 caused this ISSUE...
It's not the script what triggered the MBAM actions, it's what was done on the mounted wim, @abbodi1406 mentions that AVs can interfere.
It just seems ODD to me that this has never occurred in all the years I've been using W10UI_x.x... I have never disabled Malwarebytes to use W10UI_x.x...
A combination of an infrequently occurring application rapidly modifying files likely triggered a ransomware heuristic detection.
My host is LTSC 2019-x64 I suspect this is Malwarebytes related, since W10UI-7.7 and previous use DISM commands... Either the NEW Malwarebytes 4.0.4.49 or an update to the database... When MBAM quarantined W10UI-7.7, it was at the stage where it was processing BootWim-2 after it had been mounted...