Re: Explorer shell (desktop) does not start automatically
- From: "C_O" <magsub@xxxxxxxxx>
- Date: Tue, 29 May 2007 23:23:32 -0700
(bump - someone must have the answer...)
"C_O" <magsub@xxxxxxxxx> wrote in message
news:OMvGboJoHHA.3952@xxxxxxxxxxxxxxxxxxxxxxx
Odd behavior since installing the May security patches. This is SBS2003
standard, SP2 installed. When the system starts or restarts, and I log in
using Remote Desktop, it starts with a command window only. This is the
same effect and remedy as if I had killed the "explorer.exe" process in
Task Manager, except that in this case this process never even started in
the first place a new user session started. I am logged in, but I have to
manually type "explorer" in that command window to bring up the desktop
with its icons, toolbars, Start menu, etc. -- AFAIK this behavior started
after installing the May Microsoft patches, and persists after installing
the "standalone" latest MSI fix patch. However this may be pure
coincidence. There may not be a cause and effect correlation here.
Has anone else run into this, and how do I fix it? I can live with it, but
this could be disconcerting if anyone else ever has to manage this
machine. The error logs show no error, except the usual TermServDevices
bogus error for the printer drivers that exist on the remote controlling
machine but not on the server itself (the server is not used to run end
user applications at all).
TIA
C_O
.
- Follow-Ups:
- Re: Explorer shell (desktop) does not start automatically
- From: Terence Liu [MSFT]
- Re: Explorer shell (desktop) does not start automatically
- References:
- Prev by Date: RE: question about web server
- Next by Date: RE: FW: SBS Connection Manager Question
- Previous by thread: Re: Explorer shell (desktop) does not start automatically
- Next by thread: Re: Explorer shell (desktop) does not start automatically
- Index(es):
Relevant Pages
|