Windows could not complete the installation

Hi all,

I am needing some advice on what else I could try with the error that I continue to get when trying to apply a new created image. I have sysprep a Dell Latitude 5310 with an unattend and autounattend answer files for windows 10 20H1. I am using ADK version 2004 10.1.19041.1 and same version for the PE. I have check to see if something was in my answer files preventing me to move forward. I don't see anything unusual with the 2 files.
When I am creating the image of course the laptop is in audit mode. I install only about 5 programs, create shortcuts, add the start menu layout, add unattend answer file in sysprep folder. I run a command to clean out all temp files etc. The very last thing I do is I go into computer management to users and enable administrator account.
Next I runs DISM to capture the image all is flawless my image comes out to about 5.4gig.
I add the install.wim file to my usb drive that I created through rufus and creating GPT as I heard that's what SHOULD be used.
Also, I add the autounattend file to the root of the usb drive.

I go into BIOS make sure secure boot is disabled that way the laptop can bootup and see the usb drive.
I apply the usb drive and it starts running the image without any issues only up until it says:

Windows could not complete the installation. To install windows on this computer restart installation.

After all the research I have done, I have applied many supposedly fixes, but yet I am still having this issue.

What have I done so far? Most of the time I have had to go in through cmd Shift +F10, MMC, add computer management, cllick on administrator and see the account is disabled. But I know for a fact before shutting down the laptop in audit mode I enabled the admin account. AFter enabling admin acct., laptop restarts goes back to the same error message.
Look in the registry made some adjustments same error message.
converted drive in laptop to GPT and used rufus to create usb startup drive along with using GPT same error message
Used Secpol.msc acct. policy 0 disable same error message

From all the fixes I have researched it seems as though it points back to basically this is a password issue. I can't seem to figure out why I am having this issue if I had made sure the administrator acct. is enabled before shutting it down in audit mode.
Also, I created another image for another laptop Dell 5320 and I get the same exact issue. I thought perhaps maybe it was the image maybe it was a corrupted file. That's why I had started ALL over again in creating a new image thinking maybe it was a corrupted image. I applied the newly created image to another laptop and I get the same exact error message. So, it's not a corrupted image like I said before I think it's a password issue for a certain acct. , but I just can't seem to figure it out after 3 days and many different solutions I still have this same issue. HELP!!!!

How far it goes till you receive the message "Windows could not complete the installation"?

Do you boot the installation drive as UEFI to install as UEFI-GPT?

Did you split install.wim into smaller install.swm files or did Rufus created 2 partitions on the USB drive (FAT32 and NTFS)?

The message comes up after applying the OS and after reboot that's when it appears.

to create the bootable usb flash drive I used rufus and had to create GPT. On the laptop I had converted the partition as GPT as well.

Rufus only created one partition which was the GPT.

As we speak I am creating another image this time without the 2 answer files. I am only going to put the autounattend file in the root of the usb flashdrive and see what happens.
It makes me wonder before I shutdown the computer from audit mode I wonder if that is when the admin acct. is getting disabled?

because I know for a fact I am going into to enable the admin acct. before shutting off. Then when I go through cmd on the failure screen to the computer management. Next, I pull up the user accounts and admin acct. is disabled.
So I am not sure how it is getting disabled again that's where I think the problem is. I have to figure out to prevent that from happening.

Let's try this approach without Rufus

Open a CMD window as administrator and type:
diskpart
list disk (it will list all drives. Identify the USB drive number)
select disk n (replace n by the USB drive number obtained with list disk)
clean
convert mbr
create part primary
select part 1
format fs=fat32 quick
assign
active
exit (to exit diskpart)

Mount a Win 10 installation iso file.
Copy all files and folders to a folder.
Copy your unattended script to the root of the folder.
Replace \sources\install.wim with your custom install.wim
As your Install.wim is bigger than 4G, let's split it on smaller install.swm (to bypass the 4G limitation on FAT32)
Extract split.zip and copy split.cmd to the \sources folder (same folder you have your install.wim) and run the CMD file.
It will split install.wim into smaller install.swm and install1.swm
Delete \sources\install.wim and split.cmd
Now copy all files and folders to the USB drive created above.

Boot the USB installation drive as UEFI and see what happens

If it may help, take a look at Kari tutorial
Create media for automated unattended install of Windows 10

Yeah I have used his(Kari's approach) it has helped me out in the past.
I am not sure what is different this time as I continue to get that error message.
I am thinking because I didn't create an acct. as another admin acct. rather than just rely on the built-in acct.
As I type this up I have created a new image along with creating an admin acct. along with making some adjustments
on both answer files. I am hoping this will correct the issue I can only hope we shall see.
I will give an update as it's just about done capturing the image.

- - - Updated - - -

So, I went ahead went back to Kari's write up and I copied his answer file.
I had now added the newer answer file and re-ran the setup.
Looks like it's not working because it's just going in a loop it keeps creating partitions I believe.
However, I haven't copied the unattend file yet. So what I am going to do is recreate a new image and add the newer unattend file as well as add the newer autounattend file. I will see what happens.
I am hoping to have time to work on it this weekend because it's been a week I am having trouble and not getting anywhere.
I will keep posting updates

- - - Updated - - -

how funny I was doing this for the first time creating an image 2yrs. ago this time. I looked back at an old post of mine and this is exactly the same place I was stuck at. Unfortunately, for the life of me I can't remember what I did to overcome this issue.
I really believe it has to do with the Administrator acct. is disabled and that is why that screen pops up.
Right before I shut it down to do the capture image I make sure I enable the administrator acct. so that I won't get this error.
It happens each time not sure what is triggering it to go back to get disabled.

- - - Updated - - -

I am actually going to use my personal laptop to do a sysprep and see what happens. It's a lenovo so I wouldn't think it's any different to sysprep. I am going to use the same exact answer files and see if there is any difference.

- - - Updated - - -

Well I can say FINALLY I was able to get the image installed to the Dell laptop. It is working now, but unfortunately, the start menu didn't stick nor the background. I believe if those two would've stayed I would really be jumping with joy. Now I have to go back to see why that happened. Perhaps it was something got overlooked in the answer file. At least I am glad to see the programs are installed and working. Another thing I discovered is it will only allow the administrator login it won't allow anyone else to login. So, I definitely have a lot to look at again. At least I am relieved that the image finally installed.

Congratulations.
I have only used Sysprep to move C:\users (small SSD) to D:\users (large HDD).

Thank you! It's a real relief to finally get this figured out. Now hopefully I will keep this in my memory lol.