From: Bill on 25 Jun 2010 13:52 XP Home SP3: With the 1st incident of Windows Explorer following any boot, a "right-click" on any object will cause WE to "not responding" hour-glass and require a Task Mgr "End Task" to terminate WE. Subsequent use of WE behaves normally. What might be the cause of this strange behavior? Thanks, Bill
From: Donald Anadell on 26 Jun 2010 08:08 "Bill" <billstanton(a)psln.com> wrote in message news:e0t608IFLHA.4824(a)TK2MSFTNGP05.phx.gbl... > XP Home SP3: > > With the 1st incident of Windows Explorer following > any boot, a "right-click" on any object will cause WE > to "not responding" hour-glass and require a Task Mgr > "End Task" to terminate WE. Subsequent use of WE > behaves normally. > > What might be the cause of this strange behavior? Maybe a faulty Shell Extension? http://windowsxp.mvps.org/slowrightclick.htm http://www.helpwithwindows.com/techfiles/explorer-crashes.html http://www.nirsoft.net/utils/shexview.html Good luck, Donald Anadell > > Thanks, > Bill >
From: Bill on 26 Jun 2010 17:48 Thanks Donald, there was indeed a faulty Shell Extension. It was easy to find with Shexview, plus the fact that the faulty extension corresponded to the last thing that got installed, namely Eraser. Bill "Donald Anadell" <danadell(a)nospamersmikrotec.com> wrote in message news:OszYXhSFLHA.5448(a)TK2MSFTNGP06.phx.gbl... > > "Bill" <billstanton(a)psln.com> wrote in message > news:e0t608IFLHA.4824(a)TK2MSFTNGP05.phx.gbl... >> XP Home SP3: >> >> With the 1st incident of Windows Explorer following >> any boot, a "right-click" on any object will cause WE >> to "not responding" hour-glass and require a Task Mgr >> "End Task" to terminate WE. Subsequent use of WE >> behaves normally. >> >> What might be the cause of this strange behavior? > > Maybe a faulty Shell Extension? > > http://windowsxp.mvps.org/slowrightclick.htm > http://www.helpwithwindows.com/techfiles/explorer-crashes.html > http://www.nirsoft.net/utils/shexview.html > > Good luck, > > Donald Anadell > > >> >> Thanks, >> Bill >> > >
From: Donald Anadell on 26 Jun 2010 18:20 "Bill" <mlharding(a)jps.net> wrote in message news:o5adnTuumapd6LvRnZ2dnUVZ_uWdnZ2d(a)earthlink.com... > Thanks Donald, there was indeed a faulty Shell Extension. > It was easy to find with Shexview, plus the fact that the > faulty extension corresponded to the last thing that got > installed, namely Eraser. You're welcome Bill, glad you got it sorted out. Good luck, Donald Anadell > Bill > > > "Donald Anadell" <danadell(a)nospamersmikrotec.com> wrote in message > news:OszYXhSFLHA.5448(a)TK2MSFTNGP06.phx.gbl... >> >> "Bill" <billstanton(a)psln.com> wrote in message >> news:e0t608IFLHA.4824(a)TK2MSFTNGP05.phx.gbl... >>> XP Home SP3: >>> >>> With the 1st incident of Windows Explorer following >>> any boot, a "right-click" on any object will cause WE >>> to "not responding" hour-glass and require a Task Mgr >>> "End Task" to terminate WE. Subsequent use of WE >>> behaves normally. >>> >>> What might be the cause of this strange behavior? >> >> Maybe a faulty Shell Extension? >> >> http://windowsxp.mvps.org/slowrightclick.htm >> http://www.helpwithwindows.com/techfiles/explorer-crashes.html >> http://www.nirsoft.net/utils/shexview.html >> >> Good luck, >> >> Donald Anadell >> >> >>> >>> Thanks, >>> Bill >>> >> >> > >
|
Pages: 1 Prev: How to control displayed items in Windows Explorer? Next: PERL - Anyone using this with XP? |