DISM 10.0.19044.1586 reports in DISM.inf Error :CBS_E_SOURCE_MISSING 0x800f081f or : 0x8007007B, The filename, directory name, or volume label syntax is incorrect.

Martin Newbold 1 Reputation point
2022-08-17T08:10:40.247+00:00

Hi everyone!

How can I move forward in solving this problem?

----------

I have contacted technical support Request Number 1042707508 after my computer was alleged hacked on Sunday expressing difficulties running DISM with a USB key with Microsoft supports help we created a H :\Windows.iso on a 16GB USB key with both a low level format and basic NTFS format. Then by using MediaCreationTool21H2.exe to export Windows.iso onto the HP 16gb NTFS drive . This process needs patience as it takes some time to execute .

The proper process of execution was followed with the computer placed in cmd shell in the following process:

"Checking Repair...",
"Diagnosing your PC"
Advanced options' then 'troubleshoot'
`'advanced options'
'CMD command shell '

to repair your hard drive in this command shell I ran

x:\Windows\System32\SFC /SCANNOW /OFFBOOTDIR=C:\ /OFFWINDIR=C:\Windows

This executes with error locating potential problems on the drive .

Then running
x:\Windows\System32\dism.exe /Image:D:\ /Cleanup-Image /Restorehealth /Source:H::Windows.iso.

The following is produced
[=============================== 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 this feature. For more information on specifying the source location , see http://go.microsoft.com/fwlink/?Linkid=243077

----------

The error is evident in HRESULT as a file handle return in DISM.inf which is located at x:\Windows\Logs\DISM

2022-08-16 12:24:58, Info CSI 00000002 CSI Store 1935785526128 initialized
2022-08-16 12:24:58, Info CBS Build: 19041.1.amd64fre.vb_release.191206-1406
2022-08-16 12:24:58, Info CBS Session: 1348_82995281 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null)
2022-08-16 12:24:58, Info CBS Exec: Addsource called, Session: 1348_82995281, Client: DISM Package Manager Provider, from GPO: No, Path: h:\Windows.iso
2022-08-16 12:24:58, Warning CBS The alternate source path directory could not be accessed [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
2022-08-16 12:24:58, Info CBS Failed to add new file source [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
2022-08-16 12:24:58, Info CBS Failed to add alternate file source [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
2022-08-16 12:24:58, Info

Clearly this error Is indicative of a file handling error 0x8007007B error is caused by corrupt system files that are preventing the activation of your Windows license key, running the System File Checker (SFC) will automatically resolve the issue.

DISM 10.19044.1586 is the latest version part of MediaCreationTool21H2 which is worrying currently this verification of file on the USB stick is running and executes these errors on recovery for Microsoft 10 Professional . I note that this has also occurred on Windows Server only https://learn.microsoft.com/en-us/answers/questions/269141/dism-not-finding-source.html and not Windows 10 Professional however the advice on this was given in good faith would none of this be appropriate to windows 10 too?

Can any one give any help that will resolve these errors ?

Thank you for looking.

Windows for business | Windows Client for IT Pros | User experience | Other
{count} votes

6 answers

Sort by: Most helpful
  1. Martin Newbold 1 Reputation point
    2022-08-18T05:59:56.013+00:00

    I found these article https://www.wintips.org/fix-dism-source-files-could-not-be-found-windows-10-8/ and https://www.wintips.org/how-to-extract-install-esd-to-install-wim-windows-10-8/ that was very good and informed you to create a install.wim file if the install.esd file did not work and this error above occurred. then extracted install.wim from install.esd using

    H:  
     CD wim  
     CD sources  
     dism /export-image /SourceImageFile:install.esd /SourceIndex:6 /DestinationImageFile:install.wim /Compress:max /CheckIntegrity   
    

    So this was then tried with

     DISM /Image:C\ /Cleanup-Image /RestoreHealth /Source:H:\WIM\sources\install.wim:1 /LimitAccess  
    

    Remember this file it creates is nearly 5GB so ensure you have enough space free.


  2. Martin Newbold 1 Reputation point
    2022-08-18T17:48:44.57+00:00

    August 18, 2022, @Syed yousuf shafi said
    Try this.

    md C:\test\offline  
    DISM.exe /Mount-Wim /WimFile:h:\wim\sources\install.wim /index:1 /MountDir:C:\test\offline /ReadOnly  
    Dism.exe /Online /Cleanup-Image /restoreHealth /source:C:\test\offline /loglevel:4  
    When you are done.  
      
    DISM.exe /Unmount-Wim /MountDir:C:\test\offline /discard  
    I added the loglevel in the hope that if it fails again, there might be something useful in C:\WINDOWS\Logs\DISM\dism.log
    

  3. Martin Newbold 1 Reputation point
    2022-08-18T18:47:47.57+00:00

    The other point is that why DISM is not able to repair WinSxS? which is clearly causing part of the computers concern

    0 comments No comments

  4. Martin Newbold 1 Reputation point
    2022-08-19T05:46:38.423+00:00

    NOT AN ANSWER MICROSOFT PHILIPPINES IN 2 HOUR DENIAL!

    I went back onto Microsoft chat as it seems to me that Microsoft Philippines is in denial in regard the messages that DISM is creating and especially asking for an additional the 14 files in WindSxS which it described in the SFC log as being corrupted when in fact it appears they have been deleted possibly by Pegasus.

    It it not clear why in this two hour chat with Russel that his opinion was that from what he was saying was his option is to wipe machine rather than fix issues on them forcing your customers on to other O/S which are more stable. I informed him that they are making up responses in contrast to hard facts established by your team and the screen evidenced errors and data supplied from DISM.

    Why are Microsoft Philippines in "Denial" about what messages DISM are providing users . Why is Microsoft Philippines not providing "source" described by DISM as required to restore the feature. Russell repeatedly stated this "Source" was in Windows. How can this be true when his team had provide three different mechanism to extract the ICO and then use what it classified was the important file \sources\install.est which it used https://www.wintips.org/how-to-extract-install-esd-to-install-wim-windows-10-8/ to extract it to a wim file and copy ant mount it on the hard drive. using .

    md C:\test\offline  
    DISM.exe /Mount-Wim /WimFile:h:\sources\install.wim /index:2 /MountDir:C:\test\offline /ReadOnly  
    Dism.exe /Image:c\ /Cleanup-Image /restoreHealth /source:C:\test\offline /loglevel:4  
    

    When you are done.

    DISM.exe /Unmount-Wim /MountDir:C:\test\offline /discard  
    

    Microsoft Philippines said I added the log level in the hope that if it fails again, there might be something useful in C:\WINDOWS\Logs\DISM\dism.log

    Quite clearly this was added to find out what DISM was requesting and the something useful evidence CBS_E_SOURCE_MISSING which was not contained in the WIM fil generated from the Installed file

    At no point did they suggest how to look in the recycle bin as a possible solution.

    Further more this PE Edition cannot seem to run the utilities to Shadow copy the System Restore onto the device of which there is entries listed that could be used . I understood wiping a drive should be the last resort why are Microsodt Philapines unwilling to understand this issue and then provide solution ?


  5. Martin Newbold 1 Reputation point
    2022-08-19T10:45:27.333+00:00

    I copied these files wcp.dll, wshbth.dll, Windows.Cortana.OneCore.dll, WindowsInternal.ComposableShell.DesktopHosting.dll,
    Windows.WARP.JITService.dll, rtffilt.dll, winrnr.dll, Windows.Devices.Printers.Extensions.dll, wshext.dll, Windows.Security.Authentication.OnlineId.dll, wksprtPS.dll, Windows.Web.dll, wksprtPS.dll, WindowsCodecsRaw.dll from https://www.dll-files.com/ into my C:\Windows\System32 as this was the only option left as Microsoft Philippines would not come to the aid in providing any reasonable solution. I also had not heard from Eric who promised to Telephone today.

    This remarkably changed nothing which is suggestive of lots of other things . I tried running SFC /SCANNOW which found no corruption after 100%. I tried SFC /SCANNOW /OFFBOOTDIR c:\ /OFFWINDDIR=C:\Windows to see if it would create a useable log for DISM.

    This gave the message :
    Windows Resource Protection found corrupt files but was unable to fix some of them .

    I again ran without md C:\test\offline as it had been already created

    X:\Windows\System32\DISM.exe /Mount-Wim /WimFile:h:\wim\sources\install.wim /index:1 /MountDir:C:\test\offline /ReadOnly  
           
    X:\Windows\System32\Mounting Image :  
    X:\Windows\System32\[============================ 100% ============================]  
    X:\Windows\System32\The operation completed successfully  
    

    I then ran as directed :

    X:\Windows\System32\Dism.exe /Image:C\ /Cleanup-Image /RestoreHealth /source:C:\test\offline /loglevel:4  
    X:\Windows\System32\[============================ 100% ============================]  
    

    If fact the result was exactly the same :

    X:\Windows\System32\[=============================== 100.0% ===============================]  
    X:\Windows\System32\Error: 0x800f081f  
    X:\Windows\System32\The "source" option to specify the location of files that are required to restore the feature . For more information on specifying a source location , see http://go.microsoft .com/fwlink/?LinkId=243077  
    

    important part of dism.log

    2022-08-19 03:27:51, Info CBS Not all CSI corruption was fixed, create CorruptionDetectedDuringAcr flag for slow mode reset
    2022-08-19 03:27:51, Info CBS CheckSur: hrStatus: 0x800f081f [CBS_E_SOURCE_MISSING], download results: <none>
    2022-08-19 03:27:51, Info CBS Count of times corruption detected: 1
    2022-08-19 03:27:51, Info CBS Seconds between initial corruption detections: -1
    2022-08-19 03:27:51, Info CBS Seconds between corruption and repair: -1
    2022-08-19 03:27:51, Info CBS Failed to run Detect and repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    2022-08-19 03:27:52, Info CBS Exec: Processing complete, session(Corruption Repairing): 1996_3516312 [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    2022-08-19 03:27:52, Info DISM DISM Package Manager: PID=1996 TID=1892 Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error
    2022-08-19 03:27:52, Error CBS Session: 1996_3516312 failed to perform store corruption detect and repair operation. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    2022-08-19 03:27:52, Info CBS Session: 1996_3516312 finalized. Reboot required: no [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    2022-08-19 03:27:52, Error DISM DISM Package Manager: PID=1996 TID=1892 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.