Jump to content
Covecube Inc.

Search the Community

Showing results for tags 'build 17763'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Covecube Inc.
    • Announcements
    • Nuts & Bolts
  • BitFlock
    • General
  • StableBit Scanner
    • General
    • Compatibility
    • Nuts & Bolts
  • StableBit DrivePool
    • General
    • Hardware
    • Nuts & Bolts
  • StableBit CloudDrive
    • General
    • Providers
    • Nuts & Bolts
  • Other
    • Off-topic

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. 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) This Is what I see in the deduplication section of event log 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
×
×
  • Create New...