Tiny11 Core iso larger than official Windows iso

[Swordmaster3214]

I downloaded Windows 11, English, 24H2. The file size was 5.41 GB. I went through all of the steps, and sat back and relaxed as I was told. When it was finally done, the resulting iso was a whopping 12.8 GB. That is literally twice the size I originally started with. I do not know what went wrong, a lot of errors did show up during the process, but I thought that was normal, considering how late I am to the party. I attached the tiny11.log for review if necessary.

[wealstarr]

1.Export-image
2.CleanComponentStore

[hyryel]

hummm, according to your uploaded tiny11.log,
It seems that, when the process was creating the image, it couldn't delete the original .wim file, so, your new image contains the original wim file and the new one, thus the double size.

I think, when choosing the index at the beggining, you pick one version with "version N", wich is already trimmed by a lot of software.
You should try to redo the procedure, but choosing a "standard version" (ie: without the N)
Windows Professional
instead of
Windows Professional N

You can find theses lines starting at line 11568
`Deployment Image Servicing and Management tool
Version: 10.0.26100.1150

Exporting image
[==========================100.0%==========================]
The operation completed successfully.
Remove-Item : Cannot remove item C:\tiny11\sources\install.wim: The process cannot access the file
'C:\tiny11\sources\install.wim' because it is being used by another process.
At C:\Users\Daniel\Downloads\tiny11.-.nov24\tiny11builder-main\tiny11Coremaker.ps1:687 char:1

• Remove-Item -Path "$mainOSDrive\tiny11\sources\install.wim" -Force >n ...

•   + CategoryInfo          : WriteError: (C:\tiny11\sources\install.wim:FileInfo) [Remove-Item], IOException
    + FullyQualifiedErrorId : RemoveFileSystemItemIOError,Microsoft.PowerShell.Commands.RemoveItemCommand
  

Remove-Item : Cannot remove item C:\tiny11\sources\install.wim: The process cannot access the file
'C:\tiny11\sources\install.wim' because it is being used by another process.
At C:\Users\Daniel\Downloads\tiny11.-.nov24\tiny11builder-main\tiny11Coremaker.ps1:687 char:1

• Remove-Item -Path "$mainOSDrive\tiny11\sources\install.wim" -Force >n ...

•   + CategoryInfo          : WriteError: (C:\tiny11\sources\install.wim:FileInfo) [Remove-Item], IOException
    + FullyQualifiedErrorId : RemoveFileSystemItemIOError,Microsoft.PowerShell.Commands.RemoveItemCommand
  

Rename-Item : Cannot create a file when that file already exists.

At C:\Users\Daniel\Downloads\tiny11.-.nov24\tiny11builder-main\tiny11Coremaker.ps1:688 char:1

• Rename-Item -Path "$mainOSDrive\tiny11\sources\install2.wim" -NewName ...

•   + CategoryInfo          : WriteError: (C:\tiny11\sources\install2.wim:String) [Rename-Item], IOException
    + FullyQualifiedErrorId : RenameItemIOError,Microsoft.PowerShell.Commands.RenameItemCommand
  

Rename-Item : Cannot create a file when that file already exists.

At C:\Users\Daniel\Downloads\tiny11.-.nov24\tiny11builder-main\tiny11Coremaker.ps1:688 char:1

• Rename-Item -Path "$mainOSDrive\tiny11\sources\install2.wim" -NewName ...

•   + CategoryInfo          : WriteError: (C:\tiny11\sources\install2.wim:String) [Rename-Item], IOException
    + FullyQualifiedErrorId : RenameItemIOError,Microsoft.PowerShell.Commands.RenameItemCommand
  
  

Windows image completed. Continuing with boot.wim.`

[Swordmaster3214]

Thank you for your reply. Unfortunately, I didn't choose an N version of windows, I chose index 1, Windows 11 Home. I am not sure why it wouldn't be able to delete the file, I gave the thing permission and inside an administrator Powershell.

1.Export-image 2.CleanComponentStore

Could you please clarify? Thanks.

[hyryel]

Hello, the log only says
Remove-Item : Cannot remove item C:\tiny11\sources\install.wim: The process cannot access the file
'C:\tiny11\sources\install.wim' because it is being used by another process.

I played with DISM quite a few times, and more often than that, the dism tool is not able to dismount image due to file used by another process.
The script file od Tiny11 is a quite complexe script and the only thing your log show, is that the file "install.wim" is in use by another process.
WIM file are compressed image of windows installation. When using DISM, the file is uncompressed in a temporary folder and mounted in a virtual environment to apply update, remove or install app and do other OFFLINE task.
When dismounted, the file is repackaged to a WIM file ready for installation.

I can't provide any further information, sorry

[Swordmaster3214]

I mounted the ISO that Tiny11 Core spat out and found out that there are indeed two install.wims, one named install and the other named install2. I am assuming that install2 was the one that was created by the script, both because of the name and the smaller size compared to install. However, even if I remove the original install, the resulting size of the image would still be 8.3 GB, which is considerably larger than the default Windows image. Is there something else going on?

[Swordmaster3214]

I have just now learned about the ESD file that was also taking a lot of space in the image, but only 3.3 GB, and found out that it is actually a smaller version of a WIM file. (May be oversimplifying things.) Maybe Tiny11 Core created the ESD file, and that is why many users are claiming a 3.3 GB install? And, in case this is true, should I delete the other two install files, so it uses the smaller file and thus makes the ISO smaller?

[Swordmaster3214]

Now I am wondering if the ESD came from Tiny11Core, or if it is the default Windows ESD. Should I convert the install2.wim to an ESD just to be safe?

[hyryel]

Hello,
You did your research well. The install.wim is the original, you can remove it.
BUT, you should rename 'install2.wim' to 'install.wim'.
I think the 'install.esd' is also the original file. You can remove it.
You can find on the internet many tutorials to convert 'install.wim' into 'install.esd'.

You can try this one :
https://www.wintips.org/how-to-convert-install-wim-to-install-esd-or-vice-versa/

[Swordmaster3214]

Alright, problem essentially solved. I'm just going to leave this here and let the dev close it so they know. The final size is still a bit bigger than what everyone is claiming online, but at least it is smaller than the default Windows install.