Windows 11 24H2 - Setup Error 0x800700001 - 0x4002F (Ventoy)

Yadler1

New Member
Messages
12
Reaction score
0
everything works fine in a virtual environment, but on my PC I have an error 0x800700001 - 0x4002F
I turned off a lot of things, I have a subscription. I wanted to understand where to dig. I also want to note that this happens on a virtual machine, but if you turn it off and on completely, the installation continues. Doesn't work on the host machine.
 
I turned off a lot of things, I have a subscription. I wanted to understand where to dig. I also want to note that this happens on a virtual machine, but if you turn it off and on completely, the installation continues. Doesn't work on the host machine.
This question can't be answered without a preset (please remove any user passwords or license key).
0x400?? points to a possible problem in the OOBE phase.
 
Also very important, after attaching your preset, when does that error popup in the installation process?
 
when checking the disk. Everything works fine on the virtual machine. I think it's because of Ventoy/

This has already happened to her. I'll definitely check it now
 
Last edited by a moderator:
es it works. Ventoy is to blame!!!!

They still haven't fixed it, I can't use it yet.
 
Last edited:
I can confirm that this - still! - is a Ventoy issue. A workaround is to deploy the 24h2 install.wim using an older version of Windows Setup (23H2 for example)
 
The new 24H2 Setup client appears to be very picky about images which worked successfully for 23H2 and lower.

Try this boot.wim hack to restore the old client:
https://www.ntlite.com/community/index.php?threads/windows-11.2235/post-45606
For now I have a working ISO (I just put my modified 24H2 install.esd, autounattend.xml and $OEM$-folder inside a 23H2 iso and removed the 23H2 install.wim), but I'll try this for the next build (25H2 or whatever Microsoft releases this year).
 
Hi guys,
I got the same problem with 24H2 started from Ventoy, GPT, installing on Dell Optiplex 3050. (Windows 11 24H2 - Setup Error 0x800700001 - 0x4002F)

The interesting thing is that when i start original MS iso 24H2 and start installation (from Ventoy), 2 things happen. Using new setup it does not find drive. Using old setup it finds drive and installs. Once i do even tiny change to iso, even only bypass and setting legacy setup (and nothing else), old setup starts, but drive becomes invisible. W10 install fine without any problem. Any ideas? As for now i switched back to 23H2. I can provide settings if required, but i literary make no changes except as in picture.

1738251061986.png
 
The new 24H2 Setup client appears to be very picky about images which worked successfully for 23H2 and lower.

Try this boot.wim hack to restore the old client:
https://www.ntlite.com/community/index.php?threads/windows-11.2235/post-45606

I guess that NTLite settings as in picture are equal to the registry edit linked above (showed bellow) = start with old setup, right?

1738251704789.png
Code:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\Setup]
"CmdLine"="X:\\sources\\setup.exe"
 
Correct. The boot.wim workaround has been rolled into the Settings / System menu.

The previous NTLite release has a bug where it mistakenly applies the CmdLine reg to install.wim. Please update to v2025.01.10275 (January 29) or later.
 
Correct. The boot.wim workaround has been rolled into the Settings / System menu.

The previous NTLite release has a bug where it mistakenly applies the CmdLine reg to install.wim. Please update to v2025.01.10275 (January 29) or later.
I am updated to this version. I just tested again today with already updated version.
 
Back
Top