abbodi1406 Thanks! I installed your DISM dedup package on win 10 1803 and it works! Started scrubbling dedupjob and it not found any errors.
As of today 5/11, download of the Dedup_17134_Manual.7z package no longer trigger Windows defender alarm. Maybe an updated Windows defender signature file removed the false alarm on these files...
It took a surprising amount of hunting to find this. I was fairly close to grabbing a Server 2016 ISO and pulling packages from it myself, but I would've been like a bull in a china shop. It would've been bad.
Hi All, I'm Currently Running Windows 10 insider preview Version 1803 OS Build 10.0.17672.1000 And Missing The DeDuplication Feature. Is There Gonna Be A DeDuplication Fix/Patch For This Insider Build? Thanks In Advanced...
In general, to make a dedup working in Win10, you must install same build server OS in VM and use SxSextractor to get dedup install files as cab. Bring them to Win10, use dism /add-package to add and later just enable feature. As for 17672, as I see, there was no such Windows Server Insider Preview build. If you need dedup on client, use only those builds, which are common between client and server - eg 17666. There is a dirty trick of porting binaries between builds, but I won’t recommend that, just wait for next build common to client and server.
Does anybody know what purpose is that job type for Start-DedupJob -Type DataPort I wonder If there is a (mayby not yet documented) way to move deduplicated volume content between servers
Hi moderate and all others here I'm trying to install deduplication on Win8.1. It looks like dedup files in 2012r2 are different from the old one, which is not a surprise as dedup bugs being discovered and fixed since 2013. I'm trying to capture the new file using tools that I have found on this forum (namely, SxSv1 & SxSExpander). Unfortunately, I cannot make them work. The main cab (Microsoft-Windows-Dedup-Package-amd64-6.3.9600.16384.cab) is incomplete. It missing files from dedup-common folders. Pls, advise hint a solution.
Thanx for the prompt feedback. Can you briefly outline how to extract cabs? Which tool did you use? I've checked SxSv1 log. It looks like it pooling manifests for old versions, where no files are available (being cleaned up) in WinSxS. As the result the output cab being generated without many files, though newer versions do exist in the assembly folder. Your file is better than the ones I found elsewhere, but still it is based on 2016 build. Patched 2012r2 have files that being patched just recently.