Error when patching: [11006][20641][20643][19900][3]

When I attempt to download patch 2.3, I get this error within the last 50mb of the download. I had this error as well when I first installed the game, and it seemed to be fixed by changing my dns server to 8.8.8.8, but now this error is back. I've tried the following to no avail:

• Changing my adapter's dns to 8.8.8.8
• Setting all of the FFXIV .exes to run as Windows 7 (currently on W7 SP1)
• Disabling Microsoft Security Essentials/Windows Firewall
• Deleting patch folders in downloads\ffxivpatch\

This is getting very frustrating because I have been able to play the game, but now I'm essentially locked out again. There doesn't seem to be much recent documentation of this error, so I'm beginning to feel more and more isolated in my error. Any ideas?

Ive got the exact same problem. Ive been trying to dl all day.

I've been having this problem as well since the patch came out, haven't been able to play, sent SE a ticket, and all around super pissed off. From everything I've found on redit(which by the way seems to have more information about this them the actual forums do) this has been happening to some people every patch since around Dec and SE has never commented about (AMAZING! customer support there guys).

I've tried changing numbers in the launcher file, deleting patch files, uninstalling the game and every other "fix" I've found to no avail.

I thought it was my ISP that's giving me problems on downloading the patch. It's been three days and about every two to four minutes of downloading the client stops with this error notice:

https://lh5.googleusercontent.com/-K...543+AM.bmp.jpg

BUMMMMMMMMMMMMMMMMMMMP FOR ANSWER, WHY IS THIS SO AN ISSUE THAT IS UNNOTICED BY STAFF!!!!!!!!!!!!!!!!!!!!!!

I have the same problem. Right now it still isn't patching properly.

why is no one addressing this issue ?

Probably not the cause for everyone, but it turns out I was getting this error due to some bad RAM. I play on an iMac using a Windows 7 Bootcamp partition. As soon as I removed the bad stick of RAM, the updater completed without error. Again, might not be the solution for everyone, but something worth looking into.