Patch 2.0.5 was initially released on the morning of January 14, 2007. However, due to authentication issues, some players were not able to log on. Blizzard altered the servers to allow players with and without the patch to continue play the game. Those who have patched to 2.0.5 may be stranded as there is no rollback procedure for the game client. The problem stemmed from a change in authentication. Under the new patch, the authentication servers would only allow clients with the Burning Crusade installed, of which publicly, there were none at the time.
Attributes | Values |
---|
rdfs:label
| |
rdfs:comment
| - Patch 2.0.5 was initially released on the morning of January 14, 2007. However, due to authentication issues, some players were not able to log on. Blizzard altered the servers to allow players with and without the patch to continue play the game. Those who have patched to 2.0.5 may be stranded as there is no rollback procedure for the game client. The problem stemmed from a change in authentication. Under the new patch, the authentication servers would only allow clients with the Burning Crusade installed, of which publicly, there were none at the time.
- Patch 2.0.5 was initially released on the morning of January 14, 2007. However, due to authentication issues, some players were not able to log on. Blizzard altered the servers to allow players with and without the patch to continue play the game. Those who have patched to 2.0.5 may be stranded as there is no rollback procedure for the game client. The problem stemmed from a change in authentication. Under the new patch, the authentication servers would only allow clients with the Burning Crusade installed, of which publicly, there were none at the time.
|
Version
| |
dcterms:subject
| |
dbkwik:pl.wow/prop...iPageUsesTemplate
| |
dbkwik:wowwiki/pro...iPageUsesTemplate
| |
ToC
| |
Highlights
| - * Several bugfixes
- * Several bugfixes
|
Related
| - * Official patch notes
- * Official patch notes
|
PREV
| |
Release
| |
NEXT
| |
abstract
| - Patch 2.0.5 was initially released on the morning of January 14, 2007. However, due to authentication issues, some players were not able to log on. Blizzard altered the servers to allow players with and without the patch to continue play the game. Those who have patched to 2.0.5 may be stranded as there is no rollback procedure for the game client. The problem stemmed from a change in authentication. Under the new patch, the authentication servers would only allow clients with the Burning Crusade installed, of which publicly, there were none at the time. Hours later, Blizzard announced that the problem has since been fixed, and that clients 2.0.4 and 2.0.5 could coexist. Patch 2.0.6 was released the following week.
- Patch 2.0.5 was initially released on the morning of January 14, 2007. However, due to authentication issues, some players were not able to log on. Blizzard altered the servers to allow players with and without the patch to continue play the game. Those who have patched to 2.0.5 may be stranded as there is no rollback procedure for the game client. The problem stemmed from a change in authentication. Under the new patch, the authentication servers would only allow clients with the Burning Crusade installed, of which publicly, there were none at the time. Hours later, Blizzard announced that the problem has since been fixed, and that clients 2.0.4 and 2.0.5 could coexist. Patch 2.0.6 was released the following week.
|