DISM Hosting Service in task manager.

While monitoring my new game game performance, I noticed a DISM Hosting Service process running and accessing the disk at 100%.

Not sure why this would be running as I have no backup software nor use MS backup.

Could I have a virus? or does some other MS process use it or something?

I ran Norton 360 and MBAM with both reporting nothing.

It seems very odd to me.
-=Mark=-

See instructions https://forum.avast.com/index.php?topic=53253.0
scroll down to Farbar Recovery Scan Tool … attach the two diagnostic logs

DISM is legitimate, were you running a VM or backup at the time https://technet.microsoft.com/en-gb/library/hh825236.aspx

I have attached the two logs

@essexboy I have no backup or vm software installed. This is my gaming rig so I don’t need them. Although I was running Cities: Skylines game. Not sure if it, or the Unity engine or steam workshop may cause this.

I also had CPU-Z and HWMonitor running to monitor my system’s performance.

Thanks for the help guys
-=Mark=-

2015-04-12 10:48 - 2015-04-12 10:48 - 00165599 _____ () C:\Users\Mark\Downloads\dism.zip
2015-04-12 10:48 - 2015-04-12 10:15 - 04272347 _____ () C:\Users\Mark\Downloads\dism.log

Could you locate the DISM log and attach that please

Ooops, forgot to post that in my last thread. For some reason I lost the post and had to repost it again. Must have got sidetracked and forgot to hit post or something.

btyw, the log shows this behavior started on 4/4/15, but I had to cut it down in saze as it wouldn’t accept a zip file, and the original was too big (4MB), so I left the yesterday and today. If you need more let me know.

Any clues to what’s going on with DISM? or what could have caused it? I can’t make heads or tails out of the log file.

Thanks for any help.
-=Mark=-

Deployment Image Servicing and Management (DISM.exe) is a command-line tool that can be used to service a Windows® image or to prepare a Windows Preinstallation Environment (Windows PE) image.

I would say disable it from loading at boottime and see what happens.

Just curious.
Why asking here while you are using that Symantec crap ?

There is very sparse information about this. My reading is that it is trying to update a driver, so my best guess at this stage is that you have a corrupt driver and DISM is in a repair loop