How do I bypass the New Windows Install and only have to Old Setup?

If esp? #47 has been allocated S and windows partition has been allocated C?

Great support

Have you done it now?

Here's what I have and I injected into boot.wim #2
winpeshl.ini
-------------
startnet.cmd
%systemdrive%\sources\setup.exe
%SYSTEMDRIVE%\Windows\System32\diskpart.exe, /s "%SYSTEMDRIVE%\Windows\System32\partitions.txt"
MakeDir.cmd

startnet.cmd
Dism /apply-image /imagefile:%usbletter%:\sources\install.wim /index:6 /ApplyDir:C:\
bcdboot c:\windows /s S: /f all

reg add "HKLM\SYSTEM\Setup\LabConfig" /f /v "BypassTPMCheck" /t REG_DWORD /d 1
reg add "HKLM\SYSTEM\Setup\LabConfig" /f /v "BypassSecureBootCheck" /t REG_DWORD /d 1
reg add "HKLM\SYSTEM\Setup\LabConfig" /f /v "BypassRAMCheck" /t REG_DWORD /d 1

It reboot and restarts windows setup!

Where did I go wrong?
Thanks, John

winpeshl.ini
-------------
startnet.cmd
%systemdrive%\sources\setup.exe
%SYSTEMDRIVE%\Windows\System32\diskpart.exe, /s "%SYSTEMDRIVE%\Windows\System32\partitions.txt"
MakeDir.cmd


Where did I go wrong?

Click to expand...

Your winpeshl.ini is the wrong order

%systemdrive%\sources\setup.exe should be the last entry

[LaunchApps]
partioning.cmd
apply-image.cmd
make-dir.cmd
%systemdrive%\sources\setup.exe

I already said that in post #38



Attach files

startnet.cmd
Dism /apply-image /imagefile:%usbletter%:\sources\install.wim /index:6 /ApplyDir:C:\
bcdboot c:\windows /s S: /f all

Click to expand...

that wont work because you havent given a value to the variable %usbletter%

I explained how to do that with the tagfile named fartyname.txt see post #45

You shouldnt need this line in red in winpeshl.ini
%SYSTEMDRIVE%\Windows\System32\diskpart.exe, /s "%SYSTEMDRIVE%\Windows\System32\partitions.txt"

if you include it in your partitioning.cmd file

see post #60

Am I explaining this poorly ? Garlin and hsehes do you follow ?

SIW2 said:

Am I explaining this poorly ?

Click to expand...

You're doing fine.
@Rbcc has a bad habit of rewriting your examples by changing the arguments, or running commands out of order.

SIW2 said:

Garlin and hsehes do you follow ?

Click to expand...

I would refer you to this WinPE flowchart:
Windows PE startup sequence explained

Some problems can be avoided by using boot.wim index #2 (no Setup), and completely replacing what Setup normally does with your own script. You're basically almost there.



Replacing Setup using boot.wim (index 1):

Write a startnet.cmd which calls:
1. wpeinit
2. Create and run a diskpart script
3. DISM /apply-image to C:\
4. bcdboot /s C:\Windows
5. Copy answer file from media to C:\Windows\Panther (edit file to assume you're starting at specialize pass, skipping WinPE pass)
5. shutdown /r (reboot into specialize pass)

winpeshl.ini is generally used to call higher-level deployment tools. While you can use it to run a script, you might as well leave winpesh.ini empty and have winpeshl fall back to run startnet.cmd.

The only difference is it's assumed startnet.cmd will run wpeinit, and winpeshl doesn't run wpeinit (because the MDT and SCCM deployment tools will handle their own initialization steps).

The scripts obviously should go in 2\windows\system32 except the tagfile which should be on the root of the usb stick

I have mentioned before that flowchart is wrong

@SIW2:​

I am in the middle of my 8th edit of partitions.txt, I can't figure out why it creates the first three partitions but not the partitions that I have added! You're doing a super job, I tend to get confused and or frustrated when something doesn't work!
I have attached 2 files in one 7 zip file called myfiles.7z

that is yours below.

dont want
diskpart.exe /s X:\partitions.txt
pause

in the text file . It goes in batch file which has the .cmd extension


It is strange to have the winre partition at the start of the disk. And it is too small

will WinRE, efiand msr be made atomatically by windows?