See also :- Error Message: "Explorer Has Caused an Error in Shdocvw.dll.
Explorer Will Now Close"
http://support.microsoft.com/kb/265209/en-us
Which may not be too helpful.
However, if you're lucky, it *might* just be down to a damaged or corrupted
SHDOCVW.DLL file resulting from your spring clean. It's a longshot but has
to be worth a go, you could try replacing the existing SHDOCVW.DLL file with
a clean, fresh one and see if that helps.
A fresh copy of SHDOCVW.DLL can be extracted and/or copied from the
WIN_14.CAB. A copy of which should be available on your hard drive and/or on
your original WinMe CD (assuming either an MS copy or your OEM has made it
available in a retrievable form.
Mart
"Teri" <Te...@discussions.microsoft.com> wrote in message
news:4637DFA0-F1B2-4659...@microsoft.com...
"Teri" <Te...@discussions.microsoft.com> wrote in message
news:4637DFA0-F1B2-4659...@microsoft.com...
Possibly and if Mart and Mike's suggestions did not solve your situation,
here you can download the dll-file for free:
http://www.dll-files.com/dllindex/dll-files.shtml?shdocvw
But don't venture into scanning or fixing anything, as being offered.
That might bring you more trouble instead.
Best of luck,
Harry.
--
Noel Paton
CrashFixPC
Nil Carborundum Illegitemi
www.crashfixpc.co.uk
"Teri" <Te...@discussions.microsoft.com> wrote in message
news:0CDD1425-8AD9-4B9E...@microsoft.com...
Not trying to pour cold water on Noel's recommendation of 'fixing the
SHDOCVW problem first', I just wonder what else is missing and think a
clean install might be a quicker and easier proposition. BTW - it also
appears that there are several other versions of SHDOCVW.DLL out there on
the web, hence my suggestion of using a clean copy of the WinMe version.
However, before taking the clean install plunge, perhaps a scanreg /restore
*might* just do the trick - really clutching at straws - assuming the
'problem' only manifested itself within the past 5 days or so (i.e. there is
still at least one good restore date prior to the problem)
Also, depending on which version of Internet Explorer was installed, Terri
*may* be able to download and update to a later version. But whether that
will fix things, we'd have to wait and see.
A quick Google doesn't really offer any useful fixes to Terri's report
either, so if time and effort are important considerations, my advice would
be a clean install. (Remembering to back-up personal data and to note the 25
digit product key first!) It should be 'do-able' within a day.
Mart
"Noel Paton" <noeldp(spamless)@crashfixpc.co.uk> wrote in message
news:%23doi2b2...@TK2MSFTNGP05.phx.gbl...
"Mart" <mart(NoSpam)@nospam.nospam> wrote in message
news:e4ONBp3O...@TK2MSFTNGP02.phx.gbl...
I'm a little short on ME VM's ATM -
The original SHDOCVW should be v 5.50.4134.100
Updating to IE6SP1 (the latest for ME), new version number is 6.2800.1106
(and the old version is stored in a pre-290700 SR as shdocvw.0
installing only the IE updates brings the version number to 6.0.2800.1849
installing the rest of the updates doesn't change the version number
Reregistering the dll may also be a good idea (especially if it's been
replaced by another copy! - some were got at by hackers)
regsvr32.exe shdocvw.dll
from the Run box should do it
--
Noel Paton
CrashFixPC
Nil Carborundum Illegitemi
www.crashfixpc.co.uk
"Mart" <mart(NoSpam)@nospam.nospam> wrote in message
news:e4ONBp3O...@TK2MSFTNGP02.phx.gbl...