With this November Rollup that is huge my windows 8.1 images doesn't fit on dvd5 (4,7 gb) even it is ESD is there another way of shrinking?
Huge difference between installing Windows, updating it afterwards and installing an already updated Windows. @ OP Iirc not much without crippling it. In case you mounted it then did unmount/commit without exporting it afterwards, export it to a new WIM, that can dramatically decrease the WIM size (for me from 5,3 GB (after unmount) for three indices to 4,6 GB after exporting it).
s1ave77, what do you mean ? It's not simple ? Installing Windows 8.1 with update, and then the last 2 Updates : KB2934018, KB2959977 and then November rollup ?
That can last a lot of time depending on the system, wheras the install of a fully updated Windows lasts as long as installing untouched MS version.
but almost everyone said: the november update contains al of the updates t/m april it isn't if you integrate only the november update you will get 44 updates after installation. am i right? and resetbase what do you mean ?
It's a feature available with Windows 8.1 (not Windows 7) that, in the simplest of terms, removes all the backups of previous versions that exist on the system. This includes the versions of the files from the original installation of Windows if newer versions are present. It also means that updates cannot be uninstalled because the previous versions are no longer present on the disk. It is safe to use, unless Microsoft somehow managed a major faux pas. It's done by running (from an elevated command prompt): dism /online /cleanup-image /startcomponentcleanup /resetbase If you run it without the /resetbase command, you are still able to uninstall updates, but the process takes considerably longer. It also saves much less space, as the original files still exist in the form of a 'delta'. What this means is, the difference between the current update at the time when you ran the command, and the earlier files, is saved. Before running the resetbase command, you should run: sfc /scannow dism /online /cleanup-image /restorehealth This is just a precautionary measure to resolve any issues that may exist.
if wim size is no issue, one could in theory resetbase from winpe pass or setupcomplete.cmd phase during installation. poor man's method to avoid sysprep at all costs.
Yeah, but resetbase at setupcomplete stage ... setup can take up to an hour then (depending on the system first run can last a while) .
Don't know. I'm gonna give them until next month before I start integrating it. They haven't exactly been putting a lot of effort into 8.1 lately so I'm guessing they're working with a skeleton crew.
Would explain all the problems over the last months ... hopefully they don't screw it in the end, it's running nicely here .
After installing the update and doing this dism /online /cleanup-image /startcomponentcleanup /resetbase the update took up an extra 1 GB. However, restoring the image the next day led to almost no increase in overall size (+100-200 MB). I have seen that the impact of dism cleanup takes 1-2 restores to be complete. Even on a clean windows 8.1 (no software), the image with (nov 2014 rollup+updates) is almost equal to (april iso+apr-nov updates+nov rollup). So overall there should be no extra space taken up by nov 2014 rollup.
Not quite sure what you mean there acyuta! The November update plus the other updates and previous rollups, once you run /resetbase, shouldn't take up much more than a fresh install of just Windows. This is because it removes the old versions of the files, so the difference in sizes is primarily the difference in size of the files in the updates. Of course, it doesn't quite work that way, but it's close enough . The free space on the drive should be less because of the new features added, USN journal differences etc.