I think WIMBoot is 'deprecated' - the command will still be there (which for one thing means you can still use the same version of DISM to work with Windows 8.1), but it isn't the preferred route for Windows 10.
Ben Hastings said:
If you go to an elevated command prompt, and type this command, what does it say?:
I'd expect it to say 'The system is in the compact state'
I believe that instead of WIMBoot, in Windows 10 there are two technologies for compression:
- Compact OS (as per the command I mentioned above) - which is about the OS
- 'Single-instancing' your applications, so that applications are run from a 'Provisioning Package' which has been created for use with Reset and Recovery Drives
The compactOS setting should be determined automatically when you install. When I tried to upgrade my tablet it set the CompactOS flag as expected, but when I tried a clean-install later, probably because it was missing some key drivers, it didn't figure out that it could compact it. However I think you can switch it on and off with these commands:
The single-instancing of applications is done with DISM, and I have to admit I've not been brave enough to try it yet. I don't think it happens automatically when you upgrade from 8.1 to 10.
I'm also not sure whether you can do it on a running installation or if it needs to be done before first use. I know how to create a Provisioning Package but it's not clear to me if "DISM /Apply-CustomDataImage" creates a new Provisioning Package itself or if I need to create it first. Also I'm not sure how it works when you subsequently update applications (eg. applications like Firefox frequently update themselves), if they are stored in a .ppkg file.
I'll get round to doing some playing with single-instancing in a Virtual Machine at some point.
Further reading if you're interested:
Compact OS, single-instancing, and image optimization
How Windows 10 achieves its compact footprint