SAV9 and NT4 - OleMainThreadWndName errors
Results 1 to 4 of 4

Thread: SAV9 and NT4 - OleMainThreadWndName errors

  1. #1
    Master-Jedi-Pimps0r & Moderator thehorse13's Avatar
    Join Date
    Dec 2002
    Location
    Washington D.C. area
    Posts
    2,883

    SAV9 and NT4 - OleMainThreadWndName errors

    Incase anyone else has a **** load of NT4 boxes and you decide to throw SAV9 on them, prepare for the madness of OleMainThreadWndName errors. To spare someone the surprise of this, take a peak at this tech bulleton:

    Symantec AntiVirus Corporate Edition 9.0.2.1000, Release MR2
    Fix ID: 1-2XZVIR
    Shutdown error on Windows NT 4: "OleMainThreadWndName Will Not Close (Must be Ended)"
    Symptom: After upgrading Symantec AntiVirus, shutting down NT4 (SP6) will hang, and get a pop-up window saying the OleMainThreadWndName will not close (End, Wait, Cancel). This occurs twice before NT4 will shut down successfully.
    Solution: Recent changes to support Windows Security Center introduced a new dependency on the code as defined by Microsoft (KB 136885). The code has been corrected to resolve this problem.

    Anway, the fix does work. Hope this saves someone a nasty surprise on a Friday afternoon.

    --TH13
    Our scars have the power to remind us that our past was real. -- Hannibal Lecter.
    Talent is God given. Be humble. Fame is man-given. Be grateful. Conceit is self-given. Be careful. -- John Wooden

  2. #2
    Super Moderator: GMT Zone nihil's Avatar
    Join Date
    Jul 2003
    Location
    United Kingdom: Bridlington
    Posts
    17,191
    A pathetic spambot folks, so I put it out of its misery.
    If you cannot do someone any good: don't do them any harm....
    As long as you did this to one of these, the least of my little ones............you did it unto Me.
    What profiteth a man if he gains the entire World at the expense of his immortal soul?

  3. #3
    Junior Member
    Join Date
    May 2014
    Posts
    6
    What is the reason of this error?

  4. #4
    Super Moderator
    Join Date
    Feb 2014
    Location
    US
    Posts
    77
    Quote Originally Posted by paki250 View Post

    What is the reason of this error?
    It's in the original message above:

    Quote Originally Posted by thehorse13 View Post

    Recent changes to support Windows Security Center introduced a new dependency on the code as defined by Microsoft (KB 136885). The code has been corrected to resolve this problem.
    Rad

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •