Cannot access files in the volume that was deduplicated prior to the upgrade from 1909 Getting this error when starting a job: Data Deduplication failed to start job type "Optimization" on volume "\\?\Volume{130ee3b0-bc9e-4bca-bea3-cf923820b4c7}\" with error "0x80565309, A required filter driver is either not installed, not loaded, or not ready for service. ". Upgraded from 1909 to 2004 (19041.264), installed the packages successfully. Any suggestion? Thanks in advance.
I tested enabling data deduplication on 1909 then upgrading to 2004 and installing the dedup pack that I created and experienced no errors. Did you run the powershell commands int he readme file to enable deduplication on whatever volumes?
Thanks for the help. I installed two VM's, one with 1909 and another with 2004. Installed the corresponding dedup packages on each VM, created a new vhd on each VM, enabled deduplication on both and I've been able to make read each vhd in both VM's after enabling deduplication and running all the jobs. However, for some reason, the partition on the physical disk was only readable from the 1909 VM. Gave up and ended up running unoptimize from the VM, as I still had enough free space on that partition. Anyway, It seems that in some cases the upgraded OS version might not be able to read a deduplicated volume from a previous version.
So I upgraded 5 systems from 1909 to 2004 and tried to re-enable Dedup on them. On my only desktop system, a NUC Hades Canyon. Dedup appears to be working correctly. On my other laptop systems, it says dedup is enabled and running Get-DedupVolume says it's enabled, however I can't access files. Might have to boot from USB with 1909 and then unoptimize the drives and re-optimize the drives if there isn't a solution. Had no problems going from earlier versions of Dedup in the 17xx build to 18xx builds to 19xx builds until now.
I haven't had any issues at all going from 17xx to 18xx nor from 18xx to 1903/9 nor from 1903/9 to 19041.
It's been inconsistent for my notebooks... I could un-optimize the drives and re-enable dedup in 2004 on my X1 Extreme and Yoga 720, but doing the same methods do not work on my XPS13-9360 nor on my Alienware 13R3. After I re-enabled dedup and rebooted, the files could not be read nor are the shortcuts to certain programs are not showing their icon. I think it's buggy, but we'll see if anybody else has the same experience. My steps are reboot into 1909 using USB and running: Start-DedupJob -Volume D: -Type Unoptimization -Wait Get-DedupJob #to check the status at the end Get-DedupVolume #to re-check and make sure there is no dedup volumes present Restart-computer -force Remove the USB before it restarts In the 2004 OS after applying the 2004 dedup files: Enable-Dedupvolume -volume d: -UsageType HyperV #since I'm using VM's Start-Dedupjob -Volume D: -Type Optimization - Wait Use Get-DedupVolume #to see the savings Open some iso and VM's and was able to test. Rebooted the computer. Can't access files. I can't explain why it's inconsistent like what deathmouse is seeing. But for now I'm just going to leave dedup off for the systems where it doesn't work.
The 2004 dedup files are not working on my (en_GB) system; as with the posters above, I can no longer access files even though the installation went through successfully.
I did say it was for en-US only for now as I don't have access, time nor patience to individually extract language packs. I have no idea why it works for some people and not for others. It's working as expected over here from both 1903/9 upgrades to 19041 and clean installations of 19041.
Unfortunately even with the en_GB CAB files installed I am unable to access any deduplicated files, getting the error "The file cannot be accessed by the system".
@bfoos once package is applied, dedup enabled and it works. Unfortunately after reboot, filter driver is detached and refuses to attach... So dedup is bit unusable
Nothing I can do about that. This is a Windows Server feature and was never intended to be installed or used on client editions. Anyway, it works fine for me and other users. Nobody reporting that it isn't working is even giving up any valuable information to even begin to debug anyway. I just rebooted and manually ran a dedup job, so... ¯\_(ツ)_/¯
The only thing that I can report is that some values are not showing up. However, deduplication is working fine: Code: Volume : Y: VolumeId : \\?\Volume{34cb727f-a6f2-4546-b7c3-8de382c073a4}\ Capacity : FreeSpace : UsedSpace : UnoptimizedSize : SavedSpace : SavingsRate : OptimizedFilesCount : 3321 OptimizedFilesSize : OptimizedFilesSavingsRate : InPolicyFilesCount : 3320 InPolicyFilesSize : LastOptimizationTime : 18.05.2020 12:40:34 LastOptimizationResult : LastOptimizationResultMessage : Der Vorgang wurde erfolgreich beendet. LastGarbageCollectionTime : 30.04.2020 22:36:18 LastGarbageCollectionResult : LastGarbageCollectionResultMessage : Der Vorgang wurde erfolgreich beendet. LastScrubbingTime : 28.04.2020 14:24:50 LastScrubbingResult : LastScrubbingResultMessage : Der Vorgang wurde erfolgreich beendet.