Windows 10: 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

:)

 

Updates are not Installing?

I ran the elevated command prompt and followed those instructions. This was the errors that appeared:

-0x800F081F CBS_E_SOURCE_MISSING The source for the package or file not found.

-Error: 87 - The restorehealth1 option is not recognized in this context.

These are the warnings and errors from the Log file:

Line 47 - Warning DISM DISM Provider Store: PID=9944 TID=5560 Failed to Load the provider: C:\WINDOWS\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Line 48 - Warning DISM DISM Provider Store: PID=9944 TID=5560 Failed to Load the provider: C:\WINDOWS\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Line 73 - Warning DISM DISM OS Provider: PID=9312 TID=10180 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

Line 78 - Warning DISM DISM Provider Store: PID=9312 TID=10180 Failed to Load the provider: C:\Users\adamw\AppData\Local\Temp\331BDB33-975F-4249-8E1D-1A08F7285395\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Line 217 - Warning DISM DISM Provider Store: PID=8368 TID=8552 Failed to Load the provider: C:\WINDOWS\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Line 218 - Warning DISM DISM Provider Store: PID=8368 TID=8552 Failed to Load the provider: C:\WINDOWS\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Line 243 - Warning DISM DISM OS Provider: PID=9668 TID=6608 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

Line 248 - Warning DISM DISM Provider Store: PID=9668 TID=6608 Failed to Load the provider: C:\Users\adamw\AppData\Local\Temp\9BEFC72A-2213-48C3-A5A8-039F6965EC57\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Line 435 - Warning DISM DISM Provider Store: PID=6516 TID=7148 Failed to Load the provider: C:\WINDOWS\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Line 436 - Warning DISM DISM Provider Store: PID=6516 TID=7148 Failed to Load the provider: C:\WINDOWS\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Line 461 - Warning DISM DISM OS Provider: PID=11236 TID=4792 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

Line 466 - Warning DISM DISM Provider Store: PID=11236 TID=4792 Failed to Load the provider: C:\Users\adamw\AppData\Local\Temp\A6A7172C-5AEE-4219-9BBE-46261ED75C7C\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Line 634 - Warning DISM DISM OS Provider: PID=3088 TID=4216 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

Line 639 - Warning DISM DISM Provider Store: PID=3088 TID=4216 Failed to Load the provider: C:\Users\adamw\AppData\Local\Temp\A67CE293-5041-4115-93F5-EB47E186B1BC\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Line 666 - Warning DISM DISM Provider Store: PID=3088 TID=4216 Failed to Load the provider: C:\Users\adamw\AppData\Local\Temp\A67CE293-5041-4115-93F5-EB47E186B1BC\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Line 715 - Info DISM DISM Package Manager: PID=3088 TID=10092 Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error

Line 716 - Error DISM DISM Package Manager: PID=3088 TID=4216 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)

Line 717 - Error DISM DISM Package Manager: PID=3088 TID=4216 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg

Line 718 - Error DISM DISM Package Manager: PID=3088 TID=4216 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)

Line 719 - Error DISM DISM Package Manager: PID=3088 TID=4216 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg

Line 720 - Error DISM DISM Package Manager: PID=3088 TID=4216 Failed to restore the image health. - CPackageManagerCLIHandler:rocessCmdLine_CleanupImage(hr:0x800f081f)

Line 721 - Error DISM DISM Package Manager: PID=3088 TID=4216 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)

Line 792 - Warning DISM DISM OS Provider: PID=8408 TID=10964 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

Line 797 - Warning DISM DISM Provider Store: PID=8408 TID=10964 Failed to Load the provider: C:\Users\adamw\AppData\Local\Temp\BD7BC07B-B943-4E1A-841C-E9E6D773ADBD\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Line 824 - Warning DISM DISM Provider Store: PID=8408 TID=10964 Failed to Load the provider: C:\Users\adamw\AppData\Local\Temp\BD7BC07B-B943-4E1A-841C-E9E6D773ADBD\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

I don't really understand what any of that means, or how to resolve it. Any ideas?

 

Mail App "Add Account" and Sync Not working

Hello,

I appreciate the help! Unfortunately this did not work.

I got the following message:

"Error: 0x800f0950

DISM failed. No operation was performed.

For more information, review the log file."

I reviewed the log file, but I don't know what it means. There were a few "warnings" and a few "errors". They are listed below. There are several other lines in the log file between these, but these are the only ones that are listed "error" or warning. Sorry
if this is too much information, appreciate the help!

"Warning DISM DISM OS Provider: PID=7432 TID=13268 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"

Warning DISM DISM Provider Store: PID=7432 TID=13268 Failed to load the provider: C:\Users\riley\AppData\Local\Temp\92AC0123-AED3-43BD-9547-5325B9C610BE\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Warning DISM DISM Provider Store: PID=7432 TID=13268 Failed to load the provider: C:\Users\riley\AppData\Local\Temp\92AC0123-AED3-43BD-9547-5325B9C610BE\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Error DISM DISM Package Manager: PID=7432 TID=13268 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0950)

Error DISM DISM Package Manager: PID=7432 TID=13268 Failed processing package changes with session options - CDISMPackageManager:rocessChangesWithOptions(hr:0x800f0950)

Error DISM DISM Package Manager: PID=7432 TID=13268 Failed to install capability. - CPackageManagerCLIHandler:rocessCmdLine_AddCapability(hr:0x800f0950)

Error DISM DISM Package Manager: PID=7432 TID=13268 Failed while processing command add-capability. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0950)

Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F0950

 

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--

 

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...

 

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--

 

Ditto. A screenshot of the command window including the DISM command and the results would be helpful - one that looks like this...

 

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"[/quote] 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)[/quote] ...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.

 

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.

 

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--

 

Thanks for all the help!

 

It was my intention to find out for myself if these warnings were commonplace and if so, were they significant. I didn't feel I had sufficient evidence to say conclusively that they were benign, but felt I should at least present my findings so you could draw your own conclusions.

One more exhibit for the defence:

I have an old Windows 7 Toshiba laptop on which I have recently done a 'factory reset'. The reset image included a Dism log generated by Toshiba when they initially built the image. I know this must be the case for two reasons, the first entry is dated 2010-04-06 16:30:34, a timestamp that is earlier than the factory restore image file, plus the line... Code: 2010-04-06 16:30:34, Info DISM DISM.EXE: Host machine information: OS Version=6.1.7600, Running architecture=amd64, Number of processors=2[/quote] ...stating 'Number of processors=2' (this laptop only has a single-core processor).

The first warning is a 'failed to load PEProvider.dll' one...
Code: 2010-04-06 16:45:13, Warning DISM DISM Provider Store: PID=1196 Failed to Load the provider: C:\Users\ADMINI~1\AppData\Local\Temp\FB07F29A-B056-45B9-8C48-EAF530A9D8C3\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e) 2010-04-06 16:45:13, Info DISM DISM Provider Store: PID=1196 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect[/quote] ...followed by the Info "Continuing by assuming that it is not a WinPE image".

I'm confident now that such warnings are harmless and @Mystere's explanation is the correct one.

Please don't let that be trying to get a totally error-free event log. *Smile

 

@Bree: Amen, Brother. Like THAT's going to happen. But Windows has been, is and always will be a source of perpetual activity for those with even the mildest of OCD "must clean the PC" tendencies. I should know!
--Ed--