Explorer fails to start

[hhmcsv]

My T60 with Win7 Ultimate 32bit have since yesterday behaved oddly. Upon start, the usual desktop does not show, but when right-click, an error box comes up suggesting that explorer did not start, and windows is looking for a solution. This gives the result that the desktop shows up as normal - and everything else is normal from there.
I have done a system restore from two days ago (when this problem was not there), but unfortunately it still is.
Not at every start - about every third.
Any clues to this annoying behaviour?

[Harryc]

Click Start – in the search box, type sfc /scannow and press Enter.
When the scanning is over, right click on the result – run as Administrator and read KB929833 to understand how to use this data.

http://support.microsoft.com/kb/929833

[hhmcsv]

Hi Harryc!
Thanks for the detailed advice. In the meantime I have performed a chkdsk and a defrag.
Running the sfc resulted in an empty file, following the procedure from MS. So I assume there is no faults any more???
I'll get back as soon as the calamity shows again - hopingly never!

[hhmcsv]

So far the problem has not reappeared after about 10 starts. A bit of Googeling on the topic "black screen" has shown, that this type of problem is not unknown. But as far as I could see, the reported problems are of a permanent character, not intermittent as by me. On this link:
http://social.technet.microsoft.com/For ... 9b3cf45e82
there is lengthly discussions and suggestions for cure. But by me, the suggested corrections to the Registry seems in order.
A byproduct of the procedures above (defrag, chkdsk, sfc) has resulted in a shortening of the startup-time of about 10 seconds, from about 70sec to 60sec. In fact, as I measure startup-time to the showing of my Google Calendar in Firefox, sometimes the browser is up and running before the wireless network is finished establishing web-access.
So something good has come of it - now I only hope that the problem stays away!

[hhmcsv]

So now 3 days has gone with no fault re-appearing. My guess is, that the running the sfc did the trick, even though the log showed up empty.