MrSmite

[HowTo] Patch from 3.3.5.12340 to 4.3.4.15595 (UPDATED 2014-01-24)

210 posts in this topic

2014-01-24

  • Clarify the "before you start" section to account for clients copied to new machines
  • Clarify how to check the Launcher version
  • Clarify when to run backgrounddownloader.exe
  • Fixed some typos, missed some typos and probably even made more typos

 

Update history:

2013-10-16 - Some people have mentioned that the 6 part wow-4.2.2.14545-to-4.3.0.15005 patch is corrupt however I just downloaded and extracted it successfully. Please try disabling download managers or try a different browser if you have trouble extracting it.

 

2013-08-08 - Guide revised, replaced some links with newer versions

 

I've put the guide in the spoiler below since it involves a LOT of downloading (approx. 20 to 25 GB), I thought I'd caution you first so you can decide if you want to find alternate means.

This guide will help you patch your enUS PC client from 3.3.5.12340 to 4.3.4.15595.

For enGB PC users, the process is the same. Sorry, I don't have your specific patches but you can check wowwiki, wowpedia or patches scrolls for them.

If you're a MAC user, I'm not sure what your patching process is like but you can check Blizzard's macgamefiles patch list on the official forums.


Step 1: Download prerequisite files

I've uploaded these files which will help as you install patches.
Download them and set them aside for now.

TFIL collection v2 - Used to check for additional data. Ignore the ones that come with any patches.
wow-4.x-base_win-enUS - Required for manually applying patches
wow-4.x-tools_updaters-enUS v2 - Required for manually applying patches

wow_cata_win-final_collection-enUS - A collection of "wow-0-xxxxx-Win-final.MPQ" in case a 3rd
party patch is missing them. These are needed to apply patches using commands or scripts.
Only download this if you find a patch doesn't meet any of the following criteria:

  • Has an EXE
  • Has a wow-patch.mpq
  • Has a wow-0-xxxxx-Win-final.MPQ

Step 2: Download the patches

In the spoiler tag is a master list of the patches you will need.
Download them and set them aside for now. The downloads total approx. 11 GB

Note:

Patches that say "by MrSmite" contain a detailed readme and script. You might want
to review them before applying the other patches since it can be adapted...


wow-3.3.x-to-4.0.0.12911 - Skip this if you have a Cata DVD

Don't worry that the above patch actually says "3.3.0.10958-4.0.0.12911", Blizzard at one point recommended patching up to 3.3.5.12340 before applying this patch anyway.

wow-4.0.0.12911-to-4.0.1.13164
wow-4.0.1.13164-to-4.0.1.13205
wow-4.0.1.13205-to-4.0.3.13287
wow-4.0.3.13287-to-4.0.3.13329
wow-4.0.3.13329-to-4.0.6.13596
wow-4.0.6.13596-to-4.0.6.13623
wow-4.0.6.13623-to-4.1.0.13914
wow-4.1.0.13914-to-4.1.0.14007
wow-4.1.0.14007-to-4.2.0.14333
wow-4.2.0.14333-to-4.2.0.14480
wow-4.2.0.14480-to-4.2.2.14545

wow-4.2.2.14545-to-4.3.0.15005 by MrSmite (~1.5 GB)

I had to split this into a multi-part ZIP file in order to upload. Since there is absolutely NO help on AG, I'm not able to link all the files in their descriptions so here's all 6 pieces:

Part 1 of 6, Part 2 of 6, Part 3 of 6, Part 4 of 6, Part 5 of 6, Part 6 of 6

Just put them all in the same folder and use 7-Zip, WinZip, WinRar or WhateverTheHell to unpack.

* Note: Some users have had trouble with 7-Zip. You can download a free UnRAR commandline utility from the WinRAR site if you need to.

wow-4.3.0.15005-to-4.3.0.15050 by MrSmite
wow-4.3.0.15050-to-4.3.2.15211 by MrSmite
wow-4.3.2.15211-to-4.3.3.15354 by MrSmite
wow-4.3.3.15354-to-4.3.4.15595 by MrSmite


 

Step 3: Install the patches

IMPORTANT: I can't stress this enough NEVER run Launcher.exe
IMPORTANT: I guess I have to remind people to block Blizzard's servers in their WTF too

This set of instructions should work for all the patches you've downloaded regardless of what instructions they came with. Take a minute to read them before you start and keep them handy for reference.

Patches uploaded by other people might be a bit confusing. Take a look at the "_instructions.txt" file in one of my patch archives for help.

Before you start:

  • If you have more than one installation make sure you run WoW.exe once to get the proper installation path in the registry or the patch might try to modify the wrong installation.
     
  • If you've copied your wow client to a new computer, make sure you run WoW.exe once to get the proper installation path in the registry or the patch won't be able to find your installation

 

  • Pre-Patching
    • Make a backup of your 3.3.5a client
    • Copy "base-Win" to the "Data" folder
    • Edit realmlist.wtf
      • change "realmlist" and "patchlist" to point anywhere but the official servers (127.0.0.1 is a good choice for now)
    • Edit or create launcher.wtf in the "WTF" folder
      • Make sure the contents are the following:
        • SET downloaderTags "EXP3,EXP2,EXP1,Win,enUS"


          SET expansionLevel "3"
          SET locale "enUS"
          SET downloadCompleted "0"
          SET patchApplicationCompleted "1"
          SET requiredCompleted "0"
          SET userspeed "1268770"
          SET accountType "CT"

      • Note: Check this file after each patch, some patches may delete or change it. Replace it if they do
  • Apply the patches in order

          * Note: If you have a Cata DVD then use that and skip wow-3.3.x-to-4.0.0.12911
    • Extract the patch archive to a temporary folder
    • Copy the patch contents to the appropriate folders in your WoW installation
      • If the patch contains an EXE, copy everything to the "Updates" folder
        • These (and only these) types of patches can be deleted when finished
      • If the patch contains a "wow-patch.MPQ" and a bunch of MPQ files, copy "wow-patch.MPQ" to the WoW root (overwriting) and copy the other MPQs to their appropriate folders (usually same folder structure as the archive)
         
      • If the patch contains a bunch of MPQ files without a "wow-patch.MPQ", put them in the appropriate folders (usually same folder structure as the archive)
        • Important: If this type of patch does not contan a "wow-0-xxxxx-Win-final.MPQ" (where xxxxx matches the patch revision) then you will need to download the collection at the top of the guide and extract it. Place this in the "Updates" folder.
    • Apply the patch

      See Notes section below if you get errors trying to apply the patch
      • If the patch contained an EXE, run the EXE
      • If the patch contained an update script (my uploads), run the script
      • If you have the "wow-patch.MPQ", just run "Blizzard Updater.exe"
      • If you have a file such as "wow-0-xxxxx-Win-final.MPQ" (where xxxxx matches the patch revision), run this from your WoW root:
         

        "Blizzard Updater.exe" --skippostlaunch=1 --patchlist="Updateswow-0-xxxxx-Win-final.MPQ"

        ** Replace xxxxx with the proper number for your patch

    • Run "BackgroundDownloader.exe" to see if there is additional patch info
      only after the following patches:

      wow-4.0.6.13596-to-4.0.6.13623
      wow-4.3.0.15050-to-4.3.2.15211
      wow-4.3.3.15354-to-4.3.4.15595
      • Make sure your tools are updated by checking "Launcher.exe" (right-click -> properties), the version should be 4.2.1.2756.
        Run the tools updater if it isn't (don't run the launcher)
      • Copy the MFIL / TFIL from the collection you downloaded to the WoW root
        • Overwrite any that came with the patches
      • Run "backgrounddownloader.exe"
        • The first two will download approx. 7 GB, the last approx. 4 GB
  • When finished, run WoW.exe (not Launcher.exe)
    • Follow the guide for setting up a server (make sure to compile the tools)
    • Edit "realmlist.wtf" and point "realmlist" and "patchlist" to your server's IP
    • Patch WoW.exe
      • This is required or you won't be able to log out, every NPC will be "Unknown" plus a host of other problems
    • Run WoW.exe (not Launcher.exe)
      • Allow it to connect to Blizzard's servers to check for additional data
      • Log in, create a character and enter the world
        • If it is downloading, there will be an arrow over the system menu button. This uses a slow UDP pulse so it may take several days. Just leave the client running.
    • The final client size after patching and optimizations performed when WoW.exe is first run is approx. 15.7 GB (confirmed by +CDawg who collaborated on the process)

Notes:

  • If at any time you have trouble installing a patch, you may need to do one or more of the following
    • Copy "base-Win" to the "Data" folder (this file sometimes gets corrupt) and try repatching
    • Update the tools (BackgroundDownloader, Blizzard Updater)
  • Oh, did I mention: IMPORTANT: I can't stress this enough NEVER run Launcher.exe
  • Oh, did I mention: IMPORTANT: I guess I have to remind people to block Blizzard's servers in their WTF too

---------------------------------- End of Guide ----------------------------------

Forum Mods:

You can close the following threads since they will be obsolete

http://www.trinityco...tion-available/
http://www.trinityco...2-10-23-334-pm/
http://www.trinityco...patches-where/

5

Share this post


Link to post
Share on other sites

Guide is finished (unless I think of something I missed).

Please add comments if you get stuck and the forums will notify me

or maybe someone who got it working will answer you.

Good Luck!

PS:

If you ran Launcher.exe and it patched you to 5.x then I can't help you. You'll

need to start over and remember:

IMPORTANT: I can't stress this enough NEVER run Launcher.exe

IMPORTANT: I guess I have to remind people to block Blizzard's servers in their WTF too

0

Share this post


Link to post
Share on other sites

Thank god there are torrentz =P

0

Share this post


Link to post
Share on other sites

Thank god there are torrentz =P

None of the enUS torrents have enough seeders to complete. This process isn't really that difficult anyway.

0

Share this post


Link to post
Share on other sites

it looks nice, but it is not a very good guide... my patching process is failing massively and the how-to is very hard to follow correctly... do not use this if you do not want to waste whole day and end up with nothing but corrupted files

you need to make a detailed step-by-step guide, not this "if it gets corrupted, try this and that and dance around the fire hoping it will help" one...

btw: the launcher.exe file is run by the patching process, so it gets kind of hard to "never run it"

0

Share this post


Link to post
Share on other sites

@cezeta

If you have a specific problem than ask about it otherwise please refrain from cluttering the topic with unconstructive posts like "it's bad, don't use it".

This, as far as I know, is the most concise guide around that actually results in a proper 4.3.4.15595.

PS:

Launcher.exe shouldn't be a problem because blizzard's servers should already be blocked (that's emulator 101). I only wrote that in the guide because people (probably you) were unblocking the servers and running Launcher.exe on purpose.

0

Share this post


Link to post
Share on other sites

I have blizz servers blocked in WTF, I also blocked launcher.exe in my firewall, so it can not reach internet... but it was the first thing that came to my mind, when I tried to use your how-to to upgrade my client...

and specific problem? well the most important problem is that your guide is very unspecific, some steps are missing or unclear and some are redundant...

for example:

wow-4.x-tools_updaters-enUS - Required for manually applying patches

-> when you install the first patch (wow-3.3.x-to-4.0.0.12911), these files are updated and none of these updaters can be run

another unclear thing is:

TFIL collection - Used to check for additional patch data after patching

- when to use these? what version when? is it neccesary, if there is this file included in the patch itself?

I tried to use the common sence, but after many hours I ended up with nothing but corrupted files and I can not imagine, that there will be someone, who will get this thing working using your guide, sorry.. there are too many unclear and possibly fatal places, where things can go wrong

0

Share this post


Link to post
Share on other sites

@cezeta

You clearly didn't read the entire guide first as I instructed. It looks like you just blundered right into it without preparing...

I have blizz servers blocked in WTF, I also blocked launcher.exe in my firewall, so it can not reach internet... but it was the first thing that came to my mind, when I tried to use your how-to to upgrade my client...

If you have the servers blocked then what's the problem? Even if Launcher.exe did run it can't download anything.

and specific problem? well the most important problem is that your guide is very unspecific, some steps are missing or unclear and some are redundant...

for example:

wow-4.x-tools_updaters-enUS - Required for manually applying patches

-> when you install the first patch (wow-3.3.x-to-4.0.0.12911), these files are updated and none of these updaters can be run

First off, the tools don't need to be updated every patch, only if a patch won't apply. Second, one of the tools is from patch wow-4.3.0.15005-to-4.3.0.15050 so it will work just fine if you use it only when a patch won't apply.

another unclear thing is:

TFIL collection - Used to check for additional patch data after patching

- when to use these? what version when? is it neccesary, if there is this file included in the patch itself?

How is this unclear? The guide specifically says when to copy the TFIL and run "BackgroundDownloader.exe"

I tried to use the common sence, but after many hours I ended up with nothing but corrupted files and I can not imagine, that there will be someone, who will get this thing working using your guide, sorry.. there are too many unclear and possibly fatal places, where things can go wrong

Common sense or not, I don't think you read the guide through before starting. If you did, your issues would've been addressed. Seeing as I've received comments from others that have had success I don't think it's an issue with the guide.

0

Share this post


Link to post
Share on other sites

@MrSmite, maybe update the guide with, "make a copy of your wow 3.3.5a client first...

That way when someone doesn't read your guide all the way through (won't mention names) they will have a backup.

lolz.

BTW, Good guide :)

Also, I made a copy of my current client (3.3.5) and renamed it (bcuz I still love my Wrath), so that way when I update to 4.x I have a 3.3.5 client as well. ;) Once the installation is done, renaming the client directory will 'un-link' the registry in Windows. (If the install was from scratch)

0

Share this post


Link to post
Share on other sites

@MrSmite, maybe update the guide with, "make a copy of your wow 3.3.5a client first...

That way when someone doesn't read your guide all the way through (won't mention names) they will have a backup.

lolz.

BTW, Good guide :)

Thanks. Ony problem with doing that is I'll end up changing it every day for all the repack kids that don't take time to follow directions. IMO there is plenty of warning already.

Also, I made a copy of my current client (3.3.5) and renamed it (bcuz I still love my Wrath), so that way when I update to 4.x I have a 3.3.5 client as well. ;) Once the installation is done, renaming the client directory will 'un-link' the registry in Windows. (If the install was from scratch)

Yes, indeed. I simply name mine based on the expansion: wow_exp02, wow_exp03...

The only catch is there is only one "WoW.exe" in the registry and the updater looks for that so it matters which one you've run last as to which path gets saved.

0

Share this post


Link to post
Share on other sites

You clearly didn't read the entire guide first as I instructed. It looks like you just blundered right into it without preparing...

This is not true, I have read it multiple times. It may surprise you, but I am not that stupid :-D

If you have the servers blocked then what's the problem? Even if Launcher.exe did run it can't download anything.

This was more a suggestion, what you should add to your guide, for others... person, who never updated wow manualy, will probably not know, that the launcher is executed automaticaly by the patch itself.

How is this unclear? The guide specifically says when to copy the TFIL and run "BackgroundDownloader.exe"

Today I made another attempt to update my client to Cata... and I did this so far:

1) I made a copy of my enUS PC 3.3.5.12340 client

1a) I emptied folders Cache, Logs, Screenshots, WTF and all nonblizz addon folders in Interface/Addons

1b) I started the game using wow.exe so the data path in registers would be updated

1c) I blocked access to internet for file Launcher.exe in my firewall

1d) My DataenUSrealmlist.wtf file contains only "set realmlist my.random_free_server.org"

2) I downloaded and unpacked TFIL collection, base_win, tools_updaters and all the patches

3) I executed wow-3.3.x-to-4.0.0.12911WoW-x.x.x.x-4.0.0.12911-Updater.exe

according to your guide, now I should:

copy the TFIL for the patch to your WoW root

-> but there is no TFIL for this patch

-> besides, when I now (client now should be 4.0.0.12911) try to run wow.exe, I get this error

==============================================================================

World of WarCraft: Retail Build (build 12911)

Exe: D:World of Warcraft WoTLK_2WoW.exe

Time: Nov 2, 2012 3:31:52.544 PM

User: Cezeta

Computer: CEZETA-PC

------------------------------------------------------------------------------

This application has encountered a critical error:

Systém nemůže nalézt uvedený soubor.

Program: D:World of Warcraft WoTLK_2WoW.exe

File: .Client.cpp

Line: 3578

file: signaturefile

WoWBuild: 12911

Settings:

SET locale "enUS"

SET realmList "us.logon.worldofwarcraft.com"

------------------------------------------------------------------------------

----------------------------------------

Stack Trace (Manual)

----------------------------------------

Address Frame Logical addr Module

Showing 15/15 threads...

--- Thread ID: 27200 [Current Thread] ---

01324D24 0060F318 0001:003A3D24 D:World of Warcraft WoTLK_2WoW.exe

00F827A5 0060F354 0001:000017A5 D:World of Warcraft WoTLK_2WoW.exe

00F86483 0060F7D4 0001:00005483 D:World of Warcraft WoTLK_2WoW.exe

00F86C97 0060FA20 0001:00005C97 D:World of Warcraft WoTLK_2WoW.exe

00F87069 0060FA30 0001:00006069 D:World of Warcraft WoTLK_2WoW.exe

00F870C8 0060FAC4 0001:000060C8 D:World of Warcraft WoTLK_2WoW.exe

754933AA 0060FAD0 0001:000033AA C:Windowssyswow64kernel32.dll

77119EF2 0060FB10 0001:00029EF2 C:WindowsSysWOW64ntdll.dll

77119EC5 0060FB28 0001:00029EC5 C:WindowsSysWOW64ntdll.dll

--- Thread ID: 28848 ---

74576D30 0388F54C 0001:00005D30 C:Windowssystem32mswsock.dll

75056A28 0388F5CC 0001:00005A28 C:Windowssyswow64WS2_32.dll

749736F3 0388F930 0001:000326F3 C:Windowssyswow64WININET.dll

7497CCBB 0388F938 0001:0003BCBB C:Windowssyswow64WININET.dll

754933AA 0388F944 0001:000033AA C:Windowssyswow64kernel32.dll

77119EF2 0388F984 0001:00029EF2 C:WindowsSysWOW64ntdll.dll

77119EC5 0388F99C 0001:00029EC5 C:WindowsSysWOW64ntdll.dll

--- Thread ID: 33000 ---

754933AA 03B2F7CC 0001:000033AA C:Windowssyswow64kernel32.dll

77119EF2 03B2F80C 0001:00029EF2 C:WindowsSysWOW64ntdll.dll

77119EC5 03B2F824 0001:00029EC5 C:WindowsSysWOW64ntdll.dll

--- Thread ID: 40160 ---

754933AA 03D2F7AC 0001:000033AA C:Windowssyswow64kernel32.dll

77119EF2 03D2F7EC 0001:00029EF2 C:WindowsSysWOW64ntdll.dll

77119EC5 03D2F804 0001:00029EC5 C:WindowsSysWOW64ntdll.dll

--- Thread ID: 32148 ---

754933AA 040FFCE4 0001:000033AA C:Windowssyswow64kernel32.dll

77119EF2 040FFD24 0001:00029EF2 C:WindowsSysWOW64ntdll.dll

77119EC5 040FFD3C 0001:00029EC5 C:WindowsSysWOW64ntdll.dll

--- Thread ID: 32364 ---

75491194 0446FB4C 0001:00001194 C:Windowssyswow64kernel32.dll

732133B7 0446FBB0 0001:000023B7 C:Windowssystem32rasman.dll

754933AA 0446FBBC 0001:000033AA C:Windowssyswow64kernel32.dll

77119EF2 0446FBFC 0001:00029EF2 C:WindowsSysWOW64ntdll.dll

77119EC5 0446FC14 0001:00029EC5 C:WindowsSysWOW64ntdll.dll

--- Thread ID: 33376 ---

754933AA 0476F878 0001:000033AA C:Windowssyswow64kernel32.dll

77119EF2 0476F8B8 0001:00029EF2 C:WindowsSysWOW64ntdll.dll

77119EC5 0476F8D0 0001:00029EC5 C:WindowsSysWOW64ntdll.dll

--- Thread ID: 30176 ---

754933AA 04A1F8C8 0001:000033AA C:Windowssyswow64kernel32.dll

77119EF2 04A1F908 0001:00029EF2 C:WindowsSysWOW64ntdll.dll

77119EC5 04A1F920 0001:00029EC5 C:WindowsSysWOW64ntdll.dll

--- Thread ID: 8212 ---

75491194 04EFF6C4 0001:00001194 C:Windowssyswow64kernel32.dll

75491148 04EFF6D8 0001:00001148 C:Windowssyswow64kernel32.dll

7496C964 04EFF6F8 0001:0002B964 C:Windowssyswow64WININET.dll

7496C8BE 04EFF714 0001:0002B8BE C:Windowssyswow64WININET.dll

7496C825 04EFF74C 0001:0002B825 C:Windowssyswow64WININET.dll

7496C73B 04EFF900 0001:0002B73B C:Windowssyswow64WININET.dll

7496C63E 04EFF90C 0001:0002B63E C:Windowssyswow64WININET.dll

754933AA 04EFF918 0001:000033AA C:Windowssyswow64kernel32.dll

77119EF2 04EFF958 0001:00029EF2 C:WindowsSysWOW64ntdll.dll

77119EC5 04EFF970 0001:00029EC5 C:WindowsSysWOW64ntdll.dll

--- Thread ID: 46452 ---

754933AA 051BFB08 0001:000033AA C:Windowssyswow64kernel32.dll

77119EF2 051BFB48 0001:00029EF2 C:WindowsSysWOW64ntdll.dll

77119EC5 051BFB60 0001:00029EC5 C:WindowsSysWOW64ntdll.dll

--- Thread ID: 33788 ---

75491194 0542F7C0 0001:00001194 C:Windowssyswow64kernel32.dll

75491148 0542F7D4 0001:00001148 C:Windowssyswow64kernel32.dll

0128F970 0542F80C 0001:0030E970 D:World of Warcraft WoTLK_2WoW.exe

0129354A 0542F820 0001:0031254A D:World of Warcraft WoTLK_2WoW.exe

0148D7FE 0542F858 0001:0050C7FE D:World of Warcraft WoTLK_2WoW.exe

0148D8A6 0542F864 0001:0050C8A6 D:World of Warcraft WoTLK_2WoW.exe

754933AA 0542F870 0001:000033AA C:Windowssyswow64kernel32.dll

77119EF2 0542F8B0 0001:00029EF2 C:WindowsSysWOW64ntdll.dll

77119EC5 0542F8C8 0001:00029EC5 C:WindowsSysWOW64ntdll.dll

--- Thread ID: 32144 ---

75491194 057DFAE8 0001:00001194 C:Windowssyswow64kernel32.dll

75491148 057DFAFC 0001:00001148 C:Windowssyswow64kernel32.dll

0128A3FE 057DFB28 0001:003093FE D:World of Warcraft WoTLK_2WoW.exe

0129354A 057DFB3C 0001:0031254A D:World of Warcraft WoTLK_2WoW.exe

0148D7FE 057DFB74 0001:0050C7FE D:World of Warcraft WoTLK_2WoW.exe

0148D8A6 057DFB80 0001:0050C8A6 D:World of Warcraft WoTLK_2WoW.exe

754933AA 057DFB8C 0001:000033AA C:Windowssyswow64kernel32.dll

77119EF2 057DFBCC 0001:00029EF2 C:WindowsSysWOW64ntdll.dll

77119EC5 057DFBE4 0001:00029EC5 C:WindowsSysWOW64ntdll.dll

--- Thread ID: 32784 ---

75491194 05A5FCB8 0001:00001194 C:Windowssyswow64kernel32.dll

75491148 05A5FCCC 0001:00001148 C:Windowssyswow64kernel32.dll

0129E536 05A5FD08 0001:0031D536 D:World of Warcraft WoTLK_2WoW.exe

0129354A 05A5FD1C 0001:0031254A D:World of Warcraft WoTLK_2WoW.exe

0148D7FE 05A5FD54 0001:0050C7FE D:World of Warcraft WoTLK_2WoW.exe

0148D8A6 05A5FD60 0001:0050C8A6 D:World of Warcraft WoTLK_2WoW.exe

754933AA 05A5FD6C 0001:000033AA C:Windowssyswow64kernel32.dll

77119EF2 05A5FDAC 0001:00029EF2 C:WindowsSysWOW64ntdll.dll

77119EC5 05A5FDC4 0001:00029EC5 C:WindowsSysWOW64ntdll.dll

--- Thread ID: 12256 ---

75491194 05D3F78C 0001:00001194 C:Windowssyswow64kernel32.dll

75491148 05D3F7A0 0001:00001148 C:Windowssyswow64kernel32.dll

0129E536 05D3F7DC 0001:0031D536 D:World of Warcraft WoTLK_2WoW.exe

0129354A 05D3F7F0 0001:0031254A D:World of Warcraft WoTLK_2WoW.exe

0148D7FE 05D3F828 0001:0050C7FE D:World of Warcraft WoTLK_2WoW.exe

0148D8A6 05D3F834 0001:0050C8A6 D:World of Warcraft WoTLK_2WoW.exe

754933AA 05D3F840 0001:000033AA C:Windowssyswow64kernel32.dll

77119EF2 05D3F880 0001:00029EF2 C:WindowsSysWOW64ntdll.dll

77119EC5 05D3F898 0001:00029EC5 C:WindowsSysWOW64ntdll.dll

--- Thread ID: 23464 ---

75491194 05F5F874 0001:00001194 C:Windowssyswow64kernel32.dll

75491148 05F5F888 0001:00001148 C:Windowssyswow64kernel32.dll

0128F849 05F5F8BC 0001:0030E849 D:World of Warcraft WoTLK_2WoW.exe

0129354A 05F5F8D0 0001:0031254A D:World of Warcraft WoTLK_2WoW.exe

0148D7FE 05F5F908 0001:0050C7FE D:World of Warcraft WoTLK_2WoW.exe

0148D8A6 05F5F914 0001:0050C8A6 D:World of Warcraft WoTLK_2WoW.exe

754933AA 05F5F920 0001:000033AA C:Windowssyswow64kernel32.dll

77119EF2 05F5F960 0001:00029EF2 C:WindowsSysWOW64ntdll.dll

77119EC5 05F5F978 0001:00029EC5 C:WindowsSysWOW64ntdll.dll

----------------------------------------

Stack Trace (Using DBGHELP.DLL)

----------------------------------------

Showing 15/15 threads...

--- Thread ID: 27200 [Current Thread] ---

--- Thread ID: 28848 ---

74576D30 mswsock.dll <unknown symbol>+0 (0x00000001,0x0388F828,0x0388F724,0x0388F620)

75056A28 WS2_32.dll select+159 (0x00000001,0x0388F828,0x0388F724,0x0388F620)

749736F3 WININET.dll InternetCrackUrlW+1690 (0x0388F944,0x754933AA,0x007BCCC8,0x0388F984)

7497CCBB WININET.dll InternetSetStatusCallback+1297 (0x007BCCC8,0x0388F984,0x77119EF2,0x007BCCC8)

754933AA kernel32.dll BaseThreadInitThunk+18 (0x007BCCC8,0x63ACC360,0x00000000,0x00000000)

77119EF2 ntdll.dll RtlInitializeExceptionChain+99 (0x7497CCAE,0x007BCCC8,0x00000000,0x00000000)

77119EC5 ntdll.dll RtlInitializeExceptionChain+54 (0x7497CCAE,0x007BCCC8,0x00000000,0x00000000)

--- Thread ID: 33000 ---

754933AA kernel32.dll BaseThreadInitThunk+18 (0x007D2F18,0x6396C2E8,0x00000000,0x00000000)

77119EF2 ntdll.dll RtlInitializeExceptionChain+99 (0x77132E25,0x007D2F18,0x00000000,0x00000000)

77119EC5 ntdll.dll RtlInitializeExceptionChain+54 (0x77132E25,0x007D2F18,0x00000000,0x00000000)

--- Thread ID: 40160 ---

754933AA kernel32.dll BaseThreadInitThunk+18 (0x007D2150,0x63F6CD08,0x00000000,0x00000000)

77119EF2 ntdll.dll RtlInitializeExceptionChain+99 (0x77133E45,0x007D2150,0x00000000,0x00000000)

77119EC5 ntdll.dll RtlInitializeExceptionChain+54 (0x77133E45,0x007D2150,0x00000000,0x00000000)

--- Thread ID: 32148 ---

754933AA kernel32.dll BaseThreadInitThunk+18 (0x007D2150,0x642BC7C0,0x00000000,0x00000000)

77119EF2 ntdll.dll RtlInitializeExceptionChain+99 (0x77133E45,0x007D2150,0x00000000,0x00000000)

77119EC5 ntdll.dll RtlInitializeExceptionChain+54 (0x77133E45,0x007D2150,0x00000000,0x00000000)

--- Thread ID: 32364 ---

75491194 kernel32.dll WaitForSingleObjectEx+67 (0x000022DC,0xFFFFFFFF,0x00000001,0x00000000)

732133B7 rasman.dll RasAddNotification+1088 (0x00000000,0x0446FBFC,0x77119EF2,0x00000000)

754933AA kernel32.dll BaseThreadInitThunk+18 (0x00000000,0x6462C118,0x00000000,0x00000000)

77119EF2 ntdll.dll RtlInitializeExceptionChain+99 (0x732132FB,0x00000000,0x00000000,0x00000000)

77119EC5 ntdll.dll RtlInitializeExceptionChain+54 (0x732132FB,0x00000000,0x00000000,0x00000000)

--- Thread ID: 33376 ---

754933AA kernel32.dll BaseThreadInitThunk+18 (0x007E6B78,0x6452C25C,0x00000000,0x00000000)

77119EF2 ntdll.dll RtlInitializeExceptionChain+99 (0x77133E45,0x007E6B78,0x00000000,0x00000000)

77119EC5 ntdll.dll RtlInitializeExceptionChain+54 (0x77133E45,0x007E6B78,0x00000000,0x00000000)

--- Thread ID: 30176 ---

754933AA kernel32.dll BaseThreadInitThunk+18 (0x007E6B78,0x6485C3EC,0x00000000,0x00000000)

77119EF2 ntdll.dll RtlInitializeExceptionChain+99 (0x77133E45,0x007E6B78,0x00000000,0x00000000)

77119EC5 ntdll.dll RtlInitializeExceptionChain+54 (0x77133E45,0x007E6B78,0x00000000,0x00000000)

--- Thread ID: 8212 ---

75491194 kernel32.dll WaitForSingleObjectEx+67 (0x00002374,0x00002710,0x00000000,0x04EFF6F8)

75491148 kernel32.dll WaitForSingleObject+18 (0x00002374,0x00002710,0x007CD200,0x00002710)

7496C964 WININET.dll Ordinal101+30013 (0x007CD200,0x00002710,0x80070490,0x007C8F90)

7496C8BE WININET.dll Ordinal101+29847 (0x007CD200,0x04EFF730,0x00000000,0x007CD200)

7496C825 WININET.dll Ordinal101+29694 (0x007CD200,0x00000000,0x00000000,0x007CD200)

7496C73B WININET.dll Ordinal101+29460 (0x007CD200,0x04EFF918,0x754933AA,0x007CD200)

7496C63E WININET.dll Ordinal101+29207 (0x007CD200,0x04EFF958,0x77119EF2,0x007CD200)

754933AA kernel32.dll BaseThreadInitThunk+18 (0x007CD200,0x64CBC3BC,0x00000000,0x00000000)

77119EF2 ntdll.dll RtlInitializeExceptionChain+99 (0x7496C631,0x007CD200,0x00000000,0x00000000)

77119EC5 ntdll.dll RtlInitializeExceptionChain+54 (0x7496C631,0x007CD200,0x00000000,0x00000000)

--- Thread ID: 46452 ---

754933AA kernel32.dll BaseThreadInitThunk+18 (0x007D6488,0x653FC1AC,0x00000000,0x00000000)

77119EF2 ntdll.dll RtlInitializeExceptionChain+99 (0x745762EE,0x007D6488,0x00000000,0x00000000)

77119EC5 ntdll.dll RtlInitializeExceptionChain+54 (0x745762EE,0x007D6488,0x00000000,0x00000000)

--- Thread ID: 33788 ---

75491194 kernel32.dll WaitForSingleObjectEx+67 (0x000023C8,0xFFFFFFFF,0x00000000,0x0542F80C)

75491148 kernel32.dll WaitForSingleObject+18 (0x000023C8,0xFFFFFFFF,0x02FA8AB0,0x00000000)

0128F970 WoW.exe GetBattlenetAllocator+903472 (0x02FA8050,0x00000000,0x02FA8AB0,0x0542F858)

0129354A WoW.exe GetBattlenetAllocator+918794 (0x02FA8A48,0xCFEB7B0F,0x00000000,0x02FA8AB0)

0148D7FE WoW.exe GetBattlenetAllocator+2992062 (0x00000000,0x0542F870,0x754933AA,0x02FA8AB0)

0148D8A6 WoW.exe GetBattlenetAllocator+2992230 (0x02FA8AB0,0x0542F8B0,0x77119EF2,0x02FA8AB0)

754933AA kernel32.dll BaseThreadInitThunk+18 (0x02FA8AB0,0x6566C254,0x00000000,0x00000000)

77119EF2 ntdll.dll RtlInitializeExceptionChain+99 (0x0148D824,0x02FA8AB0,0x00000000,0x00000000)

77119EC5 ntdll.dll RtlInitializeExceptionChain+54 (0x0148D824,0x02FA8AB0,0x00000000,0x00000000)

--- Thread ID: 32144 ---

75491194 kernel32.dll WaitForSingleObjectEx+67 (0x00002168,0xFFFFFFFF,0x00000000,0x057DFB28)

75491148 kernel32.dll WaitForSingleObject+18 (0x00002168,0xFFFFFFFF,0x00000000,0x02FA8548)

0128A3FE WoW.exe GetBattlenetAllocator+881598 (0x00000000,0x00000000,0x02FEFBE8,0x057DFB74)

0129354A WoW.exe GetBattlenetAllocator+918794 (0x02FA8548,0xCFD47823,0x00000000,0x02FEFBE8)

0148D7FE WoW.exe GetBattlenetAllocator+2992062 (0x00000000,0x057DFB8C,0x754933AA,0x02FEFBE8)

0148D8A6 WoW.exe GetBattlenetAllocator+2992230 (0x02FEFBE8,0x057DFBCC,0x77119EF2,0x02FEFBE8)

754933AA kernel32.dll BaseThreadInitThunk+18 (0x02FEFBE8,0x6559C128,0x00000000,0x00000000)

77119EF2 ntdll.dll RtlInitializeExceptionChain+99 (0x0148D824,0x02FEFBE8,0x00000000,0x00000000)

77119EC5 ntdll.dll RtlInitializeExceptionChain+54 (0x0148D824,0x02FEFBE8,0x00000000,0x00000000)

--- Thread ID: 32784 ---

75491194 kernel32.dll WaitForSingleObjectEx+67 (0x00002170,0x00000064,0x00000000,0x05A5FD08)

75491148 kernel32.dll WaitForSingleObject+18 (0x00002170,0x00000064,0x00000000,0x02FEDA30)

0129E536 WoW.exe GetBattlenetAllocator+963830 (0x00FE9340,0x00000000,0x02FC27E8,0x05A5FD54)

0129354A WoW.exe GetBattlenetAllocator+918794 (0x02FEDA30,0xCF0C7E03,0x00000000,0x02FC27E8)

0148D7FE WoW.exe GetBattlenetAllocator+2992062 (0x00000000,0x05A5FD6C,0x754933AA,0x02FC27E8)

0148D8A6 WoW.exe GetBattlenetAllocator+2992230 (0x02FC27E8,0x05A5FDAC,0x77119EF2,0x02FC27E8)

754933AA kernel32.dll BaseThreadInitThunk+18 (0x02FC27E8,0x6581C748,0x00000000,0x00000000)

77119EF2 ntdll.dll RtlInitializeExceptionChain+99 (0x0148D824,0x02FC27E8,0x00000000,0x00000000)

77119EC5 ntdll.dll RtlInitializeExceptionChain+54 (0x0148D824,0x02FC27E8,0x00000000,0x00000000)

--- Thread ID: 12256 ---

75491194 kernel32.dll WaitForSingleObjectEx+67 (0x00002170,0x00000064,0x00000000,0x05D3F7DC)

75491148 kernel32.dll WaitForSingleObject+18 (0x00002170,0x00000064,0x00000000,0x02FEDB38)

0129E536 WoW.exe GetBattlenetAllocator+963830 (0x00FE9350,0x00000000,0x02FC2A08,0x05D3F828)

0129354A WoW.exe GetBattlenetAllocator+918794 (0x02FEDB38,0xCF7A7B7F,0x00000000,0x02FC2A08)

0148D7FE WoW.exe GetBattlenetAllocator+2992062 (0x00000000,0x05D3F840,0x754933AA,0x02FC2A08)

0148D8A6 WoW.exe GetBattlenetAllocator+2992230 (0x02FC2A08,0x05D3F880,0x77119EF2,0x02FC2A08)

754933AA kernel32.dll BaseThreadInitThunk+18 (0x02FC2A08,0x65F7C264,0x00000000,0x00000000)

77119EF2 ntdll.dll RtlInitializeExceptionChain+99 (0x0148D824,0x02FC2A08,0x00000000,0x00000000)

77119EC5 ntdll.dll RtlInitializeExceptionChain+54 (0x0148D824,0x02FC2A08,0x00000000,0x00000000)

--- Thread ID: 23464 ---

75491194 kernel32.dll WaitForSingleObjectEx+67 (0x000023EC,0xFFFFFFFF,0x00000000,0x05F5F8BC)

75491148 kernel32.dll WaitForSingleObject+18 (0x000023EC,0xFFFFFFFF,0x00000000,0x02FEFE08)

0128F849 WoW.exe GetBattlenetAllocator+903177 (0x02FC1EB8,0x00000000,0x02FC2C28,0x05F5F908)

0129354A WoW.exe GetBattlenetAllocator+918794 (0x02FEFE08,0xCF5C7A5F,0x00000000,0x02FC2C28)

0148D7FE WoW.exe GetBattlenetAllocator+2992062 (0x00000000,0x05F5F920,0x754933AA,0x02FC2C28)

0148D8A6 WoW.exe GetBattlenetAllocator+2992230 (0x02FC2C28,0x05F5F960,0x77119EF2,0x02FC2C28)

754933AA kernel32.dll BaseThreadInitThunk+18 (0x02FC2C28,0x65D1C384,0x00000000,0x00000000)

77119EF2 ntdll.dll RtlInitializeExceptionChain+99 (0x0148D824,0x02FC2C28,0x00000000,0x00000000)

77119EC5 ntdll.dll RtlInitializeExceptionChain+54 (0x0148D824,0x02FC2C28,0x00000000,0x00000000)

----------------------------------------

Loaded Modules

----------------------------------------

DBG-MODULE<00F80000 00B26000 "WoW.exe" "Wow.pdb" 0 {c407bf58-93be-4be8-bb0f809865fcfd75} 1 1283470620>

DBG-MODULE<69CA0000 00084000 "COMCTL32.dll" "comctl32v582.pdb" 0 {ab2667ae-cefc-4ff9-aa74c3b9857bfa9a} 2 1290254380>

DBG-MODULE<6BF70000 001C3000 "d3d9.dll" "d3d9.pdb" 0 {f55aeb50-462b-473f-9733515dc6532daf} 2 1290254259>

DBG-MODULE<6CC80000 00115000 "dbghelp.dll" "dbghelp.pdb" 0 {a95a9676-9559-4b16-959820e93cb1abec} 1 1152389492>

DBG-MODULE<6D1A0000 00006000 "sensapi.dll" "SensApi.pdb" 0 {1f9bbfcb-f7a9-451b-89a51771ca4c47db} 2 1247533841>

DBG-MODULE<6D6B0000 0007B000 "AcSpecfc.DLL" "AcSpecfc.pdb" 0 {d581e4f3-6080-4ba2-a2171d69e729d632} 2 1247533441>

DBG-MODULE<6E320000 000E7000 "DDRAW.dll" "ddraw.pdb" 0 {497dbeef-b385-4f24-bc6a468137860ada} 2 1247533496>

DBG-MODULE<6E410000 000C8000 "OPENGL32.dll" "opengl32.pdb" 0 {d6a5e50a-cc5c-4af5-9ff7b7b387ca4a2a} 2 1247533787>

DBG-MODULE<6E8D0000 00014000 "MSACM32.dll" "msacm32.pdb" 0 {3d318d5e-38c5-4502-b64578f0710a510f} 2 1247533646>

DBG-MODULE<6EB80000 00022000 "GLU32.dll" "glu32.pdb" 0 {2c6b6170-dfa8-4c3e-8ce7ef5d4408ce74} 2 1247533535>

DBG-MODULE<6ECA0000 00030000 "DINPUT8.dll" "dinput8.pdb" 0 {ca86b91a-9619-4907-8e07314413ffe1dd} 2 1247533505>

DBG-MODULE<70350000 00009000 "HID.DLL" "hid.pdb" 0 {015645ef-10de-49b0-84ee745a3fdc0f8d} 2 1247533548>

DBG-MODULE<704F0000 00013000 "dwmapi.dll" "dwmapi.pdb" 0 {d8d91b3f-339a-4fdc-960fc7121d146df4} 2 1247533575>

DBG-MODULE<71AC0000 0001B000 "AUTHZ.dll" "authz.pdb" 0 {2d43c270-b407-466c-8b640ee17bf00012} 2 1247533452>

DBG-MODULE<71AE0000 00025000 "peerdist.dll" "peerdist.pdb" 0 {71032826-7640-4af4-8567ee4df4a88bc3} 1 1247533772>

DBG-MODULE<726D0000 00006000 "d3d8thk.dll" "d3d8thk.pdb" 0 {d9c3a335-615f-448e-a0b012d76716e6b7} 2 1247533480>

DBG-MODULE<72700000 00006000 "DCIMAN32.dll" "dciman32.pdb" 0 {f1c0c4b3-249c-4aaa-8a5130d41835b365} 2 1247533492>

DBG-MODULE<72720000 00079000 "mscms.dll" "mscms.pdb" 0 {93303cbc-777e-44a5-92376e1f326e2017} 2 1290254544>

DBG-MODULE<72950000 00038000 "fwpuclnt.dll" "fwpuclnt.pdb" 0 {eb7d55a5-3635-4ad9-87ce2e36914aaf37} 2 1290254386>

DBG-MODULE<72990000 00006000 "rasadhlp.dll" "rasadhlp.pdb" 0 {9c177d0e-6fd1-4d28-bae05d9757e8182f} 2 1247533782>

DBG-MODULE<72BE0000 0004C000 "apphelp.dll" "apphelp.pdb" 0 {f442bedc-c0f6-46d3-840d29898c5899cb} 2 1290254142>

DBG-MODULE<72FD0000 00240000 "msi.dll" "msi.pdb" 0 {c2bd5404-106a-411e-83151b5ec2468c16} 2 1333797524>

DBG-MODULE<73210000 00015000 "rasman.dll" "rasman.pdb" 0 {df9a8608-77f9-4fec-bb7a2cf29c7d5edd} 2 1247533791>

DBG-MODULE<73230000 00052000 "RASAPI32.dll" "rasapi32.pdb" 0 {b6e3857a-947f-4f9e-86d6c3a36576bf15} 2 1247533783>

DBG-MODULE<73290000 00005000 "wshtcpip.dll" "wshtcpip.pdb" 0 {92a92ff2-9357-4b48-9795898561f00719} 2 1247533914>

DBG-MODULE<732A0000 00006000 "wship6.dll" "wship6.pdb" 0 {02e45101-e951-429f-85676adfcc0ea72a} 2 1247533910>

DBG-MODULE<73340000 00010000 "NLAapi.dll" "nlaapi.pdb" 0 {4c9854c4-89d7-4a7f-97b24d70fac99cf3} 2 1290254607>

DBG-MODULE<73480000 00044000 "dnsapi.DLL" "dnsapi.pdb" 0 {4b77ba91-498a-432f-8dd6e52085c4c423} 2 1299130163>

DBG-MODULE<734E0000 00032000 "WINMM.dll" "winmm.pdb" 0 {7afd98fc-aad3-4f6b-8b31a4667c4e2bfc} 2 1290254914>

DBG-MODULE<740F0000 00008000 "Secur32.dll" "secur32.pdb" 0 {8ef4e863-187c-45e7-8f4632152cc82feb} 2 1345827150>

DBG-MODULE<742D0000 00007000 "WINNSI.DLL" "winnsi.pdb" 0 {f7a0c25b-1b0e-4fa6-876494d3f6bfd101} 2 1247533891>

DBG-MODULE<742E0000 0001C000 "iphlpapi.DLL" "iphlpapi.pdb" 0 {f162d2e1-37ed-4297-8bf38c99aee2daab} 2 1290254425>

DBG-MODULE<74390000 0019E000 "comctl32.dll" "comctl32.pdb" 0 {b4ce90aa-b95e-4b89-a22a7711dfd7e6ef} 2 1290254108>

DBG-MODULE<74530000 00012000 "MPR.dll" "mpr.pdb" 0 {1408743d-4222-4025-a49e02a79ce7190a} 2 1247533622>

DBG-MODULE<74550000 00009000 "VERSION.dll" "version.pdb" 0 {52234e5c-7ec4-4646-b62d56357b2c9487} 2 1247533867>

DBG-MODULE<74570000 0003C000 "mswsock.dll" "mswsock.pdb" 0 {5d01bc6d-4da8-4939-baf8725d60d595a6} 2 1290254568>

DBG-MODULE<74670000 0000D000 "rtutils.dll" "rtutils.pdb" 0 {b7794699-4af6-4de6-b40cbffe6d34d049} 2 1290254764>

DBG-MODULE<746B0000 0000B000 "profapi.dll" "profapi.pdb" 0 {ca045ca9-e5c7-4d89-9b90e776b38a18b3} 2 1247526721>

DBG-MODULE<746C0000 00017000 "USERENV.dll" "userenv.pdb" 0 {fd47f512-75f8-4fca-aa6071cb11cc4ab8} 2 1290254888>

DBG-MODULE<747B0000 0000C000 "CRYPTBASE.dll" "cryptbase.pdb" 0 {e62feae5-59ee-4cd9-95614215b01ac210} 2 1247526721>

DBG-MODULE<747C0000 00060000 "SspiCli.dll" "wsspicli.pdb" 0 {c40594fd-ee2c-4889-84d245a514b2a513} 1 1345827215>

DBG-MODULE<74940000 0011B000 "WININET.dll" "wininet.pdb" 0 {2981adfd-0166-425e-9491a7e1ded84a94} 2 1345791078>

DBG-MODULE<74AF0000 000F0000 "RPCRT4.dll" "wrpcrt4.pdb" 0 {fac24015-130d-4d7f-aaa77ea36ed5af1c} 2 1290254937>

DBG-MODULE<74BE0000 00100000 "USER32.dll" "wuser32.pdb" 0 {0fce9cc3-01ed-4567-a819705b2718e1d6} 2 1290254937>

DBG-MODULE<74CE0000 000A0000 "ADVAPI32.dll" "advapi32.pdb" 0 {3f32049f-550c-42b0-9cf114a1fb8a97e9} 2 1290254086>

DBG-MODULE<74D80000 00111000 "urlmon.dll" "urlmon.pdb" 0 {07a0fd41-d759-4377-8f2fc7e009b2f924} 2 1345791106>

DBG-MODULE<74EA0000 000CC000 "MSCTF.dll" "msctf.pdb" 0 {173daef8-6b25-48db-a6134eb74c4d2f23} 2 1247533673>

DBG-MODULE<74F70000 00090000 "GDI32.dll" "wgdi32.pdb" 0 {08a541b5-9422-42bd-b4aeabd8c87e4cff} 2 1290254931>

DBG-MODULE<75050000 00035000 "WS2_32.dll" "ws2_32.pdb" 0 {18c960b9-5840-4c4f-80f686ee978a33d4} 2 1290254952>

DBG-MODULE<75120000 00047000 "KERNELBASE.dll" "wkernelbase.pdb" 0 {615fe84e-9611-4fe8-b63193c923e026f5} 1 1345484402>

DBG-MODULE<75170000 0019D000 "SETUPAPI.dll" "setupapi.pdb" 0 {c6b7cc38-0fcd-42c2-9edb1b61757dfd92} 2 1290254809>

DBG-MODULE<75310000 00027000 "CFGMGR32.dll" "cfgmgr32.pdb" 0 {e4c73e93-b825-413f-99e80ba656c48317} 2 1306232913>

DBG-MODULE<75340000 00006000 "NSI.dll" "nsi.pdb" 0 {d15a8167-9fae-4a73-92344b6fd2686794} 2 1247533785>

DBG-MODULE<753E0000 00012000 "DEVOBJ.dll" "devobj.pdb" 0 {583f4457-964d-46ca-8c36ed4903be6aa2} 2 1306232957>

DBG-MODULE<75400000 0007B000 "COMDLG32.dll" "comdlg32.pdb" 0 {96bc483c-dff0-4d1a-afe462f093b954ec} 2 1290254381>

DBG-MODULE<75480000 00110000 "kernel32.dll" "wkernel32.pdb" 0 {e1c01974-da97-4a69-9700cc37cd94a920} 2 1345484401>

DBG-MODULE<75590000 00060000 "IMM32.dll" "wimm32.pdb" 0 {35dd4069-eb2a-43bf-869d6e311fad0945} 2 1290254931>

DBG-MODULE<755F0000 001B8000 "iertutil.dll" "iertutil.pdb" 0 {8e10dab3-8995-403d-902896a88b847fd0} 2 1345790666>

DBG-MODULE<757B0000 00003000 "Normaliz.dll" "normaliz.pdb" 0 {9481804b-b4fd-4703-ae6ae76f8b99b476} 1 1247533780>

DBG-MODULE<757C0000 0015C000 "ole32.dll" "ole32.pdb" 0 {5061f11a-9a57-4335-95ea5ea75a156f4b} 2 1290254703>

DBG-MODULE<75930000 0000A000 "LPK.dll" "wlpk.pdb" 0 {c39166a5-3cce-43f0-adf876b9c637a1ea} 1 1247533883>

DBG-MODULE<75940000 0009D000 "USP10.dll" "usp10.pdb" 0 {f49786e2-c7c5-4ea9-9e7c37120cdaeb9c} 1 1290254889>

DBG-MODULE<75A10000 00C4A000 "SHELL32.dll" "shell32.pdb" 0 {1489bcd8-e80c-441e-91308a093631de5e} 2 1339216345>

DBG-MODULE<76660000 0008F000 "OLEAUT32.dll" "oleaut32.pdb" 0 {68047829-a475-4e78-9ac1c8035ba168cd} 2 1314418730>

DBG-MODULE<766F0000 00019000 "sechost.dll" "sechost.pdb" 0 {7af14d02-d41e-4cd6-942745fe0e6372b1} 1 1247533828>

DBG-MODULE<76710000 00057000 "SHLWAPI.dll" "shlwapi.pdb" 0 {e128b1ce-e2eb-438c-8646e6967118f33e} 2 1290254818>

DBG-MODULE<76770000 000AC000 "msvcrt.dll" "msvcrt.pdb" 0 {f1d253f9-555c-46df-8076400a52b3a929} 2 1324021538>

DBG-MODULE<770E0000 00180000 "ntdll.dll" "wntdll.pdb" 0 {d74f79eb-1f8d-4a45-abcd2f476ccabacc} 2 1321507727>

----------------------------------------

Memory Dump

----------------------------------------

Stack: 1024 bytes starting at (ESP = 0060EA9C)

* = addr ** *

0060EA90: 01 00 6E 00 36 10 33 01 9C EA 60 00 9C 69 64 01 ..n.6.3...`..id.

0060EAA0: 02 00 00 00 36 10 33 01 9C EA 60 00 B0 EA 60 00 ....6.3...`...`.

0060EAB0: D8 EA 60 00 6E 47 32 01 01 00 6E 00 70 3A 32 01 ..`.nG2...n.p:2.

0060EAC0: BC 24 00 00 03 00 00 00 00 00 00 00 30 2D 60 01 .$..........0-`.

0060EAD0: 00 01 00 00 FA 0D 00 00 04 F3 60 00 FD 4C 32 01 ..........`..L2.

0060EAE0: 02 00 00 00 30 2D 60 01 FA 0D 00 00 04 EB 60 00 ....0-`.......`.

0060EAF0: 00 00 00 00 01 00 00 00 11 11 11 11 00 00 00 00 ................

0060EB00: 10 00 FF 02 66 69 6C 65 3A 20 73 69 67 6E 61 74 ....file: signat

0060EB10: 75 72 65 66 69 6C 65 00 30 D0 55 06 30 D0 55 06 urefile.0.U.0.U.

0060EB20: 64 EB 60 00 E6 34 F9 00 00 00 FA 02 00 00 00 00 d.`..4..........

0060EB30: EF 34 F9 00 00 00 00 00 00 00 00 00 30 D0 55 06 .4..........0.U.

0060EB40: 0F 00 00 00 64 EB 60 00 6D 7A F9 00 34 EB 60 00 ....d.`.mz..4.`.

0060EB50: 00 00 00 00 7C EE 60 00 90 02 F9 00 BF EE C7 CB ....|.`.........

0060EB60: FE FF FF FF EF 34 F9 00 EF 15 32 01 30 D0 55 06 .....4....2.0.U.

0060EB70: 34 00 00 00 00 00 00 00 94 EB 60 00 E5 CB 48 01 4.........`...H.

0060EB80: 30 D0 55 06 E8 CF 55 06 34 00 00 00 34 00 00 00 0.U...U.4...4...

0060EB90: CC EE 60 00 B8 EB 60 00 CA 53 27 01 30 D0 55 06 ..`...`..S'.0.U.

0060EBA0: 3F 00 00 00 E8 CF 55 06 34 00 00 00 E8 EE 60 00 ?.....U.4.....`.

0060EBB0: CC EE 60 00 E8 EE 60 00 00 00 00 00 CC EE 60 00 ..`...`.......`.

0060EBC0: 88 EE 60 00 9D 18 29 01 CC DA 8A 01 20 EF 60 00 ..`...)..... .`.

0060EBD0: 50 F1 60 00 00 00 00 00 44 3A 2F 57 6F 72 6C 64 P.`.....D:/World

0060EBE0: 20 6F 66 20 57 61 72 63 72 61 66 74 20 57 6F 54 of Warcraft WoT

0060EBF0: 4C 4B 5F 32 2F 64 61 74 61 2F 65 6E 55 53 2F 72 LK_2/data/enUS/r

0060EC00: 65 61 6C 6D 6C 69 73 74 2E 77 74 66 00 00 00 00 ealmlist.wtf....

0060EC10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

0060EC20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

0060EC30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

0060EC40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

0060EC50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

0060EC60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

0060EC70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

0060EC80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

0060EC90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

0060ECA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

0060ECB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

0060ECC0: 00 00 00 00 00 00 00 00 78 EF 60 00 28 EE 60 00 ........x.`.(.`.

0060ECD0: 30 88 FC 02 00 00 00 00 30 88 FC 02 BC 30 26 01 0.......0....0&.

0060ECE0: 58 24 B5 84 00 00 00 00 00 00 00 00 01 00 00 00 X$..............

0060ECF0: B8 85 FC 02 61 6C 74 65 72 6E 61 74 65 5C 73 69 ....alternatesi

0060ED00: 67 6E 61 74 75 72 65 66 69 6C 65 00 08 D7 44 60 gnaturefile...D`

0060ED10: 00 00 00 00 00 00 FA 02 30 FB 55 06 46 E0 10 77 ........0.U.F..w

0060ED20: CC 01 FA 02 00 00 FA 02 00 00 FA 02 00 00 00 00 ................

0060ED30: 11 00 65 00 48 49 41 06 50 01 FA 02 64 61 74 61 ..e.HIA.P...data

0060ED40: 00 00 FA 02 50 01 FA 02 61 6C 6D 6C 69 73 74 2E ....P...almlist.

0060ED50: 50 01 FA 02 02 00 00 02 58 03 FB 02 15 00 00 15 P.......X.......

0060ED60: 11 00 00 00 20 00 00 00 00 00 00 00 03 00 00 00 .... ...........

0060ED70: 48 00 FB 02 11 00 00 00 15 00 00 00 B0 06 FB 02 H...............

0060ED80: 33 98 00 AB 11 00 00 00 1C ED 60 00 10 0F 5D 06 3.........`...].

0060ED90: D5 71 15 77 BC E8 34 17 FE FF FF FF 74 01 FA 02 .q.w..4.....t...

0060EDA0: 58 3F 41 06 A0 A3 00 06 65 08 00 00 B8 0B 5D 06 X?A.....e.....].

0060EDB0: 00 00 00 00 7F 54 00 00 71 99 60 00 F8 ED 60 00 .....T..q.`...`.

0060EDC0: 93 31 26 01 07 00 00 00 38 00 00 00 E8 ED 60 00 .1&.....8.....`.

0060EDD0: 08 00 00 00 78 EF 60 00 D8 22 41 06 50 25 41 06 ....x.`.."A.P%A.

0060EDE0: 8E 20 4C 77 8F 86 9E 00 59 DD 34 4E 85 D5 78 00 . Lw....Y.4N..x.

0060EDF0: 63 08 00 00 71 08 00 00 58 EF 60 00 A3 62 2A 01 c...q...X.`..b*.

0060EE00: 50 EF 60 C1 11 0C 00 00 10 97 8A 01 38 3F FA 02 P.`.........8?..

0060EE10: 73 69 67 6E 61 74 75 72 65 66 69 6C 65 00 61 74 signaturefile.at

0060EE20: 75 72 65 66 69 6C 65 00 00 00 FA 02 00 00 00 00 urefile.........

0060EE30: FE 34 60 01 00 00 00 00 00 00 00 00 00 00 00 00 .4`.............

0060EE40: BC 30 26 01 8F 86 9E C1 00 00 00 00 00 00 00 00 .0&.............

0060EE50: 01 00 00 00 F0 34 60 01 73 69 67 6E 61 74 75 72 .....4`.signatur

0060EE60: 65 66 69 6C 65 00 32 01 30 FB 55 06 30 FB 55 06 efile.2.0.U.0.U.

0060EE70: 30 FB 55 06 90 EE 60 00 5A DB 26 01 30 FB 55 06 0.U...`.Z.&.0.U.

0060EE80: 58 80 63 01 C6 01 00 00 00 00 00 00 30 FB 55 06 X.c.........0.U.

0060EE90: 50 EF 60 00 46 14 29 01 50 14 FA 02 60 EF 60 00 P.`.F.).P...`.`.

------------------------------------------------------------------------------

======================================================================

Hardware/Driver Information:

Processor: 0x9

Page Size: 4096

Min App Address: 0x10000

Max App Address: 0x7ffeffff

Processor Mask: 0x3

Number of Processors: 2

Processor Type: 8664

Allocation Granularity: 65536

Processor Level: 6

Processor Revision: 5894

Os Version: 6.1

Os Service Pack: 1.0

Percent memory used: 46

Total physical memory: 4294037504

Free Memory: 2284216320

Page file: 8586178560

Total virtual memory: 2147352576

Is it OK, that the client won't run? Should I finish installing all the patches first?

0

Share this post


Link to post
Share on other sites

@cezeta

If there is a step in a flowchart that you don't meet the criteria for normally you would skip that step:

Copy the TFIL for your patch

So if your patch has no TFIL then you move on since you can't perform that step.

As for running WoW.exe, you shouldn't be doing that after every patch. Also, when you're finished applying all the patches your WoW.exe might still not work with a "134" error. This unfortunately has many sources from bad video drivers to a corrupt patch somewhere.

I've just gone through the guide a fourth time and ended up with that "134" error. It's strange that 2 out of 4 times I ended up with a working client (although the dbc / map extractors still don't work with it).

This whole process is a pain in the ass and seems to be "hit and miss".

0

Share this post


Link to post
Share on other sites

it is all strange :-/

I tried to continue the upgrade process, so I installed wow-4.0.0.12911-to-4.0.1.13164, I copied TFIL and because there was not BackgroundDownloader.exe, I installed wow-4.2.1.2706-enUS-tools-patch.exe... now the backgrounddownloader gives error: "This download is not authorized"... and I am f*cked again :-(... I give up :-(

0

Share this post


Link to post
Share on other sites

Awesome guide MrSmite, now I can finally get to work on my Cataclysm branch.

0

Share this post


Link to post
Share on other sites

Try using this one:

http://limelinx.com/evmft

This is from an early 4.0 version of WOW and this one does not give any errors.

Some of the other backgrounddownloaders give that error randomly.

it is all strange :-/

I tried to continue the upgrade process, so I installed wow-4.0.0.12911-to-4.0.1.13164, I copied TFIL and because there was not BackgroundDownloader.exe, I installed wow-4.2.1.2706-enUS-tools-patch.exe... now the backgrounddownloader gives error: "This download is not authorized"... and I am f*cked again :-(... I give up :-(

0

Share this post


Link to post
Share on other sites

After screwing around with the map extractors for 2 days now, I believe I have come up with what the extractors are looking for, even though there are hundreds of errors, but according to NAY in this thread, those are OK:

http://www.trinityco... err#entry45442

I have tried this variation 3 times and it has worked all 3 times. Using Mr Smite's way of getting to 4.3.4 it gives you all the proper .MPQ files starting from 3.3.5, but when doing that method and using Trinity's map extractor, you get an invalid map.dbc error and it halts. So, even though this is a 100% proper 4.3.4 client, it is not what the extractors are looking for.

I just tried a different method and I was able to run the extractors, you do get the errors as mentioned in the thread above, but supposedly that is OK. What I did is this:

Make a backup of your 3.3.5a client.

Download this backgrounddownloader.exe which is from a 4.0 client and put it in your wow 3.3.5a root directory (where your wow.exe is located). Example: c:wow 3.3.5a

http://limelinx.com/evmft

Download this .tfil file provided by Mr Smite and put in your wow 3.3.5a root directory (where your wow.exe is located). Example: c:wow 3.3.5a

http://limelinx.com/bdleh

Download this .MPQ file and put in your Updates folder, located in your wow 3.3.5a root directory (where your wow.exe is located). Example: c:wow 3.3.5aUpdates

http://limelinx.com/ex605

Download this Launcher.wtf file and put in your WTF folder, located in your wow 3.3.5a root directory (where your wow.exe is located). Example: c:wow 3.3.5aWTF

http://limelinx.com/flrsp

Verify that your Config.wtf, located in your WTF folder has the following line in it:

SET accounttype "CT"

Now run backgrounddownloader.exe that you put in your wow root directory earlier. It should now download and update your .MPQ files from 3.3.5a version of WOW to 4.3.4 and the 4.3.4 extractors should run properly.

To make it a completely working 4.3.4 client, download this:

http://limelinx.com/eqg85

Then copy all of those files to your wow 3.3.5a root directory (where your wow.exe is located). Example: c:wow 3.3.5a

You should now have a completely working 4.3.4 client, but no promises :P

Hopefully this will work for everyone. Many thanks to Mr Smite for getting us on the right track here.

0

Share this post


Link to post
Share on other sites

it is all strange :-/

I tried to continue the upgrade process, so I installed wow-4.0.0.12911-to-4.0.1.13164, I copied TFIL and because there was not BackgroundDownloader.exe, I installed wow-4.2.1.2706-enUS-tools-patch.exe... now the backgrounddownloader gives error: "This download is not authorized"... and I am f*cked again :-(... I give up :-(

Would you please READ THE GUIDE all the way through?

I specifically say what to to if the BackgroundDownloader errors:

If the downloader errors, this is OK, there is no more data for this patch and you can move on

I don't understand how you're having so many problems. Every complaint you have has been explicitly addressed in the guide if you'd just take the time to read it.

0

Share this post


Link to post
Share on other sites

I gues I am that kind of guy :-P backgrounddownloader from oiler2112 works, it is downloading 9GB of data... I'll see what will it do :-)

0

Share this post


Link to post
Share on other sites

I gues I am that kind of guy :-P backgrounddownloader from oiler2112 works, it is downloading 9GB of data... I'll see what will it do :-)

The background downloaders from the tools updaters also work. They download 14 GB of data...

0

Share this post


Link to post
Share on other sites

Ok so my problem comes when on

wow-4.0.3.13287-to-4.0.3.13329. Maybe I'm reading the guide wrong.

Getting following error when I try to patch this with blizz updater: "The file "patch.cmd" in archive "C:UsersStruckerDownloadsWorld of WarcraftUpdateswow-update-13329.MPQ" could not be opened, because an error 2 occurred. If this problem persists, you may be able to solve it by uninstalling and then reinstalling the game. If you are unable to correct this problem, please contact Blizzard Technical Support. (MPQFile::OpenFromArchive)". Plz, if any1 can gimme an hint how to properly run this kind of patch. Thanks

0

Share this post


Link to post
Share on other sites

@strucker

First thing, that "patch.cmd" file is actually in "wow-13287-13329-Win-final.MPQ"

Second, it looks like you might have the files in the wrong folders:

wow-update-13329.MPQ goes in "<wow_installation>Data"

wow-13287-13329-Win-final.MPQ goes in "<wow_installation>Updates"

then you run this from the root of your WoW installation:

"Blizzard Updater.exe" --skippostlaunch=1 --nopatchnotes=0 --patchlist="Updateswow-13287-13329-Win-final.MPQ"

0

Share this post


Link to post
Share on other sites

Altho I had to find wow-13287-13329-Win-final.MPQ myself, all went good, moving on. Thanks MrSmite

0

Share this post


Link to post
Share on other sites

Altho I had to find wow-13287-13329-Win-final.MPQ myself, all went good, moving on. Thanks MrSmite

It is included in the archive linked from the guide.

0

Share this post


Link to post
Share on other sites

Yes, well, from links you provided, 13287 to 13329, and 13329 to 13596 archives do not have win-final mpqs. Doubt they are in some other archives so Ive just dled them from some random place.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.