Working Deduplication files for Microsoft Windows 10

Discussion in 'Windows 10' started by dreamss, Oct 4, 2014.

  1. ku16610

    ku16610 MDL Novice

    Oct 1, 2020
    6
    0
    0
    Hi does anyone have the files for Windows 10 19041.1288 knocking around , i accidentally updated and lost access to my deduce volumes data.

    thanks
     
  2. ku16610

    ku16610 MDL Novice

    Oct 1, 2020
    6
    0
    0
    nope that file doesnt seem to work , though i just noticed my windows is actually 10.0.19041.1320

    Microsoft Windows [Version 10.0.19041.1320]
    (c) Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>cd C:\Users\user\Downloads\dedupe-me\19041.1202

    C:\Users\user\Downloads\dedupe-me\19041.1202>dism /online /add-package /packagepath:"Microsoft-Windows-FileServer-ServerCore-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cab" /packagepath:"Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~10.0.19041.1202.cab"

    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844

    Image Version: 10.0.19041.1320

    Processing 1 of 2 - Adding package Microsoft-Windows-FileServer-ServerCore-Package~31bf3856ad364e35~amd64~~10.0.19041.1
    [==========================100.0%==========================]
    An error occurred - Microsoft-Windows-FileServer-ServerCore-Package Error: 0x80073701
    Processing 2 of 2 - Adding package Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~10.0.19041.1202
    [==========================100.0%==========================]

    Error: 14081

    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

    C:\Users\user\Downloads\dedupe-me\19041.1202>
     
  3. xinso

    xinso MDL Guru

    Mar 5, 2009
    7,630
    10,042
    240
  4. ku16610

    ku16610 MDL Novice

    Oct 1, 2020
    6
    0
    0
    #765 ku16610, Oct 30, 2021
    Last edited: Oct 30, 2021
    Okay some progress the Dedupe packages install without error

    Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~10.0.19041.1202.cab installs perfectly.
    Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1.cab installs perfectly also.

    but these 2 seem to always fail.

    Microsoft-Windows-FileServer-ServerCore-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cab , gives me error 14081 when i try to install. (Error 0x80073701) the referenced assembly could not be found )
    Microsoft-Windows-FileServer-ServerCore-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1.cab gives me error 0x800f081e
     
  5. xinso

    xinso MDL Guru

    Mar 5, 2009
    7,630
    10,042
    240
    #766 xinso, Oct 30, 2021
    Last edited: Oct 30, 2021
    Microsoft-Windows-FileServer-ServerCore-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cab
    sha1: D1862F476A9B8B0003D3C3D9EDFEABEB4DE479AF

    Microsoft-Windows-FileServer-ServerCore-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1.cab
    sha1: 8D254C7DEFA3E83F3F67D8715159709A7CB24024

    Q: Without FileServer-ServerCore-Package preinstalled, how can you install Dedup? Sure?

    No.
     
  6. ku16610

    ku16610 MDL Novice

    Oct 1, 2020
    6
    0
    0
    It seems to have dedupe but not the core FS
    {
    C:\WINDOWS\system32>Dism /online /get-features | more

    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844

    Image Version: 10.0.19041.1320

    Features listing for package : Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.19041.1

    Feature Name : Printing-PrintToPDFServices-Features
    State : Enabled

    Feature Name : Printing-XPSServices-Features
    State : Enabled

    Feature Name : TelnetClient
    State : Disabled

    Feature Name : TFTP
    State : Disabled

    Feature Name : LegacyComponents
    State : Enabled

    Feature Name : DirectPlay
    State : Enabled

    Feature Name : SimpleTCP
    State : Disabled

    Feature Name : Windows-Identity-Foundation
    State : Disabled

    Feature Name : NetFx3
    State : Enabled

    Feature Name : WCF-HTTP-Activation
    State : Enabled

    Feature Name : WCF-NonHTTP-Activation
    State : Enabled

    Feature Name : IIS-WebServerRole
    State : Enabled

    Feature Name : IIS-WebServer
    State : Enabled

    Feature Name : IIS-CommonHttpFeatures
    State : Disabled

    Feature Name : IIS-HttpErrors
    State : Disabled

    Feature Name : IIS-HttpRedirect
    State : Disabled

    Feature Name : IIS-ApplicationDevelopment
    State : Enabled

    Feature Name : IIS-Security
    State : Enabled

    Feature Name : IIS-RequestFiltering
    State : Enabled

    Feature Name : IIS-NetFxExtensibility
    State : Enabled

    Feature Name : IIS-NetFxExtensibility45
    State : Disabled

    Feature Name : IIS-HealthAndDiagnostics
    State : Disabled

    Feature Name : IIS-HttpLogging
    State : Disabled

    Feature Name : IIS-LoggingLibraries
    State : Disabled

    Feature Name : IIS-RequestMonitor
    State : Disabled

    Feature Name : IIS-HttpTracing
    State : Disabled

    Feature Name : IIS-URLAuthorization
    State : Disabled

    Feature Name : IIS-IPSecurity
    State : Disabled

    Feature Name : IIS-Performance
    State : Disabled

    Feature Name : IIS-HttpCompressionDynamic
    State : Disabled

    Feature Name : IIS-WebServerManagementTools
    State : Disabled

    Feature Name : IIS-ManagementScriptingTools
    State : Disabled

    Feature Name : IIS-IIS6ManagementCompatibility
    State : Disabled

    Feature Name : IIS-Metabase
    State : Disabled

    Feature Name : WAS-WindowsActivationService
    State : Enabled

    Feature Name : WAS-ProcessModel
    State : Enabled

    Feature Name : WAS-NetFxEnvironment
    State : Enabled

    Feature Name : WAS-ConfigurationAPI
    State : Enabled

    Feature Name : IIS-HostableWebCore
    State : Disabled

    Feature Name : WCF-Services45
    State : Enabled

    Feature Name : WCF-HTTP-Activation45
    State : Disabled

    Feature Name : WCF-TCP-Activation45
    State : Disabled

    Feature Name : WCF-Pipe-Activation45
    State : Disabled

    Feature Name : WCF-MSMQ-Activation45
    State : Disabled

    Feature Name : WCF-TCP-PortSharing45
    State : Enabled

    Feature Name : IIS-StaticContent
    State : Disabled

    Feature Name : IIS-DefaultDocument
    State : Disabled

    Feature Name : IIS-DirectoryBrowsing
    State : Disabled

    Feature Name : IIS-WebDAV
    State : Disabled

    Feature Name : IIS-WebSockets
    State : Disabled

    Feature Name : IIS-ApplicationInit
    State : Disabled

    Feature Name : IIS-ASPNET
    State : Disabled

    Feature Name : IIS-ASPNET45
    State : Disabled

    Feature Name : IIS-ASP
    State : Disabled

    Feature Name : IIS-CGI
    State : Disabled

    Feature Name : IIS-ISAPIExtensions
    State : Disabled

    Feature Name : IIS-ISAPIFilter
    State : Disabled

    Feature Name : IIS-ServerSideIncludes
    State : Disabled

    Feature Name : IIS-CustomLogging
    State : Disabled

    Feature Name : IIS-BasicAuthentication
    State : Disabled

    Feature Name : IIS-HttpCompressionStatic
    State : Disabled

    Feature Name : IIS-ManagementConsole
    State : Disabled

    Feature Name : IIS-ManagementService
    State : Disabled

    Feature Name : IIS-WMICompatibility
    State : Disabled

    Feature Name : IIS-LegacyScripts
    State : Disabled

    Feature Name : IIS-LegacySnapIn
    State : Disabled

    Feature Name : IIS-FTPServer
    State : Disabled

    Feature Name : IIS-FTPSvc
    State : Disabled

    Feature Name : IIS-FTPExtensibility
    State : Disabled

    Feature Name : MSMQ-Container
    State : Disabled

    Feature Name : MSMQ-DCOMProxy
    State : Disabled

    Feature Name : MSMQ-Server
    State : Disabled

    Feature Name : MSMQ-ADIntegration
    State : Disabled

    Feature Name : MSMQ-HTTP
    State : Disabled

    Feature Name : MSMQ-Multicast
    State : Disabled

    Feature Name : MSMQ-Triggers
    State : Disabled

    Feature Name : IIS-CertProvider
    State : Disabled

    Feature Name : IIS-WindowsAuthentication
    State : Disabled

    Feature Name : IIS-DigestAuthentication
    State : Disabled

    Feature Name : IIS-ClientCertificateMappingAuthentication
    State : Disabled

    Feature Name : IIS-IISCertificateMappingAuthentication
    State : Disabled

    Feature Name : IIS-ODBCLogging
    State : Disabled

    Feature Name : MediaPlayback
    State : Enabled

    Feature Name : WindowsMediaPlayer
    State : Enabled

    Feature Name : DataCenterBridging
    State : Disabled

    Feature Name : SmbDirect
    State : Enabled

    Feature Name : HostGuardian
    State : Disabled

    Feature Name : AppServerClient
    State : Disabled

    Feature Name : Windows-Defender-Default-Definitions
    State : Disabled

    Feature Name : SearchEngine-Client-Package
    State : Enabled

    Feature Name : MSRDC-Infrastructure
    State : Enabled

    Feature Name : TIFFIFilter
    State : Disabled

    Feature Name : WorkFolders-Client
    State : Enabled

    Feature Name : Printing-Foundation-Features
    State : Enabled

    Feature Name : Printing-Foundation-InternetPrinting-Client
    State : Enabled

    Feature Name : Printing-Foundation-LPDPrintService
    State : Disabled

    Feature Name : Printing-Foundation-LPRPortMonitor
    State : Disabled

    Feature Name : MicrosoftWindowsPowerShellV2Root
    State : Enabled

    Feature Name : MicrosoftWindowsPowerShellV2
    State : Enabled

    Feature Name : Client-ProjFS
    State : Disabled

    Feature Name : NetFx4-AdvSrvs
    State : Enabled

    Feature Name : NetFx4Extended-ASPNET45
    State : Enabled

    Feature Name : SMB1Protocol
    State : Enabled

    Feature Name : SMB1Protocol-Client
    State : Enabled

    Feature Name : SMB1Protocol-Server
    State : Enabled

    Feature Name : SMB1Protocol-Deprecation
    State : Enabled

    Feature Name : Client-EmbeddedBootExp
    State : Disabled

    Feature Name : Client-EmbeddedLogon
    State : Disabled

    Feature Name : Client-KeyboardFilter
    State : Disabled

    Feature Name : Client-UnifiedWriteFilter
    State : Disabled

    Feature Name : MultiPoint-Connector
    State : Disabled

    Feature Name : MultiPoint-Connector-Services
    State : Disabled

    Feature Name : MultiPoint-Tools
    State : Disabled

    Feature Name : Internet-Explorer-Optional-amd64
    State : Enabled

    Feature Name : Microsoft-Windows-Subsystem-Linux
    State : Enabled

    Feature Name : HypervisorPlatform
    State : Disabled

    Feature Name : VirtualMachinePlatform
    State : Enabled

    Feature Name : Containers-DisposableClientVM
    State : Disabled

    Feature Name : Microsoft-Hyper-V-All
    State : Disabled

    Feature Name : Microsoft-Hyper-V
    State : Disabled

    Feature Name : Microsoft-Hyper-V-Tools-All
    State : Disabled

    Feature Name : Microsoft-Hyper-V-Management-PowerShell
    State : Disabled

    Feature Name : Microsoft-Hyper-V-Hypervisor
    State : Disabled

    Feature Name : Microsoft-Hyper-V-Services
    State : Disabled

    Feature Name : Microsoft-Hyper-V-Management-Clients
    State : Disabled

    Feature Name : Client-DeviceLockdown
    State : Disabled

    Feature Name : Client-EmbeddedShellLauncher
    State : Disabled

    Feature Name : DirectoryServices-ADAM-Client
    State : Disabled

    Feature Name : Windows-Defender-ApplicationGuard
    State : Disabled

    Feature Name : ServicesForNFS-ClientOnly
    State : Disabled

    Feature Name : ClientForNFS-Infrastructure
    State : Disabled

    Feature Name : NFS-Administration
    State : Disabled

    Feature Name : Containers
    State : Disabled

    Feature Name : Dedup-Core
    State : Disabled

    The operation completed successfully.
     
  7. xinso

    xinso MDL Guru

    Mar 5, 2009
    7,630
    10,042
    240
    #770 xinso, Oct 30, 2021
    Last edited: Oct 30, 2021
    19041.1320 Pro amd64
     
  8. ku16610

    ku16610 MDL Novice

    Oct 1, 2020
    6
    0
    0
    #771 ku16610, Oct 30, 2021
    Last edited: Oct 30, 2021
    I did have Dedupe installed before , just for some idiot reason i clicked to allow an update.

    My windows version is 10 Enterprise Version 10.0.19041.1320

    PS : I very much appreciate the help , been tearing my hair out trying to fix this for last 3 days.

    Oh i have been installing all these entirely offline , ie booted into winPE , could that be my problem ?

    Online gives me the same more or less
    dism /online /add-package /packagepath:Microsoft-Windows-FileServer-ServerCore-Package-amd64-10.0.19041.1.cab /packagepath:Microsoft-Windows-FileServer-ServerCore-Package-amd64-en-US-10.0.19041.1.cab

    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844

    Image Version: 10.0.19041.1320

    Processing 1 of 2 - Adding package Microsoft-Windows-FileServer-ServerCore-Package~31bf3856ad364e35~amd64~~10.0.19041.1
    [==========================100.0%==========================]
    An error occurred - Microsoft-Windows-FileServer-ServerCore-Package Error: 0x80073701
    Processing 2 of 2 - Adding package Microsoft-Windows-FileServer-ServerCore-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1
    [==========================100.0%==========================]

    Error: 14081

    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

    Nope still refuses to install , I think ill just have to install windows server remove de dupe and then migrate to windows 10 pro

    gave it one more go removing then readding and yeah removal worked fine ,installing them back did the same thing fails on the FS core but dedupe installs fine. So strange :(

    C:\Users\user\Downloads\dedupe-me\19041.1\install>dism /online /remove-package /packagepath:Microsoft-Windows-Dedup-Package-amd64-10.0.19041.1.cab /packagepath:Microsoft-Windows-Dedup-Package-amd64-en-US-10.0.19041.1.cab

    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844

    Image Version: 10.0.19041.1320

    Processing 1 of 2 - Removing package Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~10.0.19041.1
    [==========================100.0%==========================]
    Processing 2 of 2 - Removing package Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1
    [==========================100.0%==========================]
    The operation completed successfully.

    C:\Users\user\Downloads\dedupe-me\19041.1\install>dism /online /remove-package /packagepath:Microsoft-Windows-FileServer-ServerCore-Package-amd64-10.0.19041.1.cab /packagepath:Microsoft-Windows-FileServer-ServerCore-Package-amd64-en-US-10.0.19041.1.cab

    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844

    Image Version: 10.0.19041.1320

    Processing 1 of 2 - Removing package Microsoft-Windows-FileServer-ServerCore-Package~31bf3856ad364e35~amd64~~10.0.19041.1
    [==========================100.0%==========================]
    Processing 2 of 2 - Removing package Microsoft-Windows-FileServer-ServerCore-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1
    [==========================100.0%==========================]
    The operation completed successfully.

    C:\Users\user\Downloads\dedupe-me\19041.1\install>dism /online /add-package /packagepath:Microsoft-Windows-FileServer-ServerCore-Package-amd64-10.0.19041.1.cab /packagepath:Microsoft-Windows-FileServer-ServerCore-Package-amd64-en-US-10.0.19041.1.cab

    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844

    Image Version: 10.0.19041.1320

    Processing 1 of 2 - Adding package Microsoft-Windows-FileServer-ServerCore-Package~31bf3856ad364e35~amd64~~10.0.19041.1
    [==========================100.0%==========================]
    An error occurred - Microsoft-Windows-FileServer-ServerCore-Package Error: 0x80073701
    Processing 2 of 2 - Adding package Microsoft-Windows-FileServer-ServerCore-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1
    [==========================100.0%==========================]

    Error: 14081

    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

    C:\Users\user\Downloads\dedupe-me\19041.1\install>dism /online /add-package /packagepath:Microsoft-Windows-Dedup-Package-amd64-10.0.19041.1.cab /packagepath:Microsoft-Windows-Dedup-Package-amd64-en-US-10.0.19041.1.cab

    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844

    Image Version: 10.0.19041.1320

    Processing 1 of 2 - Adding package Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~10.0.19041.1
    [==========================100.0%==========================]
    Processing 2 of 2 - Adding package Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1
    [==========================100.0%==========================]
    The operation completed successfully.

    C:\Users\user\Downloads\dedupe-me\19041.1\install>dism /online /enable-feature /featurename:Dedup-Core /all

    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844

    Image Version: 10.0.19041.1320

    Enabling feature(s)
    [==========================100.0%==========================]

    Error: 50

    The operation is complete but Dedup-Core feature was not enabled.


    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
     
  9. xinso

    xinso MDL Guru

    Mar 5, 2009
    7,630
    10,042
    240
    #772 xinso, Oct 30, 2021
    Last edited: Oct 30, 2021
    OK.
     
  10. Evengard

    Evengard MDL Novice

    Nov 9, 2007
    10
    1
    0
    No matter what I tried, I haven't managed to get dedup working on Win11. Even if my cabs with patched mums gets installed successfully, still on enable-feature the feature is not found. I really don't get what am I doing wrong...
     
  11. fish0x0zero

    fish0x0zero MDL Novice

    Dec 16, 2019
    1
    0
    0
    I stay at build 22483 for dedup. Current available cab files(22471) no longer work since the next build...
    Looking forward to a more recent version from vNext.
     
  12. Evengard

    Evengard MDL Novice

    Nov 9, 2007
    10
    1
    0
    Well, I'm on build 22000 (the RTM one), none works.
     
  13. Evengard

    Evengard MDL Novice

    Nov 9, 2007
    10
    1
    0
    I can help extracting the cab files from 22518 version if you want, but I really need help from someone to adapt them for the build 22000. Because all my attempts failed =(
     
  14. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    13,147
    64,376
    340
    Shoot
     
  15. acer-5100

    acer-5100 MDL Addicted

    Dec 8, 2018
    712
    460
    30
    #779 acer-5100, Dec 21, 2021
    Last edited: Dec 21, 2021
    Instead of risking your data with unsupported combinations, just do on w11 what I do on unsupported systems since the day server 2012 was released.

    use hyper-v, install the lightest,sipported, windows you can find (like HyperCore 1809) install it, add dedup packages to it, attach the deduped drives to the VM as physical drives and share them via SMB, oviously set the guest dedup VM, to boot when the host boots.

    No worry of on disk format changes (which happened at least four times w8/w8.1/w10 rtm/ w10 15063), easy portability across multi boot environments and access to deduped files even from vista or future releases like w12.

    Performances are near native, and after ten years, I can say very robust

    P.S you can do the same using vmware/vbox and use an even older system like XP, but the hyperv solution is better because the intrinsic robustness and the dynamic memory
     
  16. Evengard

    Evengard MDL Novice

    Nov 9, 2007
    10
    1
    0
    That feels like a horribly overuse of CPU, RAM and storage space, tbh, and limited in more ways than one. Not a solution for me, unfortunately. If thinking that way, a better approach would be setup Linux + KVM with Btrfs dedup, and then just booting Windows on top of that as a guest system with all related video cards passthrough etc (and I actually think about such a setup).