murphy78 DiskPart and Apply Image Script

Discussion in 'Scripting' started by murphy78, Apr 2, 2014.

Page 14 of 16

murphy78 MDL DISM Enthusiast

Nov 18, 2012

7,434

11,773

240
#261 murphy78, Jul 21, 2021 (OP)
Chibi ANUBIS said: ↑

Hi @murphy78 ! So we can integrate and use DaRT in boot.wim and winre.wim with your new script ?
Click to expand...

@Enthousiast made an integration script for DaRT integration. I haven't gotten around to testing it yet.
Here's the post: https://forums.mydigitallife.net/th...ion-guide-murphy78.47875/page-43#post-1496205

Bira MDL Senior Member

: Oct 4, 2017

: 318

: 183

: 10

#262 Bira, Jan 25, 2022

Hi Murphy78, how are you?
doing here some identities in your script in my language I saw that, I do not know can be mistaken my, in these parts

Code:

:IMG64
FOR %%i IN (Z Y X W V U T S R Q P O N M L K J I H G F E D C B A) DO (IF EXIST "%%i:\x64\Sources\install.wim" SET INSTALLIMAGE="%%i:\x64\Sources\install.wim"&GOTO :SETUPCHECK)
FOR %%i IN (Z Y X W V U T S R Q P O N M L K J I H G F E D C B A) DO (IF EXIST "%%i:\x64\Sources\install.esd" SET INSTALLIMAGE="%%i:\x64\Sources\install.esd"&GOTO :SETUPCHECK)
FOR %%i IN (Z Y X W V U T S R Q P O N M L K J I H G F E D C B A) DO (IF EXIST "%%i:\x64\Sources\install.swm" SET INSTALLIMAGE="%%i:\x64\Sources\install.swm"&SET SPLIT=1&SET SPLITPATTERN="%%i:\x86\Sources\install*.swm"&GOTO :SETUPCHECK)

where I optimize in my

:IMG64
FOR %%i IN (Z Y X W V U T S R Q P O N M L K J I H G F E D C B A) DO (
    for %%j in (
        wim
        esd
        swm
    ) do (
        IF EXIST "%%i:\x64\Sources\install.%%j" (
            IF "%%j" equ "swm" (
                SET INSTALLIMAGE="%%i:\x64\Sources\install.swm"
                SET SPLIT=1
                SPLITPATTERN="%%i:\x64\Sources\install*.swm"
                GOTO :SETUPCHECK
            )
            SET INSTALLIMAGE="%%i:\x64\Sources\install.%%j"
            GOTO :SETUPCHECK
        )
    )
)
GOTO :SETUPCHECK

and here another mistake

:RUNDPEXISTING
DISKPART /S X:\DISKPART.TXT
SET ERRORTEMP=!ERRORLEVEL!
IF !ERRORLEVEL! NEQ 0 (
ECHO.
ECHO THERE WERE ERRORS FORMATTING THE PARTITION
ECHO.
PAUSE
GOTO :MAINMENU
)
GOTO :IMAGESELECTION
)

Where else do you get in mine, can you have one) more or not?

:RUNDPEXISTING
DISKPART /S X:\DISKPART.TXT
SET ERRORTEMP=!ERRORLEVEL!

IF !ERRORLEVEL! NEQ 0 (
    ECHO.
    ECHO THERE WERE ERRORS FORMATTING THE PARTITION
    ECHO.
    PAUSE
    GOTO :MAINMENU
)
GOTO :IMAGESELECTION

DioNZB MDL Member

Jun 23, 2013

238

419

10

#263 DioNZB, Apr 22, 2023

All the download links are down, Can someone provide me with a new one
Thanks in advance

Windows 10, version 1809 (refresh) 17763.107 ISO DOWNLINKS
Windows 10, version 1809 Updated December - 17763.194 ISO downloadlinks

Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Enthousiast MDL Tester

Oct 30, 2009

51,377

111,593

450

#264 Enthousiast, Apr 25, 2023

DioNZB said: ↑

All the download links are down, Can someone provide me with a new one
Thanks in advance
Click to expand...

Abandoned.

R.I.P Nigel Mxman2k. Sleep well, old chap

Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
haz367 MDL Addicted

Jan 11, 2020

827

1,500

30

#265 haz367, Apr 26, 2023
Last edited: Apr 26, 2023

https://forums.mydigitallife.net/threads/win-11-boot-and-upgrade-fix-kit.83724/
Enthousiast MDL Tester

Oct 30, 2009

51,377

111,593

450

#266 Enthousiast, Apr 27, 2023

haz367 said: ↑

https://forums.mydigitallife.net/threads/win-11-boot-and-upgrade-fix-kit.83724/
Click to expand...

That's only for win 11 x64, but i did make a fix for it but that was install.esd related:
https://forums.mydigitallife.net/threads/win-11-boot-and-upgrade-fix-kit.83724/page-50#post-1767560

R.I.P Nigel Mxman2k. Sleep well, old chap

Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
haz367 MDL Addicted

Jan 11, 2020

827

1,500

30

#267 haz367, Apr 27, 2023
Last edited: May 2, 2023

Excuse me for being a jerk for a min...

Keep up the good work everybody
haz367 MDL Addicted

Jan 11, 2020

827

1,500

30

#268 haz367, Apr 27, 2023

@murphy78

You lurker...pls fix the good work.
murphy78 MDL DISM Enthusiast

Nov 18, 2012

7,434

11,773

240

#269 murphy78, Apr 30, 2023 (OP)

haz367 said: ↑

@murphy78

You lurker...pls fix the good work.
Click to expand...

Sorry about that. Re-uploaded the 3 files in the OP to mirror creator. They should be working again.

Enthousiast MDL Tester

: Oct 30, 2009

: 51,377

: 111,593

: 450

#270 Enthousiast, May 2, 2023

Did you fix the scripts too?

ISO with install,esd (your currently uploaded version):

Code:

============================================================
Add Muprhy78 Diskpart and Apply Image script to boot.wim
originally by Enthousiast v1.2...
============================================================

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 N

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, 3558719488 bytes (3394 MiB)

Extracting archive: Source_ISO\25352.1.230422-2250.ZN_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US_ESD_2023_05_02.ISO
--
Path = Source_ISO\25352.1.230422-2250.ZN_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US_ESD_2023_05_02.ISO
Type = Udf
Physical Size = 3558719488
Comment = Win_10_x64_en-US
Cluster Size = 2048
Created = 2023-05-03 02:00:00

Everything is Ok

Folders: 84
Files: 950
Size:       3567152752
Compressed: 3558719488
This script only supports install.wim and install.esd format
Structure must be sources\install.wim or x64\sources\install.wim
Press any key to continue . . .

This has been discussed here (a few posts up and down):
https://forums.mydigitallife.net/threads/win-11-boot-and-upgrade-fix-kit.83724/page-50#post-1767560

Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...

murphy78 MDL DISM Enthusiast

Nov 18, 2012

7,434

11,773

240

#271 murphy78, May 4, 2023 (OP)

Enthousiast said: ↑

Did you fix the scripts too?

ISO with install,esd (your currently uploaded version):

This has been discussed here (a few posts up and down):
https://forums.mydigitallife.net/threads/win-11-boot-and-upgrade-fix-kit.83724/page-50#post-1767560
Click to expand...

Been a while, but didn't you ask me to fix this for v1.3.1 and I did?
This is what I have posted on the releaselog:
"1.3.1 Added Media Creation Tool style x86/x64 $oem$ folder copying that would detect the architecture of the install applied and seek the appropriate $oem$ subfolder to copy
Re-worked the add diskpart apply image script to be in line with the support for the default and dual boot format
Added esd and split wim support for the add diskpart apply image script for the line that used to detect information from the install.wim
Minor other tinkerings not worth mentioning, mostly wording or spacing issues"

I never really intended on replacing your hard work for the win11 fix. I just was trying to get something going at first. IIRC there was some reason why everything was set to wim at first on those old scripts, though I don't remember why that is.
Enthousiast MDL Tester

Oct 30, 2009

51,377

111,593

450

#272 Enthousiast, May 4, 2023
Last edited: May 4, 2023

murphy78 said: ↑

Been a while, but didn't you ask me to fix this for v1.3.1 and I did?
Click to expand...

That was for the MCT like x86/64 ISO structure ate the running of the script during setup, seems now it doesn't support single install.esd anymore when inserting the script.

R.I.P Nigel Mxman2k. Sleep well, old chap

Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
murphy78 MDL DISM Enthusiast

Nov 18, 2012

7,434

11,773

240

#273 murphy78, May 5, 2023 (OP)

Enthousiast said: ↑

That was for the MCT like x86/64 ISO structure ate the running of the script during setup, seems now it doesn't support single install.esd anymore when inserting the script.
Click to expand...

I'm a bit confused. Did you just replace the files from my 1.3.1 version into the shoddy win11 v1.2 thing I made? If you did, it doesn't work that way. I never added esd support for that script. I added esd support for my 1.3.1 installer script.
KleineZiege MDL Guru

Dec 11, 2018

2,062

2,366

90

#274 KleineZiege, Jan 18, 2024

you are awesome, the script is so good,
Thank you very much.
fabricio simoes MDL Member

Dec 17, 2020

193

51

10
#275 fabricio simoes, Oct 6, 2024
murphy78 said: ↑

murphy78's DiskPart and Apply script is a small WINPE project that allows users to utilize dism and diskpart techniques
to set up BIOS-booting and UEFI-booting systems.

Features:

Multi-boot support

Add drivers to WinPE/Installed Image support

Split-Wim support

install.esd support

Ability to disable the extra system partition in BIOS/MBR

Ability to specify Recovery Image partition size

$OEM$ subfolder copies

Requirements:

Windows ADK matching build for boot.wim you are installing to if manually integrating

Brain (Not required thanks to Enthousiast script installer I modified)

What is this?: murphy78's DiskPart and Apply script is a small menu-based Windows partition and setup tool.
Why use this over Windows Setup?:
There are a few reasons:

Split-Wim support (script doesn't need to display the EULA, setup does; by default)

Windows 11 support on machines that don't have Secure Boot or TPM comparable hardware

If you've made an All-In-One version of a Windows Setup disc in the last year or two,
you've noticed that it's fairly difficult to work with AIO versions and UEFI at the same time.
Well, gents: you're in luck. This script handles wim, swm, and esd format.

So why does that help with UEFI?
Well UEFI needs a fat32 partition when installing from a USB Flash drive.
So if you try to copy over a giant 16GB AIO or even a sysprepped single-index
Windows version, if any file is larger than 4GB it will fail to hold the file.
Without fat32, there is no UFD UEFI booting. Some freeware programs like Rufus
can fool your computer into making extra partitions to handle extra large files, but many
computers may not be able to handle this. What's more, Microsoft itself does not allow it.

So what's the solution? Split-WIM support. Normally I would advocate for trying
to use MS's own tools. Since that's not an option as the EULA will fail to be detected in the first file,
you have to apply your own image. Most people have no clue how to both apply your image,
run bcdboot, and set the reagentc options for the winre.wim. I don't blame you. When I first
took on this project, I had no clue either. But I wanted to get it to work, so I stuck with it.

So how do we create this Split-WIM?
It's actually very simple.
You just run the command (3900 in this example is 4095 mb to fit in fat32):

Code:

dism /split-image /imagefile:c:\iso\sources\install.wim /swmfile: c:\iso\sources\install.swm /filesize:4095 /checkintegrity

This command will create a file called install.swm, then install2.swm, install3.swm, etc.
The way the apply works is when you are using a split-wim you specify /swmfile:install*.swm
Example (You don't need to know this. This is just for reference):
dism /apply-image /imagefile:\sources\install.swm /swmfile:\sources\install*.swm /applydir:W:\ /index:1 /verify /checkintegrity

So what do we do with the install.wim?
Just tuck it away somewhere on a spare drive or something and keep it safe in case you need it.
You no longer need it for your install disc.

So how do I use this project?
Recently @Enthousiast made a script installer and I've modified his first version:
So now you can run add-Diskpart_Apply_Image_Tool_murphy78_custom_v1.1.cmd with an
iso in the source_iso folder and it will spit out an already integrated diskpart/apply image iso
The script gives you a choice to include a winpeshl.ini which will start the script automatically
If you choose that option you can still choose to exit the script when running the setup media.
It will just run the setup program after exiting. Instead of the characteristic blue setup screen,
it will be white to denote that it is not running a normal setup routine. This is MS's way of telling
people that it has ran an abnormal startup routine for setup. There is no other alteration to setup.

Below are the basic manual install instructions:
Mount boot.wim index 2
Copy the files from the appropriate architecture folder
Add any additional packages you wish to your boot image (servicing stack, cumulative rollup, etc)
Resetbase your image
Commit the changes. You can re-export to compress it a little further if you wish.

Integration Instructions:

Code:

dism /mount-wim /wimfile:c:\win10\sources\boot.wim /index:2 /mountdir:c:\mount :Copy over the x64 folder's contents to the c:\mount\ directory :Do not copy over the entire x64 folder, just the contents. dism /unmount-wim /mountdir:c:\mount /commit :Make boot-prompt image with UEFI boot support (press any key blah blah) oscdimg -o -u2 -udfver102 -bootdata:2#p0,e,bc:\win10\boot\etfsboot.com#pEF,e,bc:\win10\efi\microsoft\boot\efisys.bin -lYourImageLabelMax32chars c:\win10\ c:\temp\YourISOName.iso

That's it. I recommend testing it in a VM for a bit until you know what you're doing.

More detailed descriptions of a few things:

Instructions here are for deployment tools copype versions using the Win ADK
If you've copied the files into a normal win setup boot.wim, you don't need to know this.

You don't need both amd64 and x86 winpe images. If you only plan on accessing computers with
2 cores (64-bit) you can just use the amd64. However, if you plan on using any systems with
only 1 core (32-bit) you will need to use x86. If you truly want a disc that supports both
1-core systems and UEFI, you will use both. What we can do is modify the efi\boot\bcd and set
it to boot2.wim and then rename the x64 version to boot2.wim of course. You could also try
bootx64.wim if you want clarity on what you're doing.

When you run copype it creates a directory where you specify, but it also makes a bare-bones
boot.wim of the specified architecture and copies over firmware files such as the oldschool
etfsboot.com (BIOS-Boot sector for iso files) and the efisys.bin (UEFI-Boot sector for iso files)
It puts your basic iso in the c:\winpe_amd64\media\ folder (or winpe_x86)
Inside the media is just the basic skeleton of a bootable winpe image. All it will run is
the mounted directory's "x:\windows\system32\startnet.cmd"

So my project just edits the startnet.cmd, removes the wpeinit call for speed, and then runs the
menu.cmd script. I've also included in my project x86 and x64 versions of both winrecfg.exe,
find.exe, and the associated en-US mui files. You *COULD* find the other language versions of
the files, but there's no point. The whole script runs in English and it doesn't stop to give
detailed readouts from the find or winrecfg commands. They are just for utility.

DOs and DON'Ts:

DOs:
1) Utilize a few of the options such as driver-addition when applying an older image to a raid.
After Install it will ask you if you wish to add drivers to the offline image.
It just does a dism /image:w:\ /add-driver command, but you need it before the first boot
on a raid because it won't be able to access the system drive if you don't. On win8+ it's not
that much of an issue unless you have a specialized card that doesn't have native 8.x support.

2) Try Fast Setup option if you're only installing a single-index. It's faster and less
confusing, but it won't ask you to specify partition size. It will just use the maximum.
You can use this with a Recovery Image. I've added the option in the Fast Setup options.

3) Can't get your WinPE to detect your non-supported RAID? There's a WinPE drivers section also.
It's not as easy to work with as you have to spell out the exact INF file name, but it's there.
I also give a CMD prompt every time there's a driver add option, so that you can navigate around
and figure out the directory names and file names. It's not as easy as the Windows Setup, but it's
there and it should work. I also added a wpeinit option in case some people have some sort of
Plug and Play drive that isn't normally detected.

4) Don't be afraid to Multi-Boot. With the No System Partition option enabled in BIOS boot, you
can create 4 primary partitions. If you don't enable Recovery Images, you can quad-boot your system
in about an hour. It gets even more ridiculous for UEFI. GPT partitioning doesn't limit your
primary partitions to 4, so you can go nuts. You can have as many system drives as you can fit
drive letters. I believe I've calculated it at 21, though I haven't actually tested it. You
could also have recovery images set up for each of those installs.

DON'Ts:
1) Don't choose wrong sizes for partitions . If you choose a partition size of say 10000 (in megs) for a Windows 8 x64 image, it will STILL try to apply it. It doesn't mean it will work. A general rule of thumb
for OS image size is 20GB for x64 versions and 16GB for x86 versions. Obviously if you try to put
more stuff in the image, you should make it larger. You can go into diskmgmt.msc later and create
extra partitions for data files and such. I would actually recommend learning how to change the
program files folders, or just give yourself some breathing room on your OS and make the partition
about double the recommendation, just in case.

2) Don't come crying to me if you lose your data on an important drive because winpe set the
wrong one to disk 0. I give all the options to check disks, check volumes, change disk numbers, etc.
If you don't know how to use them, that's on you. Try things with a VM until you get more comfortable
if you are a newbie. If you still don't feel comfortable, don't use it; use a normal Windows disc.

MISC NOTES:

1) I've added an $OEM$ folder copy option if you're used to working with $oem$ folders. In Fast Setup it's
enabled by default just like normal Windows Setup, but in the default Setup it gives you a choice. I haven't
actually tested this one much. I've heard things like using $OEM$\$1\Drivers\ will make a c:\drivers folder
and that when you enter the hardware config part of Windows setup it will look for appropriate drivers
anywhere on your system, including dvds or usb, but if you wanted to copy that over and use it in a Recovery
Image capture, $OEM$\$1\Drivers might be a good way to do it

2) Set the WINRE boot key to F1 during boot. You can hold f1 during boot to go straight to the Recovery options
You should still use f8 in the boot menu while over the appropriate multi-boot option if multi-booting tho.

3) Is the boot menu using an old windows 7 boot menu for your multi-boot and you want the fancy win8 version?
Boot into your win8 system. Make sure all partitions are assigned drive letters... (diskpart or diskmgmt.msc)
then go into admin prompt and run:
bcdboot c:\windows
When you reboot, the nice fancy graphical win8 boot menu should be the default. Be warned that the win8 menu
might be harder to enter recovery environment in.

Few Project Screens:
View attachment 27940 View attachment 27939 View attachment 27937 View attachment 27936 View attachment 27938

Get the File:
New:

https://mir.cr/OTWIBYSA
File Name: murphy78-Diskpart-Apply-v1.3.1.zip
File Size: 2.4.1 MB
SHA1: D0D59CB47AE8A3135998D309CD4A46AC660CC327
File type: zip/pw
PW: MDL2021

Old:

https://mir.cr/8JPSNYIV
File Name: murphy78-DiskPart-Apply-v1.3.0.zip
Size: 2.41 MB
SHA1: 18DEC4C16F73A021E8473CF51FDE63E308F6DEA4
Format: zip/pw
PW: MDL2021

https://mir.cr/WPR5LFJ1
File Name: murphy78-DiskPart-Apply-v1.2.8.7z
Size: 442 KB
SHA1: A754BA65CC1BE51AA5FE55ED4036C15805B7DCFC
Format: LZMA1

Changelog:

1.3.1 Added Media Creation Tool style x86/x64 $oem$ folder copying that would detect the architecture of the install applied and seek the appropriate $oem$ subfolder to copy
Re-worked the add diskpart apply image script to be in line with the support for the default and dual boot format
Added esd and split wim support for the add diskpart apply image script for the line that used to detect information from the install.wim
Minor other tinkerings not worth mentioning, mostly wording or spacing issues
1.3.0 Removed Recovery Partition Support. Option has been deprecated and seems to only have been supported on Win8.x
Added v1.1 custom script installer compliments @Enthousiast
Added default winrecfg.exe & winrecfg.exe.mui en-us files
Removed winrecfg packages and information about package integration
Added winpeshl.ini option
Fixed error in bios boot winre copy option syntax that prevented toggling

1.2.8 Added Win10 Multi-Boot detection support for image files (x86\sources x64\sources)
I had made a custom version of 1.2.7 for my superaio, but I've consolidated the detection for 1.2.8

1.2.7 Added multi-lang source support by changing dism commands to output /english
While the script will still be in English, it will allow for boot files from different locales*
*You would need to add the appropriate language winre mui package from the ADK winpe files
Removed the murphy78 folder and just used menu.cmd in the system32 folder

1.2.6 Forgot I removed the winrecfg.exe and dll.mui files
These get modified by the update 2934018, so you should add the 2 packages and then add the 2934018 update.
After adding all the packages and updates, you should resetbase your latest version of winpe to reduce size and uninstall info
So I added 2 folders that contain just the base winrecfg package and the en-us version.
If you are translating the output of this script, you should use appropriate language files, including different dism mui stuff in
the murphy78 folder. I may change the structure around or change things to specialize it more toward winpe 5+ since the choice.exe
doesn't allow win7/server2008 anyway. Well, I could also just add both versions... I may play with it another time.

1.2.5 Enabled display of currently selected disk number in the disk menu. (It helps to know )Changed the no-setup-option folder to USE-EXISTING-SETUP to clarify what it does.*
*(This folder uses the existing setup by default, but adds a shortcut menu.cmd in the system32 folder
so that when a user is running the existing setup, they can press shift-f10 to open admin prompt and
just type "MENU" and the diskpart/apply menu will start - This is how I do it in my monthly stuff)

1.2.4 Fixed an issue where Disk kept being set to 0 because of disk menu loop.

1.2.3 Fixed a bug where setup prompt would fail if applied to an existing boot.wim

1.2.2 Moved all the DART folder and menu.cmd files to murphy78 folder (you can delete the old menu.cmd and DART folder)
Added updated versions of winrecfg.exe and dll.mui
Changed image selection to a single parse at beginning and simply print/re-print file when re-displaying (listing many indexes was slow)

1.2.1 Fixed last-minute swm bug
Fixed split-wim apply bug in new changedir-less method

1.2.0 Reworked many portions of the script but left the basic functionality intact
Added Use Existing System Partitions and Windows Partition options
Changed Disk Options to a single short menu rather than 2 superfluous options and menu
Added Generalmx's subdirectory driver addition method from his script for WINPE drivers
Changed a lot of variable handling to use !! instead of %% and enabledelayedblahblah
Moved image detection to beginning of script
Merged a few drive letter partition options
Added few warnings for UEFI users trying to use Recovery image partitions for win7/2008/2011
Changed default Recovery Partition size to 5 GB
Changed a lot of the wording and choice strings

1.1.1: Custom unreleased version for v2 of apr win8.1
Added existing setup support and opt-out option
Added detected recovery option into main menu

1.1.0: Reworked diskpart scripts to use ramdrive txt imports and piping commands
Added Multi-Boot support
Added Fast Setup with Recovery Image
Added No System Partition option to BIOS booting
Added No WinRE movement option for BIOS boot, already disabled if NoSysPart
Added Recovery Image partition support
Added Driver addition support in both PE and Windows installs
Added Sources\$OEM$ subfolder copies if detected
Change to WINRECFG to allow mismatched x86/amd64 support replacing reagentc
Added minimal error-handling
Added DISM folder so user wouldn't need to integrate S14 updates
Reworked the entire script over and over to verify things

1.0.2: Powershell WinPE disk management version (not worth bothering)

1.0.1: Fixed GPT diskpart scripts to not use "active" command. Causes diskpart to fail and subsequent application to fail.

1.0.0: Initial prototype (broken UEFI diskparting)

Credits: @murphy78, @Enthousiast, Microsoft, TechNet
Click to expand...

Can anyone help me put diskpart to start as written.
Recently @Enthousiast made a script installer and I've modified his first version:
So now you can run add-Diskpart_Apply_Image_Tool_murphy78_custom_v1.1.cmd with an
iso in the source_iso folder and it will spit out an already integrated diskpart/apply image iso
The script gives you a choice to include a winpeshl.ini which will start the script automatically
If you choose that option you can still choose to exit the script when running the setup media.
It will just run the setup program after exiting. Instead of the characteristic blue setup screen,
it will be white to denote that it is not running a normal setup routine. This is MS's way of telling
people that it has ran an abnormal startup routine for setup. There is no other alteration to setup.
murphy78 MDL DISM Enthusiast

Nov 18, 2012

7,434

11,773

240
#276 murphy78, Oct 6, 2024 (OP)
fabricio simoes said: ↑

Can anyone help me put diskpart to start as written.
Recently @Enthousiast made a script installer and I've modified his first version:
So now you can run add-Diskpart_Apply_Image_Tool_murphy78_custom_v1.1.cmd with an
iso in the source_iso folder and it will spit out an already integrated diskpart/apply image iso
The script gives you a choice to include a winpeshl.ini which will start the script automatically
If you choose that option you can still choose to exit the script when running the setup media.
It will just run the setup program after exiting. Instead of the characteristic blue setup screen,
it will be white to denote that it is not running a normal setup routine. This is MS's way of telling
people that it has ran an abnormal startup routine for setup. There is no other alteration to setup.
Click to expand...

It's been quite a while since I've tinkered with the custom version. Using winpeshl.ini to automatically launch menu.cmd (The main diskpart/setup script)
is certainly possible and it's what I used to do on my super-aio releases because normal setup is only meant for the specific OS version that the SKUs ship with.
Obviously a diskpart/setup script was preferable in that situation because you wouldn't want mismatched recovery information, winre.wim partition sizes, etc.

As far as the actual winpeshl.ini, it's just:

Code:

[LaunchApps] %WINDIR%\system32\winpeinit.exe %WINDIR%\system32\menu.cmd %SYSTEMDRIVE%\sources\setup.exe

I changed things in 1.3.1 which is different from the v1.1 custom that comes with diskpart/apply v1.3.0 (The v1.1 custom was meant to apply to win11 stuff that @Enthousiast was working on) It meant to help with something. I forget exactly what off the top of my head.
The diskpart/apply changelog for v1.3.1 is:
1.3.1 Added Media Creation Tool style x86/x64 $oem$ folder copying that would detect the architecture of the install applied and seek the appropriate $oem$ subfolder to copy
Re-worked the add diskpart apply image script to be in line with the support for the default and dual boot format
Added esd and split wim support for the add diskpart apply image script for the line that used to detect information from the install.wim
Minor other tinkerings not worth mentioning, mostly wording or spacing issues
fabricio simoes MDL Member

Dec 17, 2020

193

51

10
#277 fabricio simoes, Oct 6, 2024
murphy78 said: ↑

It's been quite a while since I've tinkered with the custom version. Using winpeshl.ini to automatically launch menu.cmd (The main diskpart/setup script)
is certainly possible and it's what I used to do on my super-aio releases because normal setup is only meant for the specific OS version that the SKUs ship with.
Obviously a diskpart/setup script was preferable in that situation because you wouldn't want mismatched recovery information, winre.wim partition sizes, etc.

As far as the actual winpeshl.ini, it's just:

Code:

[LaunchApps] %WINDIR%\system32\winpeinit.exe %WINDIR%\system32\menu.cmd %SYSTEMDRIVE%\sources\setup.exe

I changed things in 1.3.1 which is different from the v1.1 custom that comes with diskpart/apply v1.3.0 (The v1.1 custom was meant to apply to win11 stuff that @Enthousiast was working on) It meant to help with something. I forget exactly what off the top of my head.
The diskpart/apply changelog for v1.3.1 is:
1.3.1 Added Media Creation Tool style x86/x64 $oem$ folder copying that would detect the architecture of the install applied and seek the appropriate $oem$ subfolder to copy
Re-worked the add diskpart apply image script to be in line with the support for the default and dual boot format
Added esd and split wim support for the add diskpart apply image script for the line that used to detect information from the install.wim
Minor other tinkerings not worth mentioning, mostly wording or spacing issues
Click to expand...

I don't know how to change, this version is no longer available for download, I'm using the one from @Enthousiast but I wanted it to start disk part automatically?
In which folder do I place this code created winpeshl.ini file?
vigipirate MDL Senior Member

Feb 24, 2011

411

102

10

#278 vigipirate, Oct 6, 2024

hello link

https://pixeldrain.com/u/kzZNREbz
fabricio simoes MDL Member

Dec 17, 2020

193

51

10

#279 fabricio simoes, Oct 6, 2024

vigipirate said: ↑

hello link

https://pixeldrain.com/u/kzZNREbz
Click to expand...

thank you
resolved renewed download link...
fabricio simoes MDL Member

Dec 17, 2020

193

51

10
#280 fabricio simoes, Oct 6, 2024
I'm just having a problem as my xml is in the root of the iso, it keeps asking Microsoft for an account, I can't get around it, maybe there was a specific place to put this xml, to use diskpart...?

(You must log in or sign up to post here.)

Page 14 of 16