2 problem found so far. 1- Don't recognize my w10 iso [en_windows_10_consumer_editions_version_22h2_x64_dvd] 2- wtf is this error … ? i have like 100 gb free ? Code: ERROR: Cannot set length for output file : There is not enough space on the disk. : C:\Users\Administrator\Desktop\Slimdown10\DVD\sources\install.wim - if you familiar with regex. Win10*22H2* could be better - fail to detect index, not index info my friend
Yes, because it searches for Win10_22H2_*.iso It is easy to fix and cosmetic. Will fix it with next release. EDIT: Version 1.10 now searches for any ISO names. Issue solved! I have never experienced that while testing tens of times. It seems that the message comes from 7zip command line which unpacks your ISO to the DVD folder. It can be circumvent by manually unpacking content of your ISO/DVD directly to DVD folder (instead of putting your ISO image to Slimdown10 folder), then run the script. The script will use the content of DVD folder automatically and will do its job normally. PS. I hope that your run the script from NTFS partition, not from exFAT or FAT32. Because it looks like you would have some limitation for large files (over 4GB) or 7zip has some bug. Unless install.wim is properly and fully extracted, the tool simply cannot do its job. Almost entire its job is to modify DVD\sources\install.wim file. If the file is not unpacked (it should have over 4GB in size) or corrupted, the rest will fail.
Please note, the tool is well tested. This is what I have done: 1. I have downloaded original Win10_22H2_Polish_x64.iso (language doesn't matter) directly from Microsoft. 2. I have installed the above on my HDD, by doing clean install (ie. I have removed all partitions and let the Win10 installer to recreate them). 3. I have activated newly installed Win10 using KMS_VL_ALL without even connecting to the internet. 4. I have unpacked Slimdown10_v1_00.7z on my Desktop and put Win10_22H2_Polish_x64.iso to Slimdown folder. 5. Internet connection will be needed only to download updates (it may be done automatically by the Slimdown10.cmd tool or by auxiliary PreDownloadAllUpdates.cmd tool) Internet connection is not needed anytime later. 6. I launched Slimdown10.cmd, waited, then chose Pro edition (any edition could be chosen) and waited, waited, waited. 7. The newly created ISO was Windows10_x64_pl-PL.iso. 8. I have repeated the above with Win10_22H2_English_x32.iso and installed both on VitualBox and on a real desktop PC. Everything with no errors anywhere.
new version work ok let's hope it will finish ... dism sometimes cause my computer - to crash with nice BSOD Edit. like I predict fail at install updates stage Yes. Crashed again .. wtf is wrong with dism ?
For me, DISM crashed only when launched inside VirtualBox. On real desktop PC it never crashed. But you can disable one setting ie. set IntegrateUpdates=0 inside Slimdown10.cmd, as it requires a lot of resources (memory) to integrate latest updates to the install.wim file (latest Win10 cumulative update package is larger than 700MB) You can always update your system later, after installation, instead of slipstreaming updates directly to the installation media. PS. If DISM didn't finished correctly on your system, run UnmountCleanUp.cmd to clean the remnants and start again. It is always safe to run UnmountCleanUp.cmd , as it unmounts registry keys, unmounts mount points and cleans the mount folder.
But there is no magic in DISM. I have not used any dirty tricks, but only those officially documented by Microsoft. Maybe your DISM is too old or so ? I have used Windows 10 22H2 as host and guest OS. And I have used builtin DISM there (with no additional Assessment and Deployment Kit installed) My machine used to build is pretty old (Lenovo M82 i5 with 8 GB RAM and classic 500 GB HDD). PS. DISM crashed me only inside VirtualBox, but there were only 50 GB of virtual HDD and 4 GB of RAM.
I understand but it should not happen. I have launched it tens of times (plenty of testings) on my machine, it never failed. Never on my Lenovo M82, which is relatively old PC. Only on VirtualBox it crashed, but I suspect that it was due to too low resources (RAM, disk space) I have assigned. BTW. I have not seen BSOD since Windows 98 era.
Given how much I liked Integrate7, I will absolutely test this. prime-expert.com/articles/b26/stop-disk-check-from-running-on-every-boot/ This might be included as a configuration switch, for those who want to dual-boot Win7 and Win10. By the way, did you delete your Integrate7 thread from sevenforums?
I have license for Pro on every single computer in my company. If I would like to use LTSC versions, I would have to upgrade licenses and pay. My modded versions are still legal, as I have not modified any binary files (only settings are heavily modified, which should not break license).