Results 1 to 4 of 4

Thread: New World of Warcraft Launcher is not remembered as allowed

  1. #1
    greygoosecitrus Guest

    Default New World of Warcraft Launcher is not remembered as allowed

    ~Snip~

    Firewall Info
    http://i281.photobucket.com/albums/k.../ZAVersion.jpg

    Alert #1
    http://i281.photobucket.com/albums/k...ZAMessage1.jpg

    Alert #2
    http://i281.photobucket.com/albums/k...ZAMessage2.jpg

    The new launcher seems to be registered by the firewall as a new program every time.

    Operating System:Windows XP Pro
    Software Version:8.0
    Product Name:ZoneAlarm Pro
    Last edited by GeorgeV; March 30th, 2010 at 01:50 PM. Reason: warcraft link remove due to Forum Rules

  2. #2
    thwarter Guest

    Unhappy Re: New World of Warcraft Launcher is not remembered as allowed

    Quote Originally Posted by greygoosecitrus View Post
    http://i281.photobucket.com/albums/k.../ZAVersion.jpg

    Alert #1
    http://i281.photobucket.com/albums/k...ZAMessage1.jpg

    Alert #2
    http://i281.photobucket.com/albums/k...ZAMessage2.jpg

    The new launcher seems to be registered by the firewall as a new program every time.

    Operating System:Windows XP Pro
    Software Version:8.0
    Product Name:ZoneAlarm Pro
    I also have this problem, and I believe it is because WoW is dynamically changing something in its startup launch (not login) procedure. I don't think it's a ZA problem, I think it's doing what it's supposed to do. I did enable in ZA Pro the "changes frequently" option and gave it super access, but that made no difference. I suspect a component is being dynamically updated at WoW launch. Eventually I'll get tired of this and contact World of Warcraft Technical Support.

    Perhaps someone has found a ZoneAlarm (I use the Pro version) setting, perhaps involving a component of WoW, that will eliminate this WoW.exe launch annoyance? Sometimes ZA is a little late in the popup occurrence, interfering with entering the WoW login password.
    Last edited by GeorgeV; March 30th, 2010 at 01:51 PM. Reason: Set instant email notification for this thread.

  3. #3
    pslumbert Guest

    Default Re: New World of Warcraft Launcher is not remembered as allowed

    Hi,

    Don't know if my suggestion is what you're looking for or not, but I got frustrated with the launcher and decided to bypass it altogether by accessing the WoW sign-on screen directly using the (WoW) executable.

    The executable (icon) can be found in the directory where you installed WoW, typically
    C:\program files\World of Warcraft.

    You can create a shortcut on your desktop and access it there. To have ZA remember allowed access, you should check the box in the ZA alert that pop ups when alerted that the product is asking for internet access.

    Hope this helps!
    Pat

  4. #4
    thwarter Guest

    Default Re: New World of Warcraft Launcher is not remembered as allowed

    Quote Originally Posted by pslumbert View Post
    Hi,

    Don't know if my suggestion is what you're looking for or not, but I got frustrated with the launcher and decided to bypass it altogether by accessing the WoW sign-on screen directly using the (WoW) executable.

    The executable (icon) can be found in the directory where you installed WoW, typically
    C:\program files\World of Warcraft.

    You can create a shortcut on your desktop and access it there. To have ZA remember allowed access, you should check the box in the ZA alert that pop ups when alerted that the product is asking for internet access.

    Hope this helps!
    Pat
    That's what I do, and that used to work. I don't use the launcher. However, it now appears that Blizzard periodically replaces that file, triggering ZAP. Configuring ZAP for "changes frequently" and checking the box to remember it does not resolve the issue with the wow.exe file. Although sometimes ZAP does not get triggered at all during start, usage, or shutdown of WoW, often ZAP will be triggered *at* the WoW login screen, never during actual usage of the game, and rarely but sometimes at exit of the game. I think the game downloads a file and then deletes wow.exe, and then re-names it to wow.exe and thus triggers ZAP.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Bookmarks

Posting Permissions

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