Win10PE_SE_2020-03-28 stop building with Error: "cmd.exe can not be copied"

Hello,

in the past, i created a few builds with:  Win10PE_SE_2020-03-28

But now, the builder stop with the error:  "cmd.exe can not be copied"

It is at the beginning - at point 6 or 7.


In the past, i created builds without problems from  "Win 10 1809 Enterprise".
In the images, i activated Net fx in the offline images and had no problems....

The ONLY difference, between the earlier builds and the one, i tried to build now:
I added "NTVDM" in the offline image, to get 16bit support.
I was wondering about the size of the image - after adding NTVDM" - it was 200 MB bigger after i added it.

Maybe someone can help me out?

Btw:  this "NTVDM - added" image, i used for a build with Win 10 PXE - without problems

Only, there was NO 16bit support in the build. 

- Although I previously used the image with:   "DISM / Image: c: \ test \ offline / Get-Features / Format: Table".
BOTH was present / activated.   Net fx + NTVDM

Can someone help me out?

First step would be to post a build log as that will help us help you

Hi,
thank you for your answer.

I guess, that my problem is much bigger than i thought !   :-(

I tried to do it on annother mashine = BINGO !   Everything is running fine.

On the mashine, where i have problems, i did that very often - until now....

So:  Now, i wish that i could find out, what happend to this mashine......


Also, i have annother "problem".
I noticed, that "NTVDM" isn't active - resp.:  in the Build, there is NO 16 bit Support.  (Only to/for Win 10 x86)
But, i added it before to the offline image and controlled it.

Also, i noticed, that there are totally 10 files in the build ISO - not 8, like before.

The reason, that i need the expand ISO:
There is a microsoft mouse driver, which make problems to several Toughbook's.
Therefore, i have to expand the ISO, to change the driver - using DISM - offline registry.
But, when i have expand the ISO and changed the driver, i have to burn it,
resp. create an ISO from the expand image again.
Thee is my problem:
When i do this, with - par example - IMGBurn - it tell's me, that i have to take a choice for 8 = for Win 10.

Could this be the problem?  That IMGBurn maybe don't take all 10 files - to create the ISO?

Should i use a better - annother Burner?

At least, in IMGBurn, i found the way, to make it bootable - but are there all files included?  I really don't know.....

16bit problem is solved - i expand the winBuilder ISO's again and checked about 16bit - It's OK


But still, i have the problem, that i can't run the WinBuilder PE SE  and PXE on this mashine.....

As i tild before: In the past, I made some Build's without any problems.

But now, both - PE SE  and PXE - stop with error......

But ONLY on this mashine  -  On the other, it run without any problems.

So, it has to be a problem of windows......
I run "sfc /scannow"  - (of course)  there are no problems.......

Could anyone help me out with that?

I don't want to install Windows again.....

@dazza:

here is the log file, you asked for.

SOLVED - inexplicable way

In a 4 year old German post I found in relation to "cmd.exe could not be copied to", an indication that someone had discovered a superscript comma in the original of their build - folder name as "cause".

 Although that was not the case for me - I still had a guess that I had previously simply rejected: an empty space in the source folder.

Since I had NEVER changed this folder and created several builds without any problems, I did not consider the space.

Now I just changed the name of the source folder - or removed the spaces.

BINGO! - runs like clockwork! NO error message anymore!

Nevertheless, I have to ask myself why with previous, unchanged constellations and names - until a few days ago - EVERYTHING went smoothly!

Or in other words: in previous builds, the empty spaces were present - EVERYTHING worked.

Now - ONLY after I have removed the blanks - it runs again ............

Although it now seems to be solved (at first). I would still like to know why the spaces in the source folder were NOT a problem BEFORE ....

OK - you could accuse me of being a "creepers".

But: I never wanted to die stupid :-)

glad to hear it is now fixed, sorry I didn't get round to checking log and responding sooner

I believe it has always been recommended to not use spaces in your build path somewhere on this forum in the past as well, certainly I remember years back someone telling me for an issue I had and removing spaces solved that as well :)

Yes - i should have noticed that - before 

Btw:
The spaces were NOT in the source folder of the Win 10 Image, but in the folder of the WinPESE Builder!

Anyway:
It will probably remain a mystery, which is why it didn't cause any problems beforehand ...

Here is an example: Note from "Ventoy".
If a USB stick has been prepared with Ventoy,
you should make sure that when dragging and dropping ISO's, you should make sure that the target path includes There are NO spaces 

Normally, i watch about that.....   (but, sometimes NOT    )