I have no problems with RSAT, you need to manually replace corrupt CAT file in WinSxS dir. In that file there is the correct hash. So what is your volume type? ReFS?
It is just ported package from W2012SR2b9600. Apparently RSAT itself has a different VdsInterop package within it. But it is piece of cake, just remove the packages which are unsupported by RSAT 1st before installing RSAT. Code: dism /online /disable-feature /featurename:Dedup-Core /all dism /online /remove-package /packagepath:Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~~6.2.9200.16384.cab /packagepath:Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~en-US~6.2.9200.16384.cab I will make changes to the package, but different ones from those you need, because I don't need RSAT support. My changes will include these files, which are for some reason unknown not included in current packages: Manifests: amd64_microsoft-windows-d..oyment-languagepack_31bf3856ad364e35_6.X.9X00.16384_en-us_xxxxxxxxxxxxxxxx.manifest amd64_microsoft-windows-d..oyment-languagepack_31bf3856ad364e35_6.X.9X00.16384_cs-cz_xxxxxxxxxxxxxxxx.manifest Update.CAT / MUM: Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~~6.X.9X00.16384.cat Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~~6.X.9X00.16384.mum Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~en-US~6.X.9X00.16384.cat Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~en-US~6.X.9X00.16384.mum Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~cs-CZ~6.X.9X00.16384.cat Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~cs-CZ~6.X.9X00.16384.mum There are two ways to do that: 1. Create additional CABs: Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~~6.X.9X00.16384.cab Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~en-US~6.X.9X00.16384.cab Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~cs-CZ~6.X.9X00.16384.cab for both missing CAT/MUM a MANIFESTs and possibly also the files from dir: amd64_microsoft-windows-dedup-chunklibrary_31bf3856ad364e35_6.X.9X00.16384_none_xxxxxxxxxxxxxxxx 2. Include MANIFESTs only to: Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~en-US~6.X.9X00.16384.cab Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~cs-CZ~6.X.9X00.16384.cab
No, it isn't. Because those packages are not removed with dism. (take a look into winsxs, it remains there) It is not so easy to remove it, believe me . 1st you need to replace failed components with correct one (dll and manifest in winsxs) (booting another image, or taking ownership) 2nd you have to replace component registry with hash, because this gets validated against catalog (record S256H in COMPONENTS\DerivedData\Components\msil_microsoft.storage.vds.resources_31bf3856ad364e35_6.3.9600.16384_en-us_8c04cf7b7ebc4943). Components registry hive has to be manually loaded from C:\Windows\System32\config kaspik PS what tool do you use for creating cabs? I would like to modify Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab with RSAT dll and manifest from Win8.1. (the ones I attached few posts above) Btw. cesi jsou vsude koukam
Hello, this VDS interop even in optimized package is wrong. RSAT cannot be installed and this hash is not in catalog as stated here 2013-11-02 15:23:04, Info CSI 0000007c Couldn't find the hash of component: Microsoft.Storage.Vds.Resources, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the catalog [l:192{96}]"\SystemRoot\WinSxS\Catalogs\67608e00273ebc6acc240bc56e248736f5d952bc90ef837f5fe75742b1872f5a.cat". This component is not even uninstalled if tried to uninstall with dism. Can you please build one RSAT version of this package? I did this, but this forum does not accept larger attachements. Thanks! Some more info attached-you can see, that hash is really not there.
Just wondering, has there been any progress on this? I'm encountering similar issues. Not trolling, just looking for an update. Wish I had the skillz to help...
@kaspik: OK, OK, pls send me RSAT VDSinterop files and I will make compatible package for both w8-x... There are 5 files in VDS Main, 5 files in VDS EN Resources and 5 files in VDS CZ Resources, so 15 files in total...
This is great news. I'm planning on re-installing the server, so I'll hold-off on re-adding dedup until the new package is up. Free testing. If someone could illuminate what/where/how to help, I'd be happy to contribute.
I hate to ask, but I'm not understanding the install text. Could you tell me how to install this Moderate. Do I just run that as one long command in an elevated command prompt? Also technet says that it does not support system, boot, or os volumes. Is there a way to get it to work on the system, os, boot volume. I'm on win 8.1 and would love to get this running on my ssd thank you for your help.
@anthonykash: I don't think there's any way to get dedup working on os/system/boot volumes. You're best off splitting your partitions and putting the incompatible (OS) parts in a one volume and your data in another. Hey, does anyone know how to uninstall the dedup package as supplied by @moderate? It's checked but greyed out in the Add Roles and Features Wizard and I'm having kaspik's server manager issues.
Hello, it is little bit tricky. First step you need to do is to replace 3 files in your windows directory (attached). You need to boot another media (or for example windows 8 installation media, ten hit s**t+f10 to have command line and copy it manually from command line). This is because files are owned by trusted installer, and booting another media is just easier than taking ownership. Screenshot attached. Second step You need to repair registry with correct hash value. Run regedit, if component store is not visible in registry click on HKEY_LOCAL_MACHINE folder, then File->Load Hive and browse for COMPONENTS file in C:\Windows\System32\config. Import registry (attached). Third step U can install RSAT Now.
Thanks, Kaspik. I'll follow your instructions tonight (this is for my home server) and let you know how it goes.
Did you ever publish this script? I need to do exactly what you did for deduplication except that I need to install Windows Server Backup on Windows 10. I can't figure out how to get the cab files. I "think" the files I need all have blb in the name but that's kinda an educated guess.