Locked Problem with Sysprep

[LiuBang]

when i install any windows 10 Pro in a VM or real PC and then Sysprep it then capture it using Dism
when i install the capture image on any PC i get a big used Space which is bugged and not used
means there is no files at all that is using it
i used WinDirStat to see where is the space/storage used by what
and this is what i saw in WinDirStat

i had to choose "show unknown files"
the windows in the image is edited it's not original
i don't know why this is happening , and it only happens when i sysprep windows 10 Pro ( don't know anything about others)
i don't do the unattend.xml step and i delete the admin user folder
i don't know what to do or how to solve this strange bug
i don't know what to look for
i used original windows 10 21h2 and 22h2 and same problem
when i boot from winpe , the space is not bugged and the
---------------------------------------------------------
what i realized after some testing , that this bugged space is based on my editing/removing stuff
so in the screenshot you saw up there is 10gb because i removed alot
now look at this screenshot in which i didn't remove alot

so whatever i removed it's size gets bugged , like it's removed but it's still taking space
so if the windows is original and not modified at all (nothing removed from it) there wont be a shadow file or any bug in space
i need help to know why is this happening
why the space gets bugged
i'm tired of thinking


PS:strange thing happen when i install it in VM oracle box this problem doesn't happen and don't ask me why

 

[Un4Given]

try to install VM tools

 

[LiuBang]

try to install VM tools

but what is difference
i mean if the image is syspreped from VM or real machine the result is the same
i get this bugged space
do you think capturing it from Hyper-V would make a difference ?

 

[Un4Given]

but what is difference
i mean if the image is syspreped from VM or real machine the result is the same
i get this bugged space
do you think capturing it from Hyper-V would make a difference ?

Is the problem with these photos only or all photos? on ur PC

 

[LiuBang]

Is the problem with these photos only or all photos? on ur PC

it's not photos problem
it's this bugged space that i don't know why it's happening
see this"Unknown" ?
this is the bugged space , i don't know why is this happening , it only happen when i install a syspreped image on any PC (not in VM)
when i boot from WinPE to see this bugged space , it's just not there , i see the right space (means no problems)
i just want to know why is this syspreping causing this to happen
in all the tests i have done same result with this problem

i also mentioned that the "Unknown" space increase with the same size of the files i remove , means when i edit this syspreped image and delete some stuff from it using NTLite or winreducer the size of the files that are delete gets added to this "Unknown" so it's size increases

 

[Un4Given]

maybe this is a virus or something like that you can delete it and use antivirus malware antivirus

 

[LiuBang]

maybe this is a virus or something like that you can delete it and use antivirus malware antivirus

it's not a virus i got windows defender and avast , i never use my PC without an antivirus
i tried on more than 1 PC same result

what you are suggesting is not based on the facts i'm saying up there

 

[InaccurateFool]

you may have captured unused space from the virtual hard drive

 

[LiuBang]

you may have captured unused space from the virtual hard drive

if that's possible then this unknown space shouldn't increase when i remove stuff from the image , means it should stay the same because it's already captured so it shouldn't change based on what i remove

 

[Jerry_Xristos]

After you do all the customazition in your image you have to clean up the image in order to rebuild it and save space.
On how you can do this its simple............................
Just google it or have a look at these tutorials

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

EDIT August 15, 2021: New Updated build Process. Once you build like this, you can use the other tools (in the lower section of tutorial) to edit the WIM before converting to ESD. NOTE: If video is grainy, change it to 720p. Future videos will be in 1080p. Part 1 ok.....class is in...

www.teamos.xyz

Tutorials - Backup Virtualbox VM and make installable ISO

So, you have installed a Windows OS in Virtualbox, and gotten it just the way you want it. Now you want to save it for posterity, or just in case your current VM has a brain fart and you need to reinstall it. Or, you decide you really like it and want it for a daily driver on a real hard...

www.teamos.xyz

All of this talking here is reffering on how to make a custom build which is not allowed here in our forum.
But because its almost New Year Eve I am going to leave this thread open for a while.
Thread it will be close soon
Good luck

 

[LiuBang]

After you do all the customazition in your image you have to clean up the image in order to rebuild it and save space.
On how you can do this its simple............................
Just google it or have a look at these tutorials

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

EDIT August 15, 2021: New Updated build Process. Once you build like this, you can use the other tools (in the lower section of tutorial) to edit the WIM before converting to ESD. NOTE: If video is grainy, change it to 720p. Future videos will be in 1080p. Part 1 ok.....class is in...

www.teamos.xyz

Tutorials - Backup Virtualbox VM and make installable ISO

So, you have installed a Windows OS in Virtualbox, and gotten it just the way you want it. Now you want to save it for posterity, or just in case your current VM has a brain fart and you need to reinstall it. Or, you decide you really like it and want it for a daily driver on a real hard...

www.teamos.xyz

All of this talking here is reffering on how to make a custom build which is not allowed here in our forum.
But because its almost New Year Eve I am going to leave this thread open for a while.
Thread it will be close soon
Good luck

thanks alot for that
seems it's alittle complicated than i thought to capture a syspreped image to prevent this strange bug from happening