Are you in the UK? Because as posted, it's a geo-block that specifically hits the UK that causes an issue with Zippyshare. The Sendit link now appears to work here, however did not at the time of posting (hence why I had to resort to a VPN to get to Zippyshare instead - wouldn't have gone to the extra effort if it had worked at the time) Regardless, thanks for the files - they're appreciated
Yeah I used my VPN to connect to a London, UK server and yes Zippshare was 403 forbidden but the sendit.cloud link worked fine. And no problem for the files!
If anyone is curious, the 18362.1 dedup set that I posted here work fine on the initial 19H2 (18362.10000) insider build.
Yes, highly likely. Which is why I said "initial 19H2 (18362.10000) insider build." It could possibly be broken by a future 19H2 update. Aside from that, I shared this as I fully expected someone would come along and ask "Hey, does this work on the new 19H2 builds?" I figured I'd help out the 3 people on Earth that actually search and read threads to glean needed info before posting questions.
do you have the dedup files for build (windows 10 1903 released in may 2019) 18362.30 . the one that you posted above for build 18362.10000 doesnt work for .30 build . How do you get these dedup files ? so whenever there is new OS build, we can extract them if there is way you do it. Thanks, Eswar
I've personally tested the 18362.1 dedup pack I compiled on clean installations of every single 18362 CU to date (including 18362.30) as well as a clean installation of 18362.10000 and can confirm that it installs without error and functions as expected. So instead of just saying it doesn't work, please describe the issue/s that you are having. Error codes and or DISM/CBS logs are also useful for debugging issues. With that said, these dedup files work fine on 18362.30.
Thanks ,i reboot the device and rerun the dism ,this time it works. before the reboot, following is the error code from dism log: DISM DISM Package Manager: PID=12680 TID=2720 Failed to verify package location C:\Users\eswar\Downloads\Microsoft-Windows-VdsInterop-Package-amd64-10.0.18362.1.cab - CDISMPackageManager::Internal_CreatePackageByPath(hr:0x80070002)
I have a reproducible bluescreen under 18362.239 with dedup-10.0.18362.1.7z package installed, when letting PLEX scan my deduplicated media library. Probably it's the last windows update that changed something. Dedup overwall still works as intended, it seems to be something specific that PLEX does. Is there an updated dedup package that might fix this issue or is it not worth bothering?
No there is no updated pack. Any dedup files needing updating would be updated by Windows Update in a cumulative update as far as I know as server and client CU's are identical. I don't use PLEX but I do use Kodi and it has no trouble accessing files on my dedup'd volumes. What network protocol are you using on the host?
I installed the files of dedup-10.0.18362.1.7z on my system.Currently it is Windows 10 Professional (18362.239). At any deduplication command i get follow error: Code: PS C:\WINDOWS\system32> Disable-DedupVolume -Volume D: Disable-DedupVolume : Fehler beim Laden des Anbieters In Zeile:1 Zeichen:1 + Disable-DedupVolume -Volume D: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (MSFT_DedupVolume:ROOT/Microsoft/...SFT_DedupVolume) [Disable-DedupVolume] , CimException + FullyQualifiedErrorId : HRESULT 0x80041013,Disable-DedupVolume Manual uninstall an reinstall the package via DISM brought nothing. I also reboot the system after the various steps (unstall, reinstall and Enable the feature) - same issue.
Please describe the exact steps you are using to install and enable data deduplication. You seem to be using the -Volume parameter in the above error which is wrong. When using the Enable-DedupVolume and Disable-DedupVolume commands all that is needed is the drive letter followed by a colon and encapsulated in quotation marks (IE: Enable-DedupVolume "D:"). All other dedup commands are used with the -Volume parameter (IE: Set-DedupVolume -Volume "D:" -MinimumFileAgeDays 0 -MinimumFileSize 32768).
I installed the dedup packages in the same order as in the text file described. After that in restart my computer. Than i open a powershell as administrator and type follow command: import-module deduplication. This command executed without any error. Now i try to activated the deduplication for volume d: The filesystem is NTFS. Both commands display the same error as i posted vor few days. Code: Enable-DedupVolume -Volume D: Enable-DedupVolume "D:"
Sorry but I don't know what to tell you. It's working as expected for me on a fresh installation of Pro 18362.239.