World of warcraft setup updating blizzard update agent

So they created the domain which points to

But there's a problem, they can't use http traffic (because of mixed content warnings, even though it wouldn't really be insecure), so they have to use https traffic.

world of warcraft setup updating blizzard update agent-7world of warcraft setup updating blizzard update agent-84world of warcraft setup updating blizzard update agent-87

Graev has Windows Vista and could not get past the “Updating Setup Files” little window that came up. ) This one worked for me: try and find the agent application in the folder (for example C:\Documents and Settings\All Users\Application Data\\Agent). Check the folder you downloaded your files into for any that say . Run the downloader in the same directly you chose originally and it should fix the files automatically and/or finish downloading.

We scoured the support forums for days, Googled, and had no luck until tonight. Choose Windows XP (Service Pack 3) (Note: Does not work on Vista.) Right Click the Icon, Run as Administrator. Delete your C:\Program Data\Blizzard Entertainment\Cache folder. Run the Downloader again, as administrator, and see if it gets past the “Updating Setup Files” window. Start the agent application manually and after that start Diablo III setup file in your Diablo-III-8370-en GB-Installer folder. Fix #4a – Clarification for Fix 4 by Garythe Oak 1.

So I guess I'm asking, what am I missing, why is everyone freaking out at Blizzard? Usual Root CAs (Commodo, etc...) are held to very very very high standards in how securly they store their private key because of just how bad it is for it to leak.

As a non-techie, can someone expand the reddit post below, and why each individual's person private key is thought to be secured? They are forced to undergo a very thorough audit process before being trusted.

So there is no root certificate or CA involved -- the title of this HN article is incorrect and the Reddit thread is mistaken.

(To caveat again: I have not personally verified this, and am digesting information supplied by other HNers) However, if you don't plan to log in to using Facebook, then there's probably no downside to disabling this certificate either.

Here is the fix that finally worked for Graev: Fix #1 Go to Control Panel Properties Change it from ‘Disabled’ to ‘Automatic’ Run your Diablo 3 setup as administrator and it should quickly go through Updating Setup Files and bring you to an install screen.

Looking at the certificate posted lower in this thread, everyone is throwing a fit over nothing.

What blizzard is doing is simply wrong, from a technical and ethical perspective. Everyone that has has a permanent server on localhost:22885.

Tags: , ,