Dism warnings  

Page 1 of 2 12 LastLast

  1. Posts : 17
    win10 64bit
       #1

    Dism warnings


    How to fix these warnings:
    DISM DISM OSProvider: PID=17248 TID=17340 Unable to set the DLL search path to theservicing stack folder. C:\Windows may not point to a valid Windows folder. -CDISMOSServiceManager::Final_OnConnect

    DISM DISM ProviderStore: PID=17248 TID=17340 Failed to load the provider:C:\Users\esbkk\AppData\Local\Temp\7AA3ACE5-5E0C-4C2E-9DEF-AA1D3C2C39BD\PEProvider.dll.- CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    DISM Provider Store: PID=17248 TID=17340 Failed to load theprovider:C:\Users\esbkk\AppData\Local\Temp\7AA3ACE5-5E0C-4C2E-9DEF-AA1D3C2C39BD\EmbeddedProvider.dll.- CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    Many thanks in advance
      My Computer


  2. Posts : 4,224
    Windows 10
       #2

    What is the exact content of the DISM command you're attempting? What I see in my online research is that you may need to use a mounted ISO as the source for your DISM command. The /source option in the DISM command is tricky to get right, and includes at least a couple of potential gotchas. You may also find it helpful to check over Brink's terrific tutorial on working with this vital Windows command -- namely, Use DISM to Repair Windows 10 Image.
    HTH,
    --Ed--
      My Computers


  3. Posts : 17
    win10 64bit
    Thread Starter
       #3

    Hi Ed -
    Thanks for reply.
    I would like to just fix these three warning I get in the DISM log file using Dism /online /cleanup-image /restore health. Using a mounted ISO as the source I get in fact an additional warning.
    The link refers to using a magnifier...
      My Computer


  4. Posts : 4,224
    Windows 10
       #4

    I can't diagnose your problem unless you reproduce the exact DISM command you're entering inside cmd.exe or PowerShell that emits those error messages. Please do so, and we'll see what I can figure out from there. Without that data, I can't do anything helpful, so sorry.
    --Ed--
      My Computers


  5. Posts : 27,577
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #5

    EdTittel said:
    I can't diagnose your problem unless you reproduce the exact DISM command you're entering inside cmd.exe or PowerShell that emits those error messages.
    Ditto. A screenshot of the command window including the DISM command and the results would be helpful - one that looks like this...

    Dism warnings-1507-dism.png
      My Computers


  6. Posts : 17
    win10 64bit
    Thread Starter
       #6

    Dism warnings-dism1.png

    that is the screenshot of the code that gives me he three warning in the log
      My Computer


  7. Posts : 27,577
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #7

    esbkk11000 said:
    that is the screenshot of the code that gives me he three warning in the log
    Interesting, so the DISM command completed successfully. What prompted you look in the log then?

    Looking at mine I see the same warnings with today's date. Which is also interesting, as I haven't run a DISM command line for weeks. Turns out it was Disk Clean-up's 'clean up system files' that had run DISM for me.

    Code:
    2018-03-20 22:49:51, Info                  DISM   API: PID=8720 TID=9188 DismApi.dll: Parent process command line: "C:\WINDOWS\system32\cleanmgr.exe"
    Actually, I see four warnings, mine are...
    Code:
    2018-03-20 22:49:51, Warning               DISM   DISM Provider Store: PID=8720 TID=9152 Failed to load the provider: C:\WINDOWS\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    ...
    2018-03-20 22:49:51, Warning               DISM   DISM Provider Store: PID=8720 TID=9152 Failed to load the provider: C:\WINDOWS\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    ...
    2018-03-20 22:50:01, Warning               DISM   DISM OS Provider: PID=644 TID=11208 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect
    ...
    2018-03-20 22:50:01, Warning               DISM   DISM Provider Store: PID=644 TID=11208 Failed to load the provider: C:\Users\owner\AppData\Local\Temp\ED80C7E1-4717-4F0A-B332-12C44422DC42\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    ...the first two are unsurprising, as C:\WINDOWS\system32\Dism\SiloedPackageProvider.dll and MetaDeployProvider.dll don't exist.


    But... these are just warnings, there are no errors in the dism log and dism (and disk clean-up) apparently run to completion successfully without reporting an error. I can't see any evidence of actual harm or failure as a result of these warnings. Do you?


    Edit:
    All the above was on a machine running x64 Windows 10 Home (1709) build 16299.309.

    I've just looked for and found the same four warnings on my test machine running x86 Windows 10 Pro (1709) 16299.309.

    So I restored its 1607 system image. Dism's restorehealth runs to 100% and reports success. - but there are still three warnings: 'unable to set the DLL search path to the servicing stack folder...', failed to load PEProvider.dll and failed to load EmbeddedProvider.dll.

    The dll names suggest they relate to the WinPE environment and Embedded systems respectively, so I don't know why Dism would want to load them.
    Last edited by Bree; 20 Mar 2018 at 23:39. Reason: looked at 2nd system
      My Computers


  8. Posts : 17
    win10 64bit
    Thread Starter
       #8

    I suppose you answered my question in a round-about way ... with these warnings, there is never going to be a perfect installation of windows 10 ...
      My Computer


  9. Posts : 3,257
    Windows 10 Pro
       #9

    esbkk11000 said:
    I suppose you answered my question in a round-about way ... with these warnings, there is never going to be a perfect installation of windows 10 ...
    I think you misunderstand. DISM is designed to work with a broad range of versions of windows. That means some files may not exist in one version or another. The warnings are there for debugging purposes, but they are expected because those files don't exist in your version.

    This has nothing to do with a "perfect version". It's just that the tool is designed to work with many versions.
      My Computer


  10. Posts : 4,224
    Windows 10
       #10

    Warnings aren't errors, either, as Bree pointed out in his post. The upshot of the conversation is that while you may not have a clean log (and again, Bree's observations show this is unlikely, if not impossible) you did get a successful restoration of health. IMO that's what really matters here, and you can move onto the next problem or issue, whatever it might be. Be glad! It worked!
    Best wishes,
    --Ed--
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 20:06.
Find Us




Windows 10 Forums