Tips & Tricks Windows 10 Building and Modding and Custom OS"s

[Proteus]

@00Proteus00 i know i annoying you too much but I'm so sorry
i did every step as you did in Video tutorial and i take the unattend of yours and past it in notepad and save it without any change and copy it in sysprep dir
before i make sysprep last step
and make iso and install it and unfortunately i didn't find the customization that i did and ill tell you what i did step by step
enter audit mode
boot to audit mode
install programs
make customizations with aero tweaker and win 10 tweaker
install uxpatcher and icons
reboot
copy unattend.xml to sysprep direction
choose generalize and shut down
make iso with my autounattend.xml with my own settings like Name language skip EULA etc
vmware install windows and the same result
** another try i copy unattend.xml to sysprep before any install and customization
the same result
can you please if you have time make the step of unattend.xml in video to make the tutorial completed
or tell me what i did wrong

Couple of things for ya, then Im done. We CANT talk building in public, and it must be done in PM.

1 - My build tool link with tutorials & tools

http://mythology.theworkpc.com

2 - My UNATTEND.XML
Copy and paste into notepad. Save as ALL FILES then save as UNATTEND.XML
Put file in C:\Windows\System32\Sysprep ANYTIME before you check the box and finalize the build.

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="specialize">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <CopyProfile>true</CopyProfile>
        </component>
    </settings>
</unattend>

 

[nassernody]

Couple of things for ya, then Im done. We CANT talk building in public, and it must be done in PM.

1 - My build tool link with tutorials & tools

http://mythology.theworkpc.com

2 - My UNATTEND.XML
Copy and paste into notepad. Save as ALL FILES then save as UNATTEND.XML
Put file in C:\Windows\System32\Sysprep ANYTIME before you check the box and finalize the build.

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="specialize">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <CopyProfile>true</CopyProfile>
        </component>
    </settings>
</unattend>

thank you bro so much for your patient and your help

 

[Loveena]

thank you bro so much for your patient and your help

Yes,
All our Mods/Admins have exceptional patience indeed

 

[Andy caulin]

thank you very much sir

 

[sjsl061687]

Thanks for the tutorial, i just finished my 21H2 build, i successfully bypass the problem with command promt not typing "\", it only types # on command prompt but anyways successful on first build thanks to you

 

[k3rb3r05]

Thank you much for your guide.

Would it make a difference if disks were VHD instead of VDI?

 

[Proteus]

Thank you much for your guide.

Would it make a difference if disks were VHD instead of VDI?

no difference at all. VHD is easier to work with, since there are tools to access the VHD once created.

 

[kittrie]

oh man, this thread is awesome. I am so delighted how everyone is patient with helping others in trying to make their own win builds.
I hope I will do that with windows 11, but my mind is too preocupated with other things now, so I don't have the attention span or mental composure for a task like this.

but I am so greateful something like this exists, you are all wonderful !!

 

[skole75]

Awesome, thank you for the post!

 

[Morph69]

ive done this all the way to the diskpart part and each time i try no matter what drives i choose it kicks out with the dsipart help (diskpart /?) message. ive even gone to the ms page and i get the same error's.
my disk loads in the vm are c, d, e c for the system recovery d for storage, e for windows and no matter what i do it will not work

 

[Proteus]

ive done this all the way to the diskpart part and each time i try no matter what drives i choose it kicks out with the dsipart help (diskpart /?) message. ive even gone to the ms page and i get the same error's.
my disk loads in the vm are c, d, e c for the system recovery d for storage, e for windows and no matter what i do it will not work

try the "video" method. I changed the way I do it now. Its much easier to bypass that, and after sysprep, just mount the VHD and make the WIM from there with DISM++. Saves a lot of time too. Afterwards, just unmount the VHD and good to go

 

[Morph69]

Okay cool thanks i'll give that a go

 

[lbchX]

@00Proteus00 am i right, or your site is down

http://mythology.theworkpc.com/

?

 

[Jerry_Xristos]

@00Proteus00 am i right, or your site is down

http://mythology.theworkpc.com/

?

This has nothing to do with the thread.
Please send a PM if you want or ask from proteus to contact you because you want be able to as a registered user.

 

[loader72]

Many thanks to all who contributed for this exercise of brain expansion. peace.

 

[Garth_Vader]

Spank ur ferry much...
Lots of thx...

 

[SnowMonkey]

Nice work OP, thank you for sharing the love

 

[jasonetwork]

I finally found a tutorial to create smaller windows lite

I'm sorry I only speak Spanish and I can hardly translate all this

 

[Jerry_Xristos]

I finally found a tutorial to create smaller windows lite

I'm sorry I only speak Spanish and I can hardly translate all this

Use Google translator

 

[dupa9524]

Is there a list of windows services or compononents that are required for sysprep to run properly. I used many debloating tools such as blackbird recommended on the forum. When generalizing the image, sysprep hanged and the error log was something like
>couldn't acccess componentsomething fatal error code 0