I notice that all my windows 10 machines with deduplication package installed were not offered 1909 feature upgrade when I ran windows update...
As of today 5/11, download of the Dedup_17134_Manual.7z package no longer trigger Windows defender alarm. Maybe an updated Windows defender...
Not sure if it is real: Windows defender detected a trojan Win32/Spursint.F!cl in the Dedup_17134_Manual.7z package.
I created a duplicate file copy and set minimumfileagedays to 0 and started an optimization job. The jobstatus showed "initialization" and then...
Have you tested that the deduplication processes were effectively executed? That would be great if the 16299 package is fully compatible with 17134.
I installed dedup_16299_DSIM package on a Windows 10 Pro system already running hyper-V after upgraded to 1709. I did not encounter any issues...
I just read your post today and tested my system (W10 Pro 14393.222) installed with the dedup package Dedup_10.0.14393.0.zip. I can confirm that...
Same problem with Win 8.1 Pro upgraded to Win 10, both in a VM and in a physical PC.
