I don't believe you can use the actual XML when using a deployed image. You could possibly do a registry mod if it is really bothering you where you modify the specific registry keys using a reg load/modify/unload of a mounted image. I would suggest an alternative though. You might see if you can bypass this online requirement another way. Perhaps you can simply disable internet while installing or perhaps there is a script you can download where you can shift-f10 and run it from the flash drive during OOBE.
Even disconnecting the internet, it asks to install a network driver, to connect the internet and create an online account, I think the only alternative would be to deploy a reg in install.esd, via ntlite, just one question, how is the deployment done? of the image, it doesn't need to be booted, would it be possible to just put the sources folder and install.esd?
Updated the custom installer script to auto-detect install.esd and install.swm files natively in the sources folder rather than just in dual architecture isos. It's a relatively minor change, but for people who are using isos with install.esd files, it should help you. You can download it using the link in the main project page: https://forums.mydigitallife.net/threads/murphy78-diskpart-and-apply-image-script.53532/ I've also re-uploaded older files for longevity in case anyone wants to download them.
hello sir thank you for the script 1.3.1 v2 have you modified the WinRE diskpart.txt because windows 11 sound update where if less than 600MB update error must be 1024 MB otherwise tell me how to do it please
Working Perfectly. Code: ============================================================ Add Muprhy78 Diskpart and Apply Image script to boot.wim originally by Enthousiast v1.3... ============================================================ An alternate winpeshl.ini can auto-run the diskpart/apply image script Would you like to replace the file in setup media? Y/N or Q to quit Y Extracting Source ISO... 7-Zip 19.00 (x86) : Copyright (c) 1999-2018 Igor Pavlov : 2019-02-21 Scanning the drive for archives: 1 folder, 1 file, 6733824000 bytes (6422 MiB) Extracting archive: Source_ISO\26100.2152.241004-1811.GE_RELEASE_SVC_PROD2_CLIENTMULTI_X64FRE_PT-BR.ISO WARNINGS: There are data after the end of archive -- Path = Source_ISO\26100.2152.241004-1811.GE_RELEASE_SVC_PROD2_CLIENTMULTI_X64FRE_PT-BR.ISO Type = Udf WARNINGS: There are data after the end of archive Physical Size = 6733318144 Tail Size = 505856 Cluster Size = 2048 Created = 2024-10-16 13:00:54 Everything is Ok Archives with Warnings: 1 Warnings: 1 Folders: 102 Files: 1056 Size: 6727587440 Compressed: 6733824000 Adding Murphy78 Diskpart and Apply Image Script To Boot.wim... Scanning "murphy78-DiskPart-Apply-v1.3.1\x64\" 601 KiB scanned (6 files, 4 directories) Using LZX compression with 1 thread Archiving file data: 601 KiB of 601 KiB (100%) done "WORK\Sources\boot.wim" original size: 655916 KiB Using LZX compression with 8 threads Archiving file data: 1556 MiB of 1556 MiB (100%) done "WORK\Sources\boot.wim" optimized size: 653950 KiB Space saved: 1966 KiB ============================================================ Replacing the winpeshl.ini - Script will run automatically ============================================================ Scanning "murphy78-DiskPart-Apply-v1.3.1\winpeshl.ini" (loading as WIM path: "\Windows\System32\winpeshl.ini")... 108 bytes scanned (1 files, 0 directories) Updating "\Windows\System32\winpeshl.ini" in WIM image Using LZX compression with 1 thread Archiving file data: 0 bytes of 0 bytes (0%) donene "WORK\Sources\boot.wim" original size: 655917 KiB Using LZX compression with 8 threads Archiving file data: 1556 MiB of 1556 MiB (100%) done "WORK\Sources\boot.wim" optimized size: 653950 KiB Space saved: 1967 KiB ========================================================= Creating x64 ISO... ========================================================= OSCDIMG 2.56 CD-ROM and DVD-ROM Premastering Utility Copyright (C) Microsoft, 1993-2012. All rights reserved. Licensed only for producing Microsoft authorized content. Scanning source tree (1000 files in 98 directories) Scanning source tree complete (1056 files in 103 directories) Computing directory information complete Image file is 6731399168 bytes (before optimization) Writing 1056 files in 103 directories to Win_26100.2152_x64_pt-BR_2024-10-16.iso 100% complete Storage optimization saved 66 files, 15788032 bytes (1% of image) After optimization, image file is 6718119936 bytes Space saved because of embedding, sparseness or optimization = 15788032 Done. Pressione qualquer tecla para continuar. . . Spoiler https://i.ibb.co/GsdKRrN/01.jpg https://i.ibb.co/rc4rg8D/02.jpg
Currently working on a v1.4. I have noticed that older OS versions were erroring out that I thought were working. For instance, the choice command was erroring out in win7 ultimate x86 sp1. As was the dism apply image function. This is integral to the script so I am working on adding these features in a way that can at least support win7 thru win11 plus the server versions that coincide with the release range of win7 and above. I may test vista sp2 but I'm not going to stress too much if it doesn't work. I want to add some future proofing to the recovery partition and lack of winre.wim functionality. Normal windows setup can detect a missing winre.wim from what I've heard and I want to try to mimic that to an extent with an option to disable the recovery partition extra file size increase and winrecfg function if the user isn't using a winre.wim in their install media. I also want to enable a feature of setting a custom recovery partition size. Normally the script was set to 500mb, which was a bit large when the script was last set that high but now it seems is too low for Win11. The future proofing I'm talking about would make it so that you could enter a size right when you're running the script rather than editing the script and copy/pasting over the x86 and x64 folder versions and integrating them. Long into the future I would like to figure out a way to somehow auto-size the recovery partition. I also want to try to manipulate the system into thinking the script is running on an en-US system for MUI file purposes as I think the system might error out if it has missing mui files for choice and winrecfg and the system is running on a es-es boot image for example. The script is in English and if someone wanted to modify it, they would need to provide the appropriate MUI files. That being said, doing this would at least make it possible for people to install on a system using a non-en-us image. They would theoretically just need to set the system back to their preferred language and keyboard style after install. I'll have to do some testing on this to see exactly what the deal is.
If you had a way to make a menu (1) Win7 (2)Win 8.1 (3)Win10 (4) Win11, direct each source_iso7 for example linked to the menu (1), but then you would have to create a universal boot, which would work for everyone, then I would only change install.esd inside the source_iso7 folder etc... I would only keep esd updated and it would work with all versions of Windows. It would work well with WindowsPE made with Windows 10 boot...
I assume you're talking about my optimized version of a windows PE that can just incorporate whatever install images you feed into it? While being able to install a bunch of different versions of OSes was always a goal, it was always also a goal to retain compatibility with the way Microsoft does things. That's why I use MS's official programs and only script to use them in order. To that end I want the script to at least be able to be used on official MS isos at all times. It might be nice to be able to feed a bunch of different official MS ISO files and create an AIO through an automated process, but there might already be an AIO maker out there. And if there is, you could just use the AIO result on this tool. I wish that MS had a universal install media myself, but they just don't. Their setup media is tied to their ISO files, which are tied to the build files. From my experience, with an AIO that mixes builds you have to use a newer build as the boot source and a script deployer like this one for the older builds. You can't even do a normal install on them because it will just error out on eulas or other things. Even file size is a limiting factor. It's why I gave up on my biggest AIO. The setup media just couldn't handle it. Even the dism script couldn't apply them without errors. Maybe it has something to do with chunk sizes or 32-bit or something. I don't know. People in the forum for a long time will know that I was going crazy about the errors for a long time before I gave up.
Yeah I've had similar issues and have had to use wimlib instead of dism (which is a little slower at deployment).
I have a friend who has a tool that he sells, he commented that 7 and 8.1 is very limited even in this part of the code, from 10 onwards it's easier...
Anyone happen to know a way to temporarily change a command prompt's language? I can find the OS lang with WMIC, but not set it. I can probably read and even set a registry key, but I don't know how to re-load the registry and the command prompt such that the changes would be applied. I guess there's probably some kind of way to reload a command prompt by using two scripts, but that still doesn't solve the issue of the registry not reloading. I seem to remember reading about this stuff when playing around with adding language packs but it's been so darn long. Also, I've never actually done it on the fly.
Language? You can select different codepages (international character sets) with the "mode" command. Example: Code: mode con cp select=437
I'm not quite sure what that does but I don't think it fools the system into providing English results for things like Dism queries. At least it didn't when I tried to use it before running the script on a vm.
Several utils from MS can be forced to English output, by using the /ENGLISH parameter on the command line. If DISM has it, no idea.
Great idea. I just realized that just before I reloaded this page. In fact dism has an /english parameter. This may be how I solve this problem. Edit: It seems to work. It got past the install, at least on a Spanish Windows 7 sp1 x86 image. It's a bit weird seeing the odd word in Spanish from the other utilities, but as long as it works, I won't complain. I would have thought that the choice.exe or the winrecfg.exe would have kicked out errors from not having mui files but I guess not. I won't pretend to try to understand why. Let's just hope it's because I got them from English sources and leave it at that. Spoiler
In fact, modified isos do not work in the tool, as you said, because it follows Microsoft standards, it does not accept modified isos.
As long as it uses a standard MS ISO as a template, it does work. It's why I created the script in the first place. I couldn't install my superaios any other way. BTW, I'm basically done with v1.4. I've been going all night on it though and I need to test it a lot more to make sure I didn't break anything else. Custom recovery partition appears to be working. Compatibility with windows 7 seems to be working, although that was much harder than it had any right to be. Compatibility with other languages seems to be working although I need to test at least a few other languages to be sure.
I appreciate the offer but I think it might be more trouble than help even if you notice a problem that I don't immediately. Maybe I get confused, eventually fix the issue. Then I send you another updated version. Then we have all these files with the same name floating around and when I do finally release the thing I might get even more people claiming that there's a problem but maybe it was already fixed. I think it's better if I go through the script and work on each section one by one and test each feature that I can test as best I can until I'm confident that it works to my satisfaction. It might take a couple days to test on all the different features and compatibility. I also want to mod the superaio v7 esd ver that @Enthousiast kindly uploaded for me with the latest ver and try multi-booting a bunch of different OSes.