Not able to install feature Containers on Windows Server 2016

Question

Hi Guys,

I request your help about a Windows corruption on my Windows server 2016. I can't reinstall the system so please find below a summary of the problem and all steps I've tried. Thanks in advance for your support ;-)

At first, I'm not able to install new features on the server, I've tried through GUI "Server Manager", by commands like "install-Windowsfeature" and I get always the same (In my example I need Containers feature...) :
install-Windowsfeature Containers Result: Install-WindowsFeature : The request to add or remove features on the specified server failed. Installation of one or more roles, role services, or features failed. The referenced assembly could not be found. Error: 0x80073701 At line:1 char:1

• Install-WindowsFeature containers

•     + CategoryInfo          : InvalidOperation: (@{Vhd=; Credent...Name=localhost}:PSObject) [Install-WindowsFeature], Exception
      + FullyQualifiedErrorId : DISMAPI_Error__Failed_To_Enable_Updates,Microsoft.Windows.ServerManager.Commands.AddWindowsFeatureCommand
  

Success Restart Needed Exit Code Feature Result

---

False No Failed {}

So, I'tried to check the Windows system with these commands in order to found corruptions or missing dependencing and try to fix them:

1°) sfc /scannow Result: Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations.

2°) dism /online /cleanup-image /checkhealth Result: Deployment Image Servicing and Management tool Version: 10.0.14393.3750 Image Version: 10.0.14393.3241 The component store is repairable. The operation completed successfully.

3°) dism /online /cleanup-image /scanhealth Result: Deployment Image Servicing and Management tool Version: 10.0.14393.3750 Image Version: 10.0.14393.3241 [==========================100.0%==========================] The component store is repairable. The operation completed successfully.

4°) dism /online /cleanup-image /scanhealth Result: Deployment Image Servicing and Management tool Version: 10.0.14393.3750 Image Version: 10.0.14393.3241 [==========================100.0%==========================] The component store is repairable. The operation completed successfully.

5°) dism /online /cleanup-image /restorehealth Result: Deployment Image Servicing and Management tool Version: 10.0.14393.3750 Image Version: 10.0.14393.3241 [==========================100.0%==========================] Error: 14 Not enough storage is available to complete this operation. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

6°) In CBS.log I see this kind of corruption present dur to a missing CBS catalog (some packages of KB4284833)

Checking System Update Readiness.

(p) CBS Catalog Missing Package_2847_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2849_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2850_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2851_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2852_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2853_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2854_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2855_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2864_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2874_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2881_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2889_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2892_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2893_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2894_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2895_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2896_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2897_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2898_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2899_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2900_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2901_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2902_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2903_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2904_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2905_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2906_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2907_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2908_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2909_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2911_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2912_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2913_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2914_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2915_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2916_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2917_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2918_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2920_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2921_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2922_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2923_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2924_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2925_for_KB4284833~31bf3856ad364e35~amd6410.0.1.8 (p) CBS Catalog Missing Package_2926_for_KB4284833~31bf3856ad364e35~amd64~~10.0.1.8

Summary: Operation: Detect and Repair Operation result: 0x8007000e Last Successful Step: Entire operation completes. Total Detected Corruption: 45 CBS Manifest Corruption: 45 CBS Metadata Corruption: 0 CSI Manifest Corruption: 0 CSI Metadata Corruption: 0 CSI Payload Corruption: 0 Total Repaired Corruption: 0 CBS Manifest Repaired: 0 CSI Manifest Repaired: 0 CSI Payload Repaired: 0 CSI Store Metadata refreshed: True

Total Operation Time: 603 seconds.

2020-12-16 11:35:27, Info CBS CheckSur: hrStatus: 0x8007000e [E_OUTOFMEMORY], download Result: 0x800f0948 [CBS_E_SOURCE_MISSING_FROM_WU_CAB] 2020-12-16 11:35:27, Info CBS Count of times corruption detected: 1 2020-12-16 11:35:27, Info CBS Seconds between initial corruption detections: -1 2020-12-16 11:35:27, Info CBS Seconds between corruption and repair: -1 2020-12-16 11:35:27, Info CBS SQM: Package change report datapoints not populated because SQM is not initialized or not running online. 2020-12-16 11:35:27, Info CBS Failed to run Detect and repair. [HRESULT = 0x8007000e - E_OUTOFMEMORY] 2020-12-16 11:35:28, Info CBS Reboot mark cleared 2020-12-16 11:35:28, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications 2020-12-16 11:35:28, Info CBS Winlogon: Deregistering for CreateSession notifications 2020-12-16 11:35:28, Info CBS Exec: Processing complete, session(Corruption Repairing): 30856094_632156116 [HRESULT = 0x8007000e - E_OUTOFMEMORY] 2020-12-16 11:35:28, Error CBS Session: 30856094_632156116 failed to perform store corruption detect and repair operation. [HRESULT = 0x8007000e - E_OUTOFMEMORY] 2020-12-16 11:35:28, Info CBS Session: 30856094_632156116 finalized. Download error: 0x8007000e [E_OUTOFMEMORY], Reboot required: no [HRESULT = 0x8007000e - E_OUTOFMEMORY] 2020-12-16 11:35:28, Info CBS Failed to FinalizeEx using worker session [HRESULT = 0x8007000e]

7°) Dism.exe /online /Cleanup-Image /StartComponentCleanup Result:

8°) dism /online /cleanup-image /restorehealth Result: always the same... Deployment Image Servicing and Management tool Version: 10.0.14393.3750 Image Version: 10.0.14393.3241 [==========================100.0%==========================] Error: 14 Not enough storage is available to complete this operation. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

9°) Trying Dism.exe /online /Cleanup-Image /StartComponentCleanup /resetbase No improvement, not able to fix CBS corruptions and not able to install new features...

*10°) Downloading a Windows server 2016 ISO 11°) Downloading KB4284833 which is the KB I get the package issue…. 12°) Mounting the image install.wim corresponding to my server version DISM /mount-wim /wimfile:C:\Temp\Windows_Server_2016_Datacenter_EVAL_en-us_14393_refresh /index:4 /mountdir:c:\Temp\Slipstream* SUCCESS 13°) Adding package KB4284833 msu file into it. Dism /Add-Package /Image:c:\Temp\Slipstream\ /PackagePath=C:\Temp\windows10.0-kb4284833-x64_eb8d1b6306fe77caefec2109844be73ffc7587f6.msu SUCCESS

14°) umount the image and save modifications Dismount-WindowsImage -Path c:\Temp\Slipstream\ -Save

15°) dism /online /cleanup-image /restorehealth /source:WIM:C:\Temp\Windows_Server_2016_Datacenter_EVAL_en-us_14393_refresh\sources\install.wim:4 /LimitAccess Result: Deployment Image Servicing and Management tool Version: 10.0.14393.3750 Image Version: 10.0.14393.3241 [==========================100.0%==========================] Error: 0x800f081f The source files could not be found. Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

16°) Trying to mount a C drive of a “clean” server 2016 where I don’t have any issues and trying to relaunch dism /online /cleanup-image /restorehealth /source:F:\Windows\WinSxS /LimitAccess but same result : Deployment Image Servicing and Management tool Version: 10.0.14393.3750 Image Version: 10.0.14393.3241 [==========================100.0%==========================] Error: 0x800f081f The source files could not be found. Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Thanks again for your support.

Answer 1

Hi,

Thank you for your feedback and glad to hear your issue has been resolved now.

I am very happy to hear my previous reply is useful for you, and will be appreciate if you could accept that reply as answer.

If you have any other issue about Windows, welcome back to Microsoft Q&A.

Bests,
Joy.

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hi,

Thank you for your detail information.

I noticed your CBS log show as 0x8007000e - E_OUTOFMEMORY. Please make sure you have enough memory when try to install that feature.

Please compare with that following official article to make sure you have checked prerequisites and installed docker before container.

Get started: Prep Windows for containers

Clean the existing CBS log and perform to install that feature again. If failure persists, please check CBS log file. If it shows error 0x80073701, and a specific package is massing, we could go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages to find that specific package. Take owner of that registry key, backup and delete it.

Then reboot computer and reinstall container again.

Bests,

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Hi,

Sorry for the late answer, I was able to install Containers feature by :

1°) Try to install Containers feature by install-Windowsfeature Containers => failed
2°) Take a look to cbs.log and found a KB with missing assembly error
3°) Take owner of HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages and subkey (instead TrustedInstaller)
4°) Add your user with full control recursively rights
5°) delete all subkey of this KB, I've used this powershell code =>

$Containers_KB="KB4540670"
$Reg = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages"
Get-ChildItem "$Reg" | ForEach-Object {if ($_ -match "KB4540670"){Remove-Item -Path "Registry::$_" -recurse -Confirm:$false -Force}}

6°) Retry to install Containers feature by install-Windowsfeature Containers => normally success, if it failed again recheck cbs.log and delete the KB in cause again. I 've met this case too and after that it works !
7°) Reput TrustedInstaller as owner of HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages and his subkeys.

Thanks you "JoyQiao-MSFT" I was targetting "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackagesDetect" instead "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages". ;-)

Regards,
Bernard

Answer 4

Thanks for the help and Happy new year !