Error 315300 preventing 'Diablo 3' players from logging in, inconvenient fix found

The long, long wait for Diablo 3 was made longer for some folks this morning by Error 315300, an issue that's preventing players from logging into the game.

The long, long wait for Diablo 3 was made longer for some folks this morning by Error 315300, an issue that's preventing players from logging into the game.

The error is indicative of an incorrect username or password input, commonly brought about by user error, or by attempting to paste non-plain text into the password field. However, some Diablo 3 players (and beta participants) are getting the error through no fault of their own.

The issue appears to be a subfolder in the game's ProgramData directories which gets elevated privileges, making it inaccessible for the account which installed it — even if that account is an administrator.

Users on the Blizzard forums have reported a number of fixes for Error 315300, but one seems to be the most successful across the board — at least one Polygon editor experienced the error, and managed to fix it this way: just create a new Windows user account with administrator privileges, restart your computer, and load the game in that new account.

It's a bit inconvenient to switch accounts every time you want to play Diablo 3, but right now, that appears to be your best option. We've reached out to Blizzard to try to find a cleaner fix.

In the meantime, we'd suggest checking out a few choice threads on the Technical Support forums for more fixes to your problems. If you haven't started playing yet, we also suggest you uninstall all your Diablo 3 beta files, make sure your video card is supported and, for God's sake, don't talk to the Templar.

Here's a few Blizzard-answered threads of more common issues:

• Play button in Launcher doesn't work
• Fix for Error 108
• Failed to run required program on Setup