Working Deduplication files for Microsoft Windows 10

It's working fine for me on 19042.450.

 

Hello all - long-time lurker who has gratefully benefitted from the tips on this thread - have also problems since 2004. Most annoyingly, on a volume where Dedup appears to be fully working without any 'filter driver' errors, Hyper-V VMs are 'lost' after deduplication and then the following reboot.

Has anyone been able to combine 2004, Hyper-V and Deduplication sucessfuly, or is it a lost cause for now?

These DD packages have been so damn useful I've become accustomed to their reliability - the first discovery of this issue wiped-out my un-backed up VM library.

 

My volume is also for Hyper-V, on Windows 2020, using deduplication (and, actually, Bitlocker as well). As I posted, I managed to get it to work for 1-2 days after completely reformatting my drive and copying the data. But after that, it broke again.

@bfoos,as you're the one that seems to be running dedup without problems; could this be a cause? Do you have the Hyper-V role enabled on your desktop? Do people who are experiencing problems all have Hyper-V enabled? I don't mean specifically whether or not you're hosting Hyper-V related files on the dedupped volume, just whether or not it's enabled at all.

 

Yes, I do have have Hyper-V enabled.

 

Hi, just installed build 19041.508, it works! Thank you @bfoos, i just found this on google.

 

You need to login to view this posts content.

 

Can you post that build here ?

 

Can't install Microsoft-Windows-FileServer-ServerCore-Package-amd64-10.0.19041.1.cab on my 19042,546. Maybe someone has a newer CAB?

 

There are no newer CAB files outside of vNext IP builds (which won't work on 19041/19042) and it installs fine on 19041/2.546.

 

Yes it works until you reboot. after you reboot it will stop working and will change DataAccessEnabled : False

 

Nope, not on my end. It works fine.

 

I tested on freshly installed windows 10 (2004) machine, and patch it with latest update. And it doing same after restart will change DataAccessEnabled : False. If I enable Dedup on D: drive it will work until I restart that machine. Computer have one disk divided in two partitions C drive and D drive. If I install on same machine windows 10 (1909) and do the same with according dedup packeg, everything is working perfect.

 

Hello everybody,

When I run "Update-DedupStatus -Volume "D:""

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

Anybody can help me?
I'm on Windows 10 19041.508.

 

Hello guys,

I've resolved my issue about 0x80565342.

I need to activate the feature Data deduplication on windows 10 and after a restart computer all my data are ready and enable.

Greate. After that I stop deduplication on Windows 10.

 

HI,
My windows 10 has updated to 19041.508 and dedup doesn´t work again, I cannot change the DataAccessEnabled : False. Any ideas? Thanks.

Regards.

 

DataAccessEnabled flips to True if you use psexec to run cmd as SYSTEM, remove HSM.00.cfg and HSM.01.cfg from X:\System Volume Information\Dedup\Settings, and then run Enable-DedupVolume X: -DataAccess in PowerShell.

However, these files are recreated as soon as you run the command in PowerShell, causing the filter driver not to attach to the drive the next time you go to mount it. I also noticed that running Disable-DedupVolume -DataAccess on one of my deduplicated volumes that was previously not affected by the issue did... something... to it that caused the files to be created again. Since this configuration data does not exist at all on my working volumes, I tried deleting the data again after the volume was mounted with the filter driver successfully attached. This allowed the volume to automatically mount again without DataAccessEnabled flipping to false or any strange errors being logged in event viewer.

Additionally, when the unknown configuration data is present, Enable-DedupVolume -DataAccess will throw the following in event viewer: FSCTL_DEDUP_FILE.DEDUP_SET_CHUNK_STORE_CACHING_FOR_NON_CACHED_IO failed with ERROR_INVALID_FUNCTION. When attempting to mount an affected volume at boot, I saw "Unexpected signature 0x44524352 (Expected 0x72687443), MajorVersion 40, 0x8056531d, The data is invalid."

It's a strange issue. It looks like there's a 19041.546 dedup package now... maybe we need that?

 

Just my 2c.
Build 10.0.19042.572 (aka Windows 20h2) working as it should after re-enabling feature dedup with:

Code:

dism /online /add-package /packagepath:Microsoft-Windows-FileServer-ServerCore-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cab /packagepath:Microsoft-Windows-FileServer-ServerCore-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1.cab
dism /online /add-package /packagepath:Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cab /packagepath:Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1.cab
dism /online /enable-feature /featurename:Dedup-Core /all

(files grabbed from the MEGA-archive in this thread)

Thanks again to all involved making this possible.

 

Good morining Iorx,

What is the link of the MEGA-Archive?

Thanks.

 

I have executed these commands with this package and I have this error: FSCTL_DEDUP_FILE.DEDUP_SET_CHUNK_STORE_CACHING_FOR_NON_CACHED_IO ,Where did you get the packages? .
Thanks.

 

You need to login to view this posts content.