WIM files are technically Windows Image files, but that doesn’t mean they are limited to creation of Windows images, you can create whatever you want. So for 20 GB of installation, the user must have over 60GB of free disk space, which is outrageous.Īs Aaron reminded me, you could use WIM files to tackle all the problems. The 20+ GB of installed files on the machine.The 20+ GB of extracted files from the archive.exe done with 7-zip), it means that he must have enough disk space for: If the user downloads a 20 GB ZIP file (or self-extracting. But here comes another issue.Įvery type of archive you make, has the downside that you must first extract it before you start the installation. Create a bundle/exe with Advanced InstallerĪs you can see, the most common answer you can find is “create an archive” to save up space.Create a zip file and extract it before the installation.You can tackle this problem in multiple ways: Why? Some bits were lost, thus leading to countless retries. There is also a possibility that the package is downloaded, but at the end the hash will fail. By default, each distribution point retries to download the sources in case they fail. When you distribute a package on all the distribution points, network issues will occur, trust me. The issue is simple, large packages are a nightmare to deal with in an infrastructure for large organizations who have distribution points all over the world. I haven’t used this in a long while, since i haven’t dealt with large packages for some time. Visual Studio, and it brought up some memories. Recently, I’ve came across Aaron’s response to a tweet regarding large packages like Autodesk, Adobe.

Wim zip