Dism Error 0x800f0906 Windows 10

| Posted on by



  1. Microsoft Fix For Error 0x80070057
  2. Error 0x800c0006 Live Mail Essentials
  3. Dism Error 0x800f0906 Windows 10 Service Pack
  4. Dism Error 0x800f0906 Windows 10 Xp
-->

This article discusses an issue where converting Server Core to GUI by using a DISM or PowerShell command fails with error 0x800f0906.

Original product version: Windows Server 2012 R2
Original KB number: 3023427

Dism Error 0x800f0906 Windows 10

Symptoms

Welcome to MCB Systems! MCB Systems is a San Diego-based provider of software and information technology services. Our software products include the 3CX Phone System and MCB GoldLink to 3CX. Our proactive I.T. Services free businesses to focus on their work while we maintain your I.T. Contact MCB Systems today to discuss your technology needs! Feb 17, 2016 0 I have a user who has a Lenovo notebook recently upgraded to Windows 10 Pro. He complained that it is very sluggish and Internet Explorer is extremely sluggish since the upgrade to Windows 10.

Sep 10, 2019 After it's execution, DISM creates a log file named 'CMS.log' at 'C: Windows Log CBS' directory (e.g. C: Windows Log CBS CBS.log), that captures any issues found, when DISM command tool is executed. So, the last method to fix DISM's 'Source Files Cannot be Found' error, is to examine the CBS.LOG file, in order to find out and remove the. I made a boot usb from another win 8.1 machine and using tools to do the repair did not work. I am now trying the long way starting with diskpart an bootfix.

This issue occurs when you run a DISM command, an equivalent Windows PowerShell command, or another similar method to convert to GUI.

The DISM command that is used for conversion contains the following switches:

/enable-feature /featurename:ServerCore-FullServer /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell

You receive one of the following information clusters on the command prompt:

  • Information for failure with error code 0x800f0906:

    Dism.exe /online /enable-feature /featurename:ServerCore-FullServer /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /source:wim:d:sourcesinstall.wim:4

    Deployment Image Servicing and Management tool

    Version: 6.3.9600.17031

    Image Version: 6.3.9600.17031

    Enabling feature(s)

    [66.7% ]

    Error: 0x800f0906

    The source files could not be downloaded.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:WindowsLogsDISMdism.log.

  • Information for the DISM command that continues to run for a long time without stopping:

    Dism.exe /online /enable-feature /featurename:ServerCore-FullServer /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /source:wim:d:sourcesinstall.wim:4

    Deployment Image Servicing and Management tool

    Version: 6.3.9600.17031

    Image Version: 6.3.9600.17031

    Enabling feature(s)

    [66.7% ]

Note

Windows

The progress bar on the command prompt always remains at 66.7%. The size of the CBS.log file that is under the %windir%logscbs path will continue to increase.

0x800f081e

CBS logs

The CBS.log file shows one of the following two errors:

  • Error 1

    2014-11-19 06:38:42, Info CBS Session: 30409734_2213032090 initialized by client WindowsUpdateAgent.2014-11-19 06:38:42, Info CBS Opened cabinet package, package directory: ?C:WindowsSoftwareDistributionDownloadea6d57731136ce0c61adfa2056bd76ba, sandbox location: ?C:WindowsSoftwareDistributionDownloadea6d57731136ce0c61adfa2056bd76ba, cabinet location: ?C:WindowsSoftwareDistributionDownloadea6d57731136ce0c61adfa2056bd76bawindows8.1-kb3000850-x64-express.cab, manifest location: ?C:WindowsSoftwareDistributionDownloadea6d57731136ce0c61adfa2056bd76baupdate.mum. . .. . .. . .2014-11-19 06:38:49, Info DPX Extraction of file: amd64_microsoft-windows-c..t-resources-mrmcore_31bf3856ad364e35_6.3.9600.17418_none_dc8ca600359fa9c4mrmcorer.dll failed because it is not present in the container.2014-11-19 06:38:49, Info CBS Asynchronous Session: 30409734_2213032090 finalized. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

  • Error 2

    2014-11-19 23:41:22, Info CBS Not able to find package: Package_for_KB2959977~31bf3856ad364e35~amd64~6.3.1.1 from the cached windows update index. [HRESULT = 0x800f090d - CBS_E_MISSING_PACKAGE_MAPPING_INDEX]2014-11-19 23:41:22, Info CBS Failed to find package: Package_for_KB2959977~31bf3856ad364e35~amd64~~6.3.1.1 from the index mapping [HRESULT = 0x800f090d - CBS_E_MISSING_PACKAGE_MAPPING_INDEX]

Error

Note

The updates that appear during the error may different. The cause of these errors is in the CBS component and the index file, not the updates themselves. The sample output and the list of updates that are mentioned in the error are based on internal testing of a default but updated Windows Server 2012 R2 Core installation that has no additional features or roles enabled.

Cause of Error 1 in the CBS logs section

Microsoft Fix For Error 0x80070057

This issue occurs when the conversion requires files to be downloaded for updates that are bundled as a part of a single updateID.

Dism error 0x800f0906 windows 10 pro

Local testing shows that presence of the following updates on the Core server will cause the conversion to fail with the DPX Extraction 0x80070002 errors:

  • 3000850
  • 3003057
  • 3014442
  • 2919355
  • 2959977

Note

Error 0x800c0006 Live Mail Essentials

To see sample values for updateID, open the wuindex.xml file under the %windir%servicingpackages path, and search for the updateID string.

Dism Error 0x800f0906 Windows 10 Service Pack

Cause of Error 2 in the CBS logs section

Dism Error 0x800f0906 Windows 10 Xp

The cause is the entry <Map Package='package_for_kb2959977~31bf3856ad364e35~amd64~~6.3.1.1'/> is missed under updateID 8452bac0-bf53-4fbd-915d-499de08c338b, inside the file %windir%servicingpackageswuindex.xml.