So, looking at those values for each image shows something a little more reasonable: Windows 10 releaseīut again, those don’t match: Windows 10 20H2 as we see it applied to the disk above is about 7.79GB, not the 5.80GB reported in the table (presumably because the disk allocation for files is done at a block level, and with a whole lot of small files, there’s a lot of wasted space, which is why Compact OS was created). The “TOTALBYTES” value matches what DISM reported, but the “HARDLINKBYTES” takes into account the duplication of files between C:\Windows and the WinSXS folder. If you go back to the old ImageX.exe tool (which is still available in the ADK), you can see two different numbers, again for Windows 10 20H2: So what gives? Well, it appears that DISM is reporting the size consumed by all files, not taking into account the hardlinks that are used for pretty much every Windows 10 file, so as a result the size reported is about double what it should be. For example, this is what you get from Windows 10 20H2: DISM /Get-WimInfo /WimFile:d:\sources\install.wim /Index:3)? You get these values, which would be decompressed sizes: Windows 10 releaseīut those are actually too big: If you apply one of those OSes to a hard drive and then look at the used disk space, you’ll find that they’re about half of that size.
Alright, but what if we ask DISM for the size of just the Enterprise image (e.g.
If we look at the ISO sizes, we see steadily increasing sizes: Windows 10 releaseīut there are some extenuating circumstances there: The first three (1703, 1709, 1803) were just Windows 10 Enterprise, while the rest of the ISOs contained multiple images. Those are surprisingly hard questions to answer, because it’s hard to get a consistent answer from the available tools. So how big is it, and how has that changed over time? So we’re talking about the “ultimate thin image,” straight from the Windows 10 media. And if you’re patching the image yourself (don’t bother, just download updated ISOs periodically), you have to go through great pains to get the size back down again (component cleanup, export, etc.). Of course that assumes you aren’t adding anything to the Windows image yourself (e.g. (Remember Compact OS, which I talked about back in 2015? It’s still around, just not used too much.)
16GB) drives, but those never really worked out very well because the OS would typically start off at about 8GB (decompressed) and slowly grow from there (a.k.a. Over time, there were a variety of efforts to try to squeeze the OS so that it could fit on smaller (e.g. Over the years, there have been plenty of discussions about the size of Windows images.
0 kommentar(er)
