Printable View
I've been getting error [11006][20641][20643] ever since yesterday whenever I try to download the update. It will start downloading, then stop and give me the error every time. I've uninstalled and reinstalled several times, made sure nothing was marked as read only, tried compatibility mode, and deleted the FFXIV folder in My Games. Anyone else have any ideas?
I was receiving this same error during Phase 4 of the beta, and am getting it again now for the early access. I researched it before and found a post stating it was a checksum error. However, that post was on the beta forums which are now gone.
Essentially the only way I was able to get around it was to keep trying. Eventually the patches would download and update correctly. However, it was far worse for Beta 4 since it needed about 4-5 downloads/updates, and there was a chance of failure with each one.
Until this issue is actually referenced and fixed, the only way around it may be to just keep trying. It took me over an hour of attempts during Phase 4 to get this done, and hopefully it will not take as long this time. >.>
I'm getting a similar error on my PS3. I'm trying for the third time actually...
I'm getting this problem on my PS3 even with the full version from the disc.
Did anyone ever find a solution to this?
I've called SE about this 3 times now.
First time they said they had never encountered this problem before and that a supervisor will send a solution via email. That email never arrived.
Second time they suggested turning on Javascript and enabling cookies, both were already on and still didn't work after I tried fresh reinstallation.
Third time, they speculated a hard drive corruption. Suggested filling up that "portion" of hard drive with other games and files, then installing FFXIV incase the FFIV installation was in the corrupt section of the hard drive.
I wiped my hard drive, then installed about 3GB worth of games, then installed FFXIV.
Re-launched the game. Still got the same damned error during update. SE claims to have never encountered this and they don't know a fix (well not the technicians I spoke with anyway).