Dism warnings

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

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

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

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

EdTittel said:

... you can move onto the next problem or issue, whatever it might be...

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

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

esbkk11000 said:

...It all started when one of my friends suggested that MS Windows10 is s--t, full of problems and is going to die very soon....

Those "Hello. I'm from Microsoft. There's a problem with your PC..." phone scams work the same way. They use all the warnings in the Event Log to convince the victim to let them into their PC to 'fix' it. There are always some errors reported if you look hard enough.

those DISM "warnings" are common place...
If you search your PC for the offending file - it is not present. thus the log warning..

Hi, I started getting BSOD a couple days ago, becoming more and more frequent and ran sfc /scannow: no issues. Then ran DISM, said to check the log file, so I did that and found the same strange error as in the thread. Is this what is causing my BSOD? Also I should add that it periodically would give me an "Oh Snap!" when on various Brave browser pages and giving me the error of Memory management but will not let me run a Memory Diagnostic. When selecting the 'Restart Now and check for problems (recommended)' choice, it says an error is preventing it. Any help would be appreciated. This has pushed my knowledge of what to do to its limit. DISM Log.txt