Cannot shutdown / restart the stystem

v-2kdiw_at_mssupport.microsoft.com
Date: 07/25/04 

Date: Sun, 25 Jul 2004 13:02:13 -0700

Hello,
   I have seen such issues before, and normally the issue
is caused after installing a security patch or service
pack, this problem occurs typically because one of the
Filter drivers by Vertias is not able to unload itself in
the end and hence you will notice a black screen with a
blinking cursor towards the left hand side of the screen.
I would recommend you to go the Add/Remove programs and
look for any software by Veritas, if we have any then
please try uninstalling it and see if that helps.

Thanks
Karan Diwan

Relevant Pages

  • Re: Transition Pack Problem
    ... An error occurred while installing Microsoft Office Outlook 2003 (Service ... Rerun Setup, and retry installing Outlook. ... I tried to run the transition pack and it failed due> to ...
    (microsoft.public.windows.server.sbs)
  • Re: Transition Pack Problem
    ... Rerun Setup, and retry installing Outlook. ... I tried to run the transition pack and it failed due to ... No have you installed the full SBS SP1 or just Windows Server SP1? ... Trying to run the SBS 2003 Transition Pack on our server. ...
    (microsoft.public.windows.server.sbs)
  • AcceptButton causes ObjectDisposedException
    ... I ran across a problem after installing the .NET framework Service ... After installing the service pack on my development machine, ... You have to set the AcceptButton ...
    (microsoft.public.dotnet.general)
  • Re: Is is possible to install the .NET 3.0 SP1 framework under XPe?
    ... Even though I'm installing .NET 3.0 SP1 ... framework, I guess it's upgrading some .NET 2.0 functionality, hence the ... Service Pack 1 -- Setup has determined that this version of .NET Framework is ... Additional information is available in the log file ...
    (microsoft.public.windowsxp.embedded)
  • [Full-Disclosure] Re: ABfrag followup / WITHOUT ATTACHMENT
    ... >We had installed the 'grsec' security patch and had enabled non-executable ... I wouldn't consider installing grsecurity in order to overcome this specific matter, here goes some hints: ...
    (Full-Disclosure)