We must have totally different working methods Let's see what I told to be my workflow, and check how that works in reality.

Example W10 x64 VM is one I have used for ESDto ISO and UUPto ISO testing, a clean installed build 15048 with no additional software installed, upgraded several times to builds 15055, 15058, 1501, always restored back to clean 15048.

hyper v compact vhd online dating-17

So it seems Macrium is more efficient but IMO more of a faff.

Microsoft Drive Optimizer Copyright (c) 2013 Microsoft Corp. Pre-Optimization Report: Volume Information: Volume size = 21.99 GB Free space = 15.49 GB Total fragmented space = 35% Largest free space size = 10.97 GB Note: File fragments larger than 64MB are not included in the fragmentation statistics. Post Defragmentation Report: Volume Information: Volume size = 21.99 GB Free space = 15.49 GB Total fragmented space = 34% Largest free space size = 10.98 GB Note: File fragments larger than 64MB are not included in the fragmentation statistics. Post Defragmentation Report: Volume Information: Volume size = 21.99 GB Free space = 15.49 GB Allocation Units: Slab count = 702 In-use slabs = 223 Slab Consolidation: Space efficiency = 100% Recovered space = 1.71 GB Retrim: Total space trimmed = 4.15 GB SDelete v2.0 - Secure file delete Copyright (C) 1999-2016 Mark Russinovich Sysinternals - is set for 1 pass. Press Enter to return to menu: Hello everybody, recently I've installed Windows 8,1 Pro version on my laptop and today I'm trying to install Microsoft Office 2007 Enterprise.

I have it as part of a script that compacts the OS, removes apps I don't want, runs disk cleanup and so on. The whole script takes an hour to run I guess but it saves thinking.

Please do not take this wrong, I just have to say that your process involves awfully lot unnecessary work!

Kari I always avoid defrag as it usually takes so long.

Minitool does the same in effect in a fraction of the time. Edit: I have just seen this Compacting Client Hyper-V VHDX Files Helge Kleinsdelete writes zeros to free space.

To start with, a dynamically expanding VHD can only grow.

It never shrinks, that's not what Compact Disk means.

Before I learned that VHDX expanding disks do not release space, many of these have swelled way beyond what is used of needed because I did a defrag.

Defrag will use temporary space to store files parts being defragged.

b) mount vhdx in host disk management c) shrink c drive to minimum, the re-expand to full size using minitool partition wizard or similar d) image backup vhdx using Macrium Reflect e) create new vhdx f) restore image backup from Macrium Reflect to new one (renaming old to and new name to old name). 1 Samsung 840 EVO 500GB | Windows 10 (EFI) - Velocity DUOx2 PCIe 1 Samsung 840 EVO 1TB | mac OS 10.10.5 - Velocity DUOx2 PCIe 2 Samsung 840 EVO 500GB RAID0 | Scratch disks - Velocity DUOx2 PCIe 2 WD RED 2TB - 4TB RAID0 | Data disks 2 Samsung HDD 5 I always avoid defrag as it usually takes so long.