Once you extract the files you can start the 64-bit client by opening the Launcher as normal (Run as Administrator if applicable), go intoOptions -> Game Preferences, and toggling the Launch 32-bit client setting. Before being able to launch WoW in 64-bit mode you will need to download the 64-bit client for PC/Mac (using one of the links below), and unzip it into your World of Warcraft directory. EST Blizzard posted an update this afternoon:Ī 64-bit client is now available for use with Patch 4.3.2. The download links and everything still work, however. We'll update this post when we know more. We're assuming this is due to the validation errors with the servers.
EST Blizzard pulled the download information from its support forums and posted a message saying that final preparations were being made and the client would be up soon. This is probably a quick fix that Blizzard can take care of, and we're hopeful that everything will be solved soon.ĭownload the Windows client here and the Mac client here. I've installed this live 64-bit client however, there still seems to be a version validation error with the servers. Be sure that if you do experience them, you report them right away so Blizzard can fix everything up. This means that you might experience unexpected crashes and other bugs.
Please remember that this 64-bit client is still in beta, even though you can play the live (non-PTR) game with it. Hence I knew where to begin troubleshooting.As we posted earlier, Blizzard has released the information necessary to get the 64-bit client up and running with the live patch 4.3.2 servers. I tried the same with WotLK server, but same result. Hence I knew where to begin troubleshooting. Sidenote: this is my first server, I don't have any experience with other servers.
Then using powershell's "Test-Netconnection FQDN -port 8086" gave a TRUEĪll the same above for port 8085 DIDNT work for me. In windows firewall, allowed INBOUND programs authserver.exe and worldserver.exe Apparently the subnetmask is for the network, not for the host.
Apparently 0.0.0.0 works only for local connections, but not remote connectionsĬhanged in nf port 8085 to 8086 Port 8085 had issues, had to change to 8086.Ĭhanged in nf and nf IPs 0.0.0.0 to the local (LAN) IP of the computer.
0 kommentar(er)
