I thought the problem that was happening had been resolved. The new version on September 4, 2023, with the recent problems, doesn't help at all? I use wimlib to commit, optimize or export the images, but I use ms imagex to mount them.
Nothing to worry about, if there was nothing to do everything would fall into disuse. I know a calculator dev who only changes the version to make it look like he's updating, because the downloads are so low in the store, every now and then he updates something regarding compatibility with new versions of Android. But I have no way of checking if it's true - closed source. Good thing we always find something to improve. I always say that a 10 or an A grade does not exist (in various places the way test grades are classified is different). If I get a 10 (highest grade) on something, I don't worry about making improvements to what was already considered great. This demotivates me. So I always know that a maximum grade is a lie, hehehehe But that's just me, everyone motivates themselves or is motivated in different ways. Now returning to the subject of ISOs. I don't think it's interesting to put wimlib in system32. Maybe add the path in EnvPath. In the last few days I have had problems with some tests on a virtual machine. But I didn't relate it to wimlib. I'm going to do these tests. I was thinking it was related to the integration of new updates for 22631 23H2. I was waiting for next Tuesday while I update IMCK and check if there are more things to do with the integrations (UUPdumpApp and W10UI). Even though I integrated W10UI, I still haven't done a complete ISO to redo the tests on the VM. If I have problems, I'll report them here so everyone knows. I will also reintroduce the dism commands as an option for users who want them. This way it even makes testing easier.
Yo!! I just found this repo up on Github now I see here on MDL/Scripting as pinned Thread.. Makes perfect sense, as so useful! What an excellent collection of Scripting resources! TYVM!!!
How do i stop these "C:\program Files (x86)\Microsoft" "C:\program Files (x86)\Microsoft\Edge" "C:\Program Files (x86)\Microsoft\EdgeCore" "C:\Program Files (x86)\Microsoft\EdgeUpdate" "C:\Program Files (x86)\Microsoft\EdgeWebView" being added to uup build when using uup converter...
@abbodi1406, I was reading the W10UI code, and when we call the script also passing parameter 4, it could be used so that UpdtBootFiles=1 could identify the "Windows Setup Media" and do its job by updating the boot files. But from what I saw, the "Target" variable receives the "cmd_target" argument and also, the "Target" variable is used to identify the "Windows Setup Media", but it does not find any .wim to validate the path, since "cmd_target" is a mount point. I don't know if I understood the logic correctly, maybe I confused something. But could you check that out? Thnks, man!
Yes, that's what I meant by "Windows Setup Media". There's no way I can pass the path to my folder by calling the script, that would be very useful. Simply taking advantage of sending parameter 4, within the script it is defined whether it will be used to find something in sources like netfx3 cabs or whether it will be used to targeting updates for the boot files.
W10UI v10.36 - Improved iso label accuracy for Enablement Package fake builds - Fixed accidental endless loop when AutoStart=1 and Target/Repo are not detected - Update boot files when W10UI.cmd is called from W10MUI.cmd
Hey mate, uup-converter still is not including "ei.cfg" file in the created ISO. I have tried naming the file "ei.cfg" and "EI.CFG" but no dice. I can't say for sure that this is specific problem for me since I do not get any error while running the script. Also tried placing the file with the script itself (outside of uup folder) but no luck. Can you kindly look into this? Thank you.
It actually does, when the ei.cfg is in the root of the project folder aka next to the convert-UUP.cmd it copies it to the ISOFOLDER, waiting for the ISO to be created... Spoiler: ei.cfg is included in UUP>ISO ISO
Thanks for testing mate. Can you test if the script also works when the file is named with all capital letters like "EI.CFG"? I do recall that I tried placing it with the script as you mentioned but it still didn't work. Now either there really is something wrong with my windows install or letter case does matter.
That should not matter, if it is in upper case or lower case but i will test Make sure you use UUP>ISOv93 or up.
I've put the EI.CFG in and it already shows up in ISOFOLDER but because it is copied as ei.cfg it now is lower case, iso is being created.
Thanks a lot for testing @Enthousiast Something's definitely wrong on my end . Guess I better use that newly created ISO for a clean install .