Working Deduplication files for Microsoft Windows 10

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

  1. dw0808

    dw0808 MDL Novice

    Jul 20, 2019
    4
    0
    0
    You are my hero. After both commands and afterwards installation of the packages anything works as it should. Thanks!
     
  2. smashed

    smashed MDL Junior Member

    Feb 6, 2008
    51
    13
    0
    Awesome!
     
  3. LevT

    LevT MDL Novice

    Dec 2, 2008
    16
    0
    0
    Having done that I see again

    PS C:\Windows\system32> dism /online /add-package /packagepath:Microsoft-Windows-VdsInterop-Package-amd64-10.0.17763.1.cab /packagepath:Microsoft-Windows-VdsInterop-Package-amd64-10.0.17763.1-en-US.cab
    dism /online /add-package /packagepath:Microsoft-Windows-FileServer-ServerCore-Package-amd64-10.0.17763.1.cab /packagepath:Microsoft-Windows-FileServer-ServerCore-Package-amd64-10.0.17763.1-en-US.cab
    dism /online /add-package /packagepath:Microsoft-Windows-Dedup-ChunkLibrary-Package-amd64-10.0.17763.1.cab /packagepath:Microsoft-Windows-Dedup-ChunkLibrary-Package-amd64-10.0.17763.1-en-US.cab
    dism /online /add-package /packagepath:Microsoft-Windows-Dedup-Package-amd64-10.0.17763.1.cab /packagepath:Microsoft-Windows-Dedup-Package-amd64-10.0.17763.1-en-US.cab
    dism /online /enable-feature /featurename:Dedup-Core /all

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1
    Image Version: 10.0.18362.239
    An error occurred trying to open - Microsoft-Windows-VdsInterop-Package-amd64-10.0.17763.1.cab Error: 0x80070002
    An error occurred trying to open - C:\Windows\system32\Microsoft-Windows-VdsInterop-Package-amd64-10.0.17763.1.c
    ab Error: 0x80070002
    An error occurred trying to open - Microsoft-Windows-VdsInterop-Package-amd64-10.0.17763.1-en-US.cab Error: 0x80
    070002
    An error occurred trying to open - C:\Windows\system32\Microsoft-Windows-VdsInterop-Package-amd64-10.0.17763.1-e
    n-US.cab Error: 0x80070002
    Error: 2
    An error occurred trying to open - C:\Windows\system32\Microsoft-Windows-VdsInterop-Package-amd64-10.0.17763.1.c
    ab Error: 0x80070002
    An error occurred trying to open - C:\Windows\system32\Microsoft-Windows-VdsInterop-Package-amd64-10.0.17763.1-e
    n-US.cab Error: 0x80070002
    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
    …..
     
  4. bfoos

    bfoos MDL Guide Dog

    Jun 15, 2008
    466
    370
    10
    #524 bfoos, Jul 25, 2019
    Last edited: Jul 25, 2019
    That error indicates that the packages cannot be found. Looking at your path, DISM is looking for the packages in C:\Windows\System32. You don't need to use PowerShell to install the packages, it is only needed to run any dedup commands. Simply opening an elevated command prompt from the directory containing the extracted dedup pack and copy/pasting the commands from the install.txt will get you started down the proper path.
     
  5. LevT

    LevT MDL Novice

    Dec 2, 2008
    16
    0
    0
    Thank you, but this doesn't matter for me


    Microsoft Windows [Version 10.0.18362.239]
    (c) 2019 Microsoft Corporation. All rights reserved.
    C:\Windows\system32>cd C:\Users\Op\Downloads\dedup-10.0.17763.1
    C:\Users\Op\Downloads\dedup-10.0.17763.1>dism /online /add-package /packagepath:Microsoft-Windows-VdsInterop-Package-amd64-10.0.17763.1.cab /packagepath:Microsoft-Windows-VdsInterop-Package-amd64-10.0.17763.1-en-US.cab
    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1
    Image Version: 10.0.18362.239
    Processing 1 of 2 - Adding package Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~~10.0.17763.1
    [==========================100.0%==========================]
    Processing 2 of 2 - Adding package Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1
    [==========================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.
     
  6. Krakatoa

    Krakatoa MDL Senior Member

    Feb 22, 2011
    487
    697
    10
    #526 Krakatoa, Jul 26, 2019
    Last edited: Jul 26, 2019
    :sun:
    Microsoft Windows [Version 10.0.18362.239] <> 10.0.17763.1
     
  7. bfoos

    bfoos MDL Guide Dog

    Jun 15, 2008
    466
    370
    10
    As the user above me more subtly pointed out, the reason it isn't working is because you are trying to install the 17763 dedup pack on a 18362 system. Grab the 18362.1 dedup pack and try again.
     
  8. LevT

    LevT MDL Novice

    Dec 2, 2008
    16
    0
    0
    #528 LevT, Jul 30, 2019
    Last edited: Jul 30, 2019
    Окау you were right, many thanks

    Has anyone some experience trying to enable the deduplication on the Windows boot volume?
    I feel being reasonable to apply an exclusion list similar to WimBootCompress.ini

    Aiming to avoid extra partitioning for vhdx storage volume

    What'd you concern about enabling the deduplication by default on most volumes as an extra step after volume format, and only managing their deduplication settngs then?
     
  9. bfoos

    bfoos MDL Guide Dog

    Jun 15, 2008
    466
    370
    10
    You can't enable data deduplication on a boot volume. Storage volumes only.
     
  10. SneakyZEKE

    SneakyZEKE MDL Novice

    Jan 17, 2018
    1
    0
    0
    Many BSOD with Version 10.0.18362.239. Have you 18362.295 please ?
     
  11. Nessix

    Nessix MDL Novice

    Sep 29, 2014
    1
    0
    0
    Is there a possibility to get the de version of those packages? Or other languages as en?
     
  12. bfoos

    bfoos MDL Guide Dog

    Jun 15, 2008
    466
    370
    10
    I don't know, I only use en-US systems. And I don't sprechen sie Deutsch so I won't be downloading any de-DE ISO's and installing them to extract the packages. Though I can say that I've only ever seen en-US packages shared here.
     
  13. whatever127

    whatever127 MDL PHP Wizard

    Nov 9, 2012
    964
    6,487
    30
    Other language versions can be easily installed by extracting server language pack and installing mum files for required packages.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. HardyLi

    HardyLi MDL Novice

    Oct 4, 2018
    6
    0
    0
    Windows 10 1909 is released soon, look forward to updating, thank you!
     
  15. bfoos

    bfoos MDL Guide Dog

    Jun 15, 2008
    466
    370
    10
    There are no 1909 Dedup packages. The 18362.1 packages apply for both 1903 and 1909.
     
  16. HardyLi

    HardyLi MDL Novice

    Oct 4, 2018
    6
    0
    0
    Oh! thank you very much!
     
  17. iorx

    iorx MDL Novice

    Sep 15, 2013
    1
    1
    0
    My 2c.
    18362.1 worked like a charm! Thanks!

    My primary target was to dedup my VirtualBox machines.
    But you can't dedup the system volume so my take on the this was to create a vhdx volume which I activated dedup on. But with that followed the optimization of the vhdx after dedup had done its job.

    So here if someone else need to accomplish something similar.

    Created a 256GB vhdx and mounted it as E: (in my case stored at "C:\usr\nobackup\vhdx\voldedup.vhdx")
    Enabled debup with:
    Code:
    Enable-DedupVolume -Volume E:
    Set-DedupVolume -Volume E: -MinimumFileAgeDays 0
    
    Have a batch file which runs as SYSTEM at event SysteamStartup (Task Scheduler) which optimize the size of the vhdx. This can also be run manually but one have to make sure nothing is using the volume first.

    File: diskpart-do.cmd
    Code:
    if exist "E:\" (
        (
        echo select vdisk file="C:\usr\nobackup\vhdx\voldedup.vhdx"
        echo detach vdisk
        echo select vdisk file="C:\usr\nobackup\vhdx\voldedup.vhdx"
        echo compact vdisk
        echo attach vdisk
        ) | diskpart
    ) else (
        (
        echo select vdisk file="C:\usr\nobackup\vhdx\voldedup.vhdx"
        echo compact vdisk
        echo attach vdisk
        ) | diskpart
    )
    
    And a powershell which forces dedup jobs. Run manually when needed (default scheduled jobs does this but only once a week).
    Code:
    Start-DedupJob -Volume E: -Wait -Type Optimization -Priority High -Memory 80
    Start-DedupJob -Volume E: -Wait -Type GarbageCollection -Priority High -Memory 80 -Full
    Start-DedupJob -Volume E: -Wait -Type Scrubbing -Priority High -Memory 80 -Full
    Start-Sleep -Seconds 2
    Invoke-Item ".\diskpart-do.cmd"
    
    My 200GB of VirtualBox machines (2 x OSX, 2 x Windows 7 and 4x Windows 10 with a couple of snapshots each) are now stored at approx 50% of the original space!

    Thanks again for extracting working files for dedup to work on Windows 10!

    Brgs,