I thought of making a Dedup Pack for Windows 10 RTM using the latest Server TP2 Build 10147 But unfortunately am not able download the mega link I do have in my mega account as the download completes instantly with a fake size. Only if I could get a torrent link I could extract the Dedup manifest files and make a cabinet file or atleast if I could get the NanoServer package folder which is present in the root of the ISO, then I could test and make the pack. But since there will be a new build of sever released soon this month, so lets wait for a while for newer version which will be more compatible with the Windows 10 RTM
We are screwed up... TP3 is build 10154.. Tried integrating dedup module to Windows 10 and doesn't work They are bulls**ting us on this. C:\Dedup>dism /online /add-package /packagepath:"C:\Dedup\/Files/Microsoft-Windows-FileServer-Package~31bf3856ad364e35~amd64~~10.0.10514.0.mum" /packagepath:"C:\Dedup\/Files/Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~10.0.10514.0.mum" Deployment Image Servicing and Management tool Version: 10.0.10240.16384 Image Version: 10.0.10240.16384 Processing 1 of 2 - Adding package Microsoft-Windows-FileServer-Package~31bf3856ad364e35~amd64~~10.0.10514.0 [==========================100.0%==========================] Processing 2 of 2 - Adding package Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~10.0.10514.0 [==========================100.0%==========================] Error: 0x800f081e The specified package is not applicable to this image. The specified package is not applicable to this image. The command completed with errors. For more information, refer to the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Please help!!! Long ago i did dedupe on windows 8.1 secondary 2TB drive and totally forgot about it. Now I bought new drive and installed win10 and cant acsses any of the docs, pics, videos... I am totally locked out of my files. Can anyone guide me through the process of bringing back the files or I am doomed?!
Bringing back can only be done from Windows 8.1 with dedup package added to a new drive... sorry for you
?? What do you mean ? Do you mean renaming all files to 10.0.10240.1634 and updating the info in the 3 .mum files ?
No, don't rename the files, just edit the mum. If you rename the files, the cat won't match and stuff.
Something like this so : From this : <?xml version='1.0' encoding='utf-8' standalone='yes'?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved." manifestVersion="1.0"> <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-Dedup-Package" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.10514.0"/> <package identifier="Microsoft-Windows-Dedup-Package" releaseType="Feature Pack"> <parent integrate="delegate"> <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-FileServer-Package" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.10514.0"/> </parent> <parent integrate="delegate"> <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-Foundation-Package" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.10514.0"/> </parent> <parent integrate="delegate"> <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-ServerCore-Package" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.10514.0"/> </parent> <update description="Reduces the amount of physical storage required for data by applying chunk-level deduplication and compression" displayName="Data Deduplication" name="Dedup-Core"> <mum2:customInformation xmlns:mum2="urn:schemas-microsoft-com:asm.v3"> <ServerComponent Description="Data Deduplication saves disk space by storing a single copy of identical data on the volume." DisplayName="Data Deduplication" Id="436" Parent="File-Services" Type="RoleService" UniqueName="FS-Data-Deduplication"> ... To this : <?xml version='1.0' encoding='utf-8' standalone='yes'?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved." manifestVersion="1.0"> <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-Dedup-Package" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.10240.1634"/> <package identifier="Microsoft-Windows-Dedup-Package" releaseType="Feature Pack"> <parent integrate="delegate"> <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-FileServer-Package" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.10240.1634"/> </parent> <parent integrate="delegate"> <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-Foundation-Package" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.10240.1634"/> </parent> <parent integrate="delegate"> <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-ServerCore-Package" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.10240.1634"/> </parent> <update description="Reduces the amount of physical storage required for data by applying chunk-level deduplication and compression" displayName="Data Deduplication" name="Dedup-Core"> <mum2:customInformation xmlns:mum2="urn:schemas-microsoft-com:asm.v3"> <ServerComponent Description="Data Deduplication saves disk space by storing a single copy of identical data on the volume." DisplayName="Data Deduplication" Id="436" Parent="File-Services" Type="RoleService" UniqueName="FS-Data-Deduplication"> ...
Yah, exactly. If they haven't changed the file system too much, and it installs, it might work. You can install it by putting it in it's own folder and pointing dism at the mum, IIRC. no need to re-cab it.
Would have been very good but : C:\Dedup10240>Install.cmd C:\Dedup10240>dism /online /add-package /packagepath:"C:\Dedup10240\/Files/Microsoft-Windows-FileServer-Package~31bf3856ad364e35~amd64~~10.0.10514.0.mum" /packagepath:"C:\Dedup10240\/Files/Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~10.0.10514.0.mum" Deployment Image Servicing and Management tool Version: 10.0.10240.16384 Image Version: 10.0.10240.16384 An error occurred trying to open - C:\Dedup10240\/Files/Microsoft-Windows-FileServer-Package~31bf3856ad364e35~amd64~~10.0.10514.0.mum Error: 0x800b0100 An error occurred trying to open - C:\Dedup10240\/Files/Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~10.0.10514.0.mum Error: 0x800b0100 Error: 0x800b0100 DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
It's likely hardcoded to check file versions then. Oh well. We'll have to wait for a version that matches win10 at some point in the future.
Or push MS to provide us with a full Dedup Package for Windows 10... I've twitted GabeAul for this so let's all do the same and, maybe, it'll be considered. I won't be waiting another year to be able to save 100s of Gb on my SSDs... I'll install W2K16 TP3 in a dual boot but I was really happy with dedup under W8.1, avoiding me to go from one OS to another to be able to access my VMs.
this kind of stuff should have been punted regularly to MS during the insider stuff with the TP's. It might have had a better chance. Sadly most requests and grumbles went to UI changes and pretty icons *le sigh* Thanks for the effort guys. Back to waiting
I did it some time ago to see if the .sys was enough to make w7/server2008r2 able to access the deduplicated files. Didn't work because some kernel dependency, but very likely it will work on w10 using the files from an older w10 version. Make all the deduplication actively working would be harder, but just the driver to access the already duplicated files shouldn't be that hard.