Getting error code 0x8030002F when using install DVD burned from ISO

A

abramesd

New Member
Messages
7
Reaction score
0
I created a customer Windows 10 Pro ISO and I tested it using VirtualBox. I attached the ISO to a new VirtualBox VM and the installation was successful with no errors and all the custom changes I made were applied as expected. I then used the ISO to "burn" a installation DVD and when I tried to run the Setup.EXE on the DVD I get an error as follows:

View attachment 12292

Error message is:
"Windows was unable to create a required installation folder.
Please reconfigure you boot.win file to use the flag 9
settings for the first image, and restart your installation

Error Code: 0x8030002F"

I am not exactly sure what to do here

I opened the dvd in NTLite and this is what I see

View attachment 12290

This is the original ISO I used to create my customer ISO

View attachment 12291

I thought I did everything as required but clearly I either missed something or made a mistake.

If anyone can provide some idea of what I did wrong or how to fix this please, I would be grateful. Thank you

David
 
If your ISO works in VirtualBox, then it may be caused by a problem with the DVD burning software. I realize your goal is to create an usable DVD, but you should try using Rufus to make a bootable USB.

The point is to test whether the problem follows your ISO, or the method used to create the media. If the same ISO works under VirtualBox and a Rufus-created USB drive, it's not an issue with the source file.
 
Thank you that makes sense and I was kind of leaning that way but I just wanted to check incase this was a stupid newbie error. I'll try the Rufus route and see what happens

David
 
Dear garlin,

OK I get the same error message with the Bootable USB made with Rufus. So maybe I need to provide some more info about the PC I am trying to install to.

This is a NEW pc using an ASRock x670e motherboard and a Ryzen 9 7950X3D CPU. 196 GB of RAM and 58 TB of disk storage spread over 4 SSD and 3 Iron Pro SATA hard drives.

My intension for this system was to run Windows Server 2022 as the HOST and Windows 10 PRO VM using VirtualBox.

I ran into problems supporting the internal WiFi and Network running Windows Server 2022, so today I was going to do a clean install of Windows 10 PRO I created using NTLite as the host. When I load the DVD or the USB and then double click on the setup.exe in either within a few seconds I get the error message as before complaining about not being able to create a temporary folder error code 0x8060002F

Now as a sanity check, I took the DVD and the Bootable USB and was able to create a new VM from both without error. However in the VM case I am not clicking on setup.exe the VM boots from either. In the case of the new PC the system will not boot from either the USB or the DVD, I have to start by clicking on the setup.exe.

So now I am thinking the issue may be with the new PC. I have the most current bios installed. Bios is configured for UEFI and no CMS.

I am going to try and create a regular install DVD from the Windows Media Creator Tool and see if that behaves differently.

I am also considering to wipe Server 2022 from the disks and see if that is why the DVD or USB is not booting.

If you have any more ideas or suggestions to check in NTLite please let me know, I can even share with you the Edits I made, just let me know

Again thank you for your time and any ideas you have,

David
 
I have another update. If I take the ISO image and mount it and then run setup.exe that works. The error 0x8030002F is telling me that the Windows Installer detected that Install media was modified and will not allow me to run the installer. So I guess I am stuck only being able to create VMs I tried using the NTLite install media on another PC and I am getting the same error. So now I seem to be stuck.
 
If an image works fine in VM, but doesn't on a physical PC -- it normally points to possible issues:
- Missing a required boot driver (usually for the SATA, NVME or USB3 controllers)​
- Having multiple devices with conflicting BCD boot info​

Since this is a new PC, and hopefully you don't need to preserve old data, reduce the problem to the basics:
1. Only connect one device (SSD?) to the system, and run the install. It's impossible for BIOS or Windows to be confused over which disk should be used, and it will confirm whether you need missing driver support.

2. If that install works, reconnect one more SSD. It's not clear from your decription are all the SSD's identical, or some are NVME or SATA drives. Repeat the installation.

3. Continue until all the SSD's are connected. It's probably not an issue with the HDD's, unless it's a drive ordering problem.

NTLite is agnostic about UEFI vs MBR boot, or supporting a dual-boot configuration. None of that is based on the ISO. It's a function of BIOS settings, and the BCD configs on the highest priority drive that your motherboard recognizes.
 
You must log in or register to reply here.
Back
Top