I downloaded Windows 11 23H2 22631.3007's UUP files from UUP Dump, changed ConvertConfig.ini's "vDeleteSource=0" line to "vDeleteSource=1" and after creating the ISO, it has both Pro and Enterprise editions when it should only have the latter. Also, the Windows 11 installer asks for a key when it shouldn't since I already integrated KMS_VL_ALL_AIO.cmd into the ISO. Anyway, if I click "I don't have a product key" and proceed the install, Windows 11 says it's activated.
That cmd doesn't bypass productkey, it may auto activate after install/during OOBE. vDeletesource=0 doesnt delete source, changing value to 1 does.
How so, since previously it made Windows bypass it? After installong Windows 11, it's activated. My mistake. I meant I changed ConvertConfig.ini's "vDeleteSource=0" line to "vDeleteSource=1" and it still has both Pro and Enterprise editions and not only the latter.
While I don't have a log, I can confirm when it keeps both editions even after setting DeleteSource=1.
Have you done anything? I bet ei.cfg is or something else is missing. Personally I'd use official ISO It should delete source but I havent used UUP in a very long time so im lost
No, I didn't. I don't know if it has it but like @iFlaX said, we shouldn't have both editions but only one after using vDeleteSource=1. EDIT: Never mind what I said because integrating KMS_VL_ALL_AIO.cmd was bypassing the product key before.
You have to include the ei.cfg in the ISO:\sources folder. Open the ISO with a ISO mastering tool like Ultra ISO, add the ei.cfg file and save the ISO. Read my reply for once.
I was simply saying that previously I didn't need to do that and it was easier and faster. I don't even have UltraISO or a program like that installed. Are some of them freeware? I already did and it seems for now nothing can be done about it, like you said.
It needs to be fixed by @abbodi1406 in the mean time just use the SKU specifc ei,cfg to skip the key and sku questions. You can add the ei.cfg to the UUP project folder and it should be included in the ISO at conversion.
Why is it every time you get answers, explanations and solutions you never learn from it but are able to instantly ask new questions or show you have not got anything from the replies and this has been happening since 1703 was released many, many, many years ago?
Maybe because all of them don't have to do with the same subjects and some of my problems weren't even answered or the solutions didn't fix them? Also, how could I know vDeleteSource=1 and KMS_VL_ALL_AIO.cmd's integration were broken? Is it my fault as well?
Has been explained and answered twice, IT NEEDS TO BE FIXED BY THE DEVELOPER and has been reported to be not working. The solution is to use a ei.cfg and you were shown 2 versions, and you were informed how to insert them in a couple of ways, the easiest for you is to put it in the UUP>ISO project folder and it will be included during the conversion. KMS_VL_ALL $OEM$ folder works fine, as you can see in the GIF i showed, the install was activated by KMS_VL_ALL.
I ALREADY SAID I GOT IT. Since when replying "Like I said, I already used vDeleteSource=1 and I still get both Pro and Enterprise editions." to "Not deleting the source: Code: vDeleteSource=1 is reported to @abbodi1406 with logs." means I didn't read your reply? It must be my fault as well for it to be broken, since you always accuse me of messing up things. Again, in the first post I mentioned that the problem was the product key prompt (which, according to you, is fixed by integrating the ei.cfg's configurations you showed), not Windows 11 not being activated. Like I said in that post, previously, when integrating KMS_VL_ALL_AIO.cmd (and not touching ei.cfg, since I didn't even know what was it for, and if I knew and edited it, I would've mentioned it in the post), I wasn't prompted to insert a product key, and now I am. Now, who's not reading the other's replies? I'll use NTLite to create an ISO with just the Enterprise edition until ConvertConfig.ini's "vDeleteSource=1" is fixed. EDIT: It seems "ConvertConfig.ini's "vDeleteSource=1" was fixed but Windows 11 installer still asks for a key even after integrating KMS_VL_ALL_AIO.cmd into the ISO when it didn't previously and it seems this behavior won't be the same as before, at least in the near future. I'll have to skip that step and Windows 11 will be automatically activated after signing in to my local user account because of KMS_VL_ALL_AIO.cmd's integration.