Will try to count it to add into release notes. I'm running it on 500GB SDD partition, so I never think about free space during building. I have unreleased similar project for Windows 7 to build perfect AIO where is needed like 400GB free space during building process
I'm collecting DISM 8 language files.. If everything goes without problem, XP2ESD can be adapted to run on XP too, but this needs some tests. Also VHD mounting should be switched from Diskpart to DISM. Will see if it can be done during upcoming weekend
Hi at the step where it installs to the VM [5] it gets stuck at an command window with many "Access Denied" Errors Edit: Error shows only on Home Versions
I managed to make the boot work by changing the diskpart script to dism but now I get an error at the end of the installation saying that it is corrupt or a file called ntoskrnl.exe is missing, what can I do in this case?
Which Windows 10 version is used as input? It's related to "System reserved" partition. For now is setup.cmd designed only for 50MB partition deleting. Also be sure to install it on first partition.
What you mean with Home versions? Do you mean host system? And is Builder launched with admin privilegies?
All editions using same code for VirtualBox installing. Maybe something is wrong on your side.. I have no idea what happed
I succesfully created an DVD but only with Pro and ProN (Retail and Volume) only Home Editions doesnt work
I am using the iso of windows 10 1507 I already eliminated the reserved partition and the system is working I will try to manually modify the setup.cmd so that it eliminates the said partition, what happened but the rest like the dism and that must be corrected I can do The compression will work and the rest of the progress that your script does everything I did (half of the progress) manually changing the paths to location C: \ and well I'm done, thanks for answering!
What size "System reserved" partition was created? It can be easy adapted to delete any size of partition
but why do you create an Account Administrator with Windows XP Home ?! also because after installation there are two accounts ... I deleted the command line where it creates the Administrator account ... yet it works perfectly.
You need to understand some things before you start complaining. This tool is for automated building in all cases without user touch. 1) Fully unattended setup without creating new user is impossible on Home edition 2) New Administrator account works great and cover Administrator auto-login 3) Old broken Administrator is still here, just renamed to AdministratorN - I hope it's explained in first post 4) New Administrator account is before launching OOBE hidden from logon screen using same way as is done in Professinal edition So on Professional edition you get after setup using XP2ESD 1) Your account created using OOBE 2) Adminstrator account - hidden So on Home edition you get after setup using XP2ESD 1) Your account created using OOBE 2) Adminstrator account - hidden 3) AdministratorN account - original one just renamed, but you cannot use it from Microsoft design. - hidden And Administrator account on Home edition is welcome addition
What's the benefit of this over say using Windows XP Integral edition which has all these fixes already completed?