I somehow managed to get around the boot loop (probably by updating all applicable drivers and cleaning all stale versions) but updating from .21 to .84 causes a login issue. I even tried an in-place upgrade with an update-integrated installer.
Guys,i've tried to create virtual version (proworkstation) but all the time create only the enterprice version. did anyone knows why? i want to make clean install the proworkstation version.
All works still the same, how exactly did you create Prof-WS, can you show the indexes inside the wim? These SKUs all originate from Home and Home N: Code: "Win 10 (2004 20H1) Home xx-XX (19041.84)" "Win 10 (2004 20H1) Home N xx-XX (19041.84)" "Win 10 (2004 20H1) Professional xx-XX (19041.84)" "Win 10 (2004 20H1) Professional N xx-XX (19041.84)" "Win 10 (2004 20H1) Education xx-XX (19041.84)" "Win 10 (2004 20H1) Education N xx-XX (19041.84)" "Win 10 (2004 20H1) Pro-Education xx-XX (19041.84)" "Win 10 (2004 20H1) Pro-Education N xx-XX (19041.84)" "Win 10 (2004 20H1) Pro-Workstation xx-XX (19041.84)" "Win 10 (2004 20H1) Pro-Workstation N xx-XX (19041.84)" "Win 10 (2004 20H1) Enterprise xx-XX (19041.84)" "Win 10 (2004 20H1) Enterprise N xx-XX (19041.84)" "Win 10 (2004 20H1) ServerRdsh xx-XX (19041.84)" Some languages will also have CoreSingleLanguage.
I've download the pro and home edition only and then i'll try to make virtual version with the scrit inside the folder or did i make somethink wrong?
Please specify the info, did you use uup dump or another script? For uup dump convertconfig.ini (used by create_virtual_editions.cmd) to create enterprise: Code: [create_virtual_editions] vAutoStart =1 vDeleteSource=0 vPreserve =0 vwim2esd =0 vSkipISO =0 vAutoEditions=Enterprise will create Enterprise as additional SKU to the base ones.
the uup dump i use but now i've see that i must use the third script to create virtual edition sorry for the upset.
It actually is 20H1. https://forums.mydigitallife.net/th...pc-slow-vb_release.80763/page-33#post-1578545
It is 20H1 indeed, but at the same time Microsoft gave it a name already, even if it is still in IP Slow Ring.
This is the same as before, MSFT releases a build to devs first, next to the oem's and GA. Iirc it was with 17763.1 "released to devs" first, now for 19041/2004/20H1 it gets that stage for a few months before GA.
I left it for hours but it froze 2 times at different stages and nothing happened. The third time I launched it, it finished and created the ISO. Nevertheless, it took about 2 hours for it to complete on SSD, didn't know it would take that long
That phase should just take a minute or two max, the whole process can take ages, depending on the used hardware.