Tried idea's supplied by Alice's link[s]??? Have you peeked into these yet?
The cause for this error has many possible reasons. Read the sublink topics and see if there's anything that could directly apply to you or your software.
The Mshtml.dll file is responsible for image rendering.
Since this is recent, it may be helpful to know what you may have done recently. Installed or unistalled anything, updated anything, changed graphic settings...etc.
Just hoping for a little more to go on to help pin this down.
==================== Wait a minute...........
Just noticed your post and inquiry into the mysterious "closing.exe"
error. All of this may be tied into this one problem. I think you need to concentrate on the "what, why and where" this is coming from.
Link to that post: CLOSING error message persists!
Have you done the "file find" for closing.exe
to see if this exists? If found right click it and select properties to see what nfo you get from this. What folder is it in?
Could also do an advanced search for files *.* that contain text
Have you tried running SFC to see if it flags any files as corrupt?
Keeping this in mind:
Here's some friendly handy dandy advice to accompany an SFC use recommendation:
Sfc is best left, used as an extractor for file replacement and a "Helper" tool ONLY. For those who have no foreknowledge or familiarity with their OS files, drivers [.dll's etc.] it will be very confusing and intimidating. In addition, in many cases, be down right dangerous when it comes to inflicting cases of "Versionitus".
If you do not use it often and routinely to update the baseline file such as after all upgrades/updates, new installations or uninstalls you can easily be over whelmed by all the files that get flagged.
Don't get me wrong, this can be a good tool for a troubled OS but it takes a great deal of upkeep and a thorough understanding of how the baseline file list and files of description: altered/changed, corrupt, and deleted are determined.
Altered files= If System File Checker detects a change in date, time, size, or version, it considers the file to be........
Changed= a change in date, time, or version, file will be reported as changed. SFC can not determine if this was a good/bad, planed or unplanned. It is up to you as the user to determine if this change was an due to an unplanned overwrite, virus, system glitch etc. or an "expected"/planed change as a result via an update/upgrade or install.
Maybe Corrupt= You are always notified of damaged files. A file is identified as damaged if its date and version match, but the "CRC" [File size: A checksum added to a file entry whenever a file is written to disk, used to see if the file has changed] value does not match the baseline. Usually, if a file is flagged as corrupt your best bet is to err on sfc determination that it is corrupt. You should have enabled the option to always backup file before replacement in case of mis- judgment.
NOTE*I had this option enabled but have since disabled it as I frequently install and uninstall app's and games. This got to be more of a nuisance than an aid.
To sum up:
This tool should only be used as a helper app unless:
*You have formed a habit of running this as part of a regular routine to keep the "baseline list" up to date such as after an update/upgrade/install/uninstall,
*Or are specifically using it to check for "file corruption flags" due to current application problem]. Any file flagged as corrupted or changed should be further investigated before taking sfc's word that it needs replacement. If a file is flagged as such just click sfc's "ignore option" for now, until you can confirm it is not part of a recent install or update.
note*Generally never replace a newer version file with an older one.
1]there are always exceptions to every rule and there are even workarounds for the exceptions.
2]Usually, if a file is flagged as corrupt your best bet is to err on sfc determination that it is corrupt. It has a backup option that will offer to backup any file you replace so this is reversible.
3]known bug in original win98 SFC has been fixed with updates or winSE, but if you have not employed such updates:
You must be careful to browse[point] to specific cab folder when dealing with certain key file replacements as indicated by links below: http://support.microsoft.com/support.../q192/8/32.asp
What ya' got running at startup?
This just may be a bad app or script, running at startup that is making an internal call to close and is unable to. The fact that it faults and fails to do what it is suppose to [CLOSE] may be interfering with explorer/iexplore load.
Got to admit though, this sure sounds viral or trojan in nature, how current is your dat file for Norton. May need to run a specialized Trojan" cleaner. Many virus programs can not properly detect Trojan's.