[Deduplication + DrivePool = NO GO, since Windows 16299 (1709, Fall Creators)]

Hi

I' use the MS deduplication and DrivePool both since the beginning.

I never had any major problem with them, aside some calculation glitches with older DP releases.

Now I'm in troubles.

The deduplication of Windows has changed a bit since the build 16299 or so.

A disk previously deduplicated with Win10 or Win server 2016, after being touched by a recent W10/Server 1803/1809/Server 2019, will be silently upgraded and the deduped files become inaccessible by older incarnations. So downgrade/dual boot is not an option.

DrivePool (I tested even the latest beta) will fight with the dedup filter and while DP itself still works, the deduplication does not.

Before you ask,  yes the option to skip the FS filter is correctly set, as usual, in my case


This is what I get from powershell with a simple

Get-dedupstatus  (after DP installation and a reboot)

Quote

Get-DedupStatus : Si è verificato un errore generico che non è compreso in alcun codice di errore più specifico.
In riga:1 car:1
+ Get-DedupStatus
+ ~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (MSFT_DedupVolumeStatus:ROOT/Microsoft/...dupVolumeStatus) [Get-DedupStatu
   s], CimException
    + FullyQualifiedErrorId : HRESULT 0x80010108,Get-DedupStatus

This Is what I see in the deduplication section of event log

Quote

 

Errore di Deduplicazione dati: errore imprevisto.

Operazione:
   Avvio del servizio Deduplicazione file server in corso.

Dettagli errore:
   Errore: DeviceIoControl (FSCTL_GET_NTFS_VOLUME_DATA), 0x80070001, Funzione non corretta.

 

Sorry messages are in Italian but I think are still pretty clear.


So please fix DP asap to not ruin the good reputation of your product (and also to make my life easier )


P.S. FYI Drive Bender 2800 has the exact same behavior