Enable Deduplication on Windows 10

Enable Deduplication on Windows 10

Because of many comments about the fact that after upgrading your Windows 10 computer to a new version (most of the time Insiders release), deduplication features are not working and so your deduplicated volumes and data are not accessible anymore. Let me remind you that, it is a non-Microsoft supported deduplication package which is built for a specific version of Windows 10 based on Windows Server 2016 native features. It means that I cannot create a specific Windows 10 build version of this package without having the Windows Server 2016 corresponding build.
Use this package at your own risks, and note that I am not responsible for any data loss/business loss, device corruption or any other type of loss due to the use of this package.

Any build (based on 16237.1001)

The following package is compatible with any W10 build starting from 10240 (and x64 bit system). This package is different from the others as we cannot simply use DISM. This version is based on work of members of mydigitallife.info forum and adapted by me with 16237.1001 source files. You can find instructions and credits in the readme.txt file and download the package here.

Build 16237.1001

Based on Windows Server 2016 insider build, I created the deduplication package for W10 build 16237.1001 that you can find here. Note that DISM requires the exact same build to deploy the package and so the features. And as Microsoft is providing a lot of minor builds, I am working on the creation of package which is “minor build agnostic”.

Build 14393.0

Hello, I was very busy these last few months and I got no time to work on this blog… Anyway, I made the new Dedup Package for build 14393.0 that I tested on my W10 14393.187 and it is fully functional. You can find this package directly from here (md5: 48cdbfddcc4a2266950ad93a6cfe2b9f).As always, to install deduplication feature on your Windows 10 computer, you will just need to launch install.cmd file as administrator. Enjoy.

Build 14300.1000

You will find the deduplication package for build 14300.1000 here (md5 : 6a7ba5b2d6353cc42ff2c001894f64b4). As usual now, to install deduplication feature on your Windows 10 computer, you will just need to launch install.cmd file as administrator. For information, this package is only working for x64 platform (don’t forget to open x64 version of PowerShell to access deduplication cmdlets).

Note that I can only build this package if I have the linked Windows Server 2016 build, so if you need a special package for a build of Windows 10 contacts me with the link or the .iso of the appropriate Windows Server 2016 build.

Build 14291.1001

You will find the deduplication package for build 14291.1001 here (md5 : b150cd2fe60e314e24cedeafeb6f1f42). To install deduplication feature on your Windows 10 computer, you will just need to launch install.cmd file as administrator.

Build 10586

You will find the new package based on Windows Server 2016 TP4 build 10586 here (md5 : 21251c030d3c1a5572bd0f12473c623c). To install deduplication feature on your Windows 10 computer, you will just have to launch install.cmd file as administrator and voila!

You don’t need anymore to be part of Microsoft Insider Program for this build. So just skip text above until PS module usage here. If you want more information about available cmdlets and usage, you can read my article here.

Build 10514

Until now if you wanted to make use of deduplication on your Windows client operating system, especially on Windows 8.1 you had to reuse deduplication module of Windows Server 2012. But as you probably know, Windows 10 still does not provide this functionality by native, and the old module used for Windows 8.1 is not compatible… So perhaps you still have not migrated to Windows 10 because of this ?! Well, I’m glad to announce that those dark times are about to end. A friend of mine (http://www.slr-corp.fr) worked with other people on this project during the summer to bring this functionality to Windows 10. Now let’s see how we can do this.

First download the package here. (md5 : b7ed10bf8b8fbc312a7b35d2ffd0eef3)

Then you have to join Microsoft Insider Program.

When you are part of the insider program. You can now unzip the downloaded package (copy to your local disk) and run Install.cmd as administrator.

At this time you will need to restart your computer. When it’s done, open a PowerShell prompt (as administrator) and change your execution policy (if not already done) to Bypass.

Then, you have to import the PS module, enable deduplication on volume and finally start the job.

You can follow the execution of the job with the command Get-DedupJob and have a status of savedspace and savingsrate with command Get-DedupVolume.

As you can see below, here the concrete result of deduplication. I have a folder with all my Hyper-V machines that normally would take 376 GB but thanks to deduplication, it only takes 81 GB.

36 thoughts on “Enable Deduplication on Windows 10

    1. Hello,
      As I said on Twitter, as soon as I can get a Windows Server 2016 in build 15063, I will work on the Win10 Dedup package for W10 creators update 🙂

      1. Arthur,
        First off, really appreciate your past work and putting this blog together!

        You had noted the first part of April that you were awaiting access to “Windows Server 2016 in build 15063”. Any luck in accessing this build or update on the package for the Creators Build?

        1. Hello,
          Thank you for your support.
          And to answer your question, no I still not have access to Windows Server 2016 build 15063… But be sure that when it will be the case, dedup package will be provided shortly after. It seems that a lot of people are waiting for it, except Microsoft 😉

  1. I have setup a server2016 essentials and deduplication is not on the features list to enable. none of the power shell commands work either. in server2012r2 essentials I was able to turn this on with nothing special. in see in the winsxs folder that there is several dedup folders. any idea if dedup works with essentials 2016?

    1. Hello,
      After some tests, I confirm that the latest version of my Dedup Package works perfectly with Windows Server 2016 Essentials edition as long as you are using build 14393.

  2. This tested successfully on a fresh install of 14393.0. My pc has been updated over the past few months and this process does not work now that I am on 14393.1066. Is there a trick to make this work on newer versions or do you plan to release an updated version?

    Thanks, keep up the awesome work!

    1. Hello Jesse,
      This package is still working with build 14393.1066 on my personal W10 computer and my other W10 VMs. Do you have any error ? (e.g. using PowerShell cmdlets)

  3. Hi Arthur,
    how it’s the whole think working?
    If i make it run on build 14393 and then upgrade windows I will never be able to use the files, or only til the next package from you (or rollback)?
    thank you

    1. Hello,
      If you upgrade your windows build version to creators update, you will not be able to use the deduplicated volume and so the data on it. I suggest you to wait before updating your Windows 10 if you want to take advantage of the deduplication feature. And as mentioned on my twitter, Microsoft will soon onboard Windows Server as part of Insider program. So I should be able to provide this deduplication package for each new build of Windows 10 (if they follow the same roadmap).

  4. One small hiccup in the universal package, the scripts are blocked due to being a downloaded source. The usual unblock-file and Set Execution policy fails due to the folder being owned by trusted installer. You can allow the script to be run each time (after answering R about 8 times) but to get it to ‘Stick’ I had to take ownership of the folder, set the scripts to inherit from the parent and then give access to the file so I could choose “unblock”.

    1. Resolved the issue, you have to unblock the .zip file after downloading the build. The readme does mention unblocking a file however it references a .7z file which does not exist, perhaps change it to reference .zip and clarify that it’s the entire downloaded package?

      1. Hello,
        Thank you for your comments, I updated the package with appropriate modification on Readme file.

        1. Thank you for all the effort and work that you put into this, The universal package is a great idea, glad you were able to get it worked out.

  5. Hi Arthur – I upgraded from Windows 10 1607 to 1703. Before upgrading I disabled dedup on my VM drive. Since I’ve upgraded Windows I can’t access the data on that drive. However I can browse over to it and see it I just can’t do anything with it include move off the drive. Any recovery tips would be much appreciated.

  6. Hi,

    I can’t get the latest dedup package (Any build (based on 16237.1001)) to work with my win 10 enterprise build 15063.540
    A dedup job will go from initializing to not existing anymore without optimizing anything.
    Any suggestions on what i can try? I can

      1. Hi Remy, first thank you for this post.

        This is also happening to me too.

        This is the schedule I created “New-DedupSchedule -Name “NightlyOptimization” -Type Optimization -DurationHours 11 -Memory 100 -Cores 100 -Priority High -Days @(1,2,3,4,5) -Start (Get-Date “2017-08-25 23:00:00″)”

        And when I ran it manually “Start-DedupJob -Type Optimization -Volume G: -Memory 100 -Cores 100 -Priority High”


        1. I tested it this with Windows LTSB version 1607 build 14393.1715 in a VM same results. Dedup job go from initializing to not existing without doing anything. Any tips on this? Thanks

          1. Had a similar problem, resolved by installing newer package from mydigitallife:
            >Dism packages, only for build 16299.15 (Windows 10 version 1709)

          2. Hi,

            same problem here. Version 1709 build 16299.309. Dedup job go from initializing to nothing 🙁


  7. I also tested on 10.0.16299 and I get the same result. When I check get-dedupstatus | fl
    under LastOptimizationResultMessage it says

    the job was terminated while in a handshake pending state

    the lastoptimizationresult is


  8. This package was working great for me for many builds but doesn’t seem to work correctly with Windows 10 1709 (16299.64). Any idea if that’s the same for everyone or when an update will come? Thanks for all the hard work!

  9. This package was working great for me for many builds but doesn’t seem to work correctly with Windows 10 1709 (16299.64). Any idea if that’s the same for everyone or when an update will come? Thanks for all the hard work!

  10. Also having an the same error in 16299.248. Goes from initializing to no job.

    LastOptimizationResult : 0x80565342
    LastOptimizationResultMessage : The job was terminated while in a handshake pending state.

    Seems we need a new version.

  11. For anyone in 2018 looking to do this: Seems like (as of mid-May) the version listed here do not work. Running a dedupe job goes from “initializing” to Failed. Further inspection reveals it terminates during a handshake (I’m guessing when Windows is doing a lot of talking among its parts). Frustrating, considering I’m looking at some of my drives (via ddpeval.exe) with savings potentials of 25%+, and others nearing 50% (ISOs, etc.). 🙁

  12. Hello Arthur, could you please help us make a 1803 version 10 package? or if you can make a package available to us. Let’s take a lot of your work !!!

  13. I really love the work you have done for all of us, but this project seems a little dead?

    @Arthur REMY have you abandoned it entirely?

Leave a Reply

Your email address will not be published. Required fields are marked *