#Battle.net blizzard update agent download

Now you can click on Yes in the UAC prompt… and tada, it should work.This will lock the program to just 1 CPU core/thread, minimizing the risk of the hypothesized multithreading bug. If you’re on Windows 7, just click the “” node to uncheck everything, and then click on “CPU 0” to enable it. Make sure only 1 of the CPU’s checkboxes is enabled.Right click on it and then click on the “Set Affinity…” command.Instead, open up Task Manager and find the program in the “Processes” tab (Diablo-whatever.exe).When you get the UAC prompt, do NOT click Yes (yet).

#Battle.net blizzard update agent download

Download the “Diablo-III-Setup-enUS.exe” as usual, from Blizzard’s website.It makes compiling Paint.NET really fast (lots of C++/CLI these days), and is killer for working on all that multithreaded rendering code.Īnyway, the fix is a bit clumsy but it seems to work (so far! we’ll see if it still works after all the downloading is done): That means Task Manager shows 32 tiny little performance graphs. It is a beast: dual processor, 8 cores each, with HyperThreading. You see, I just put together a brand new Dual Xeon E5-2687W system. In a last act of desperation before borrowing the DVD from a friend to try and load it that way, I had some Raymond Chen style psychic insight and thought it might be a multithreading bug. Every single time, over and over and over and over again. I finally succumbed and bought a copy of Diablo 3 today, only to found out that it just doesn’t work:Īrgh! No matter what I did, it would always crash.