Launcher Error -2146697211 after Windows 10 Upgrade.

The launcher uses the Internet Explorer components of Windows...so you would want to be adjusting things at either the OS level (inetcpl.cpl in the search/run box) or from within Internet Explorer itself for the browser related items (like TSL encryption(the new 3.x SSL) and trusted sites and such).

You should probably also create exceptions in your chosen security applications for the executables as well to make sure they have internet access and such (ffxivlauncher, ffxivupdater, etc.--6 or 7 total nested in the different subfolders).

I also had that error right after upgrading to windows 10. I deleted my ffxiv boot config files (documents\my games\ffxiv\) and disabled all my antivirus/firewall shields (AVAST) and it seemed to work. Re-enabled shields and restarted computer and now it works just fine!

Quote:

---

Originally Posted by Flaeb

http://puu.sh/jr0uj/6b4226a8f5.png

I've done a ton of research on this issue and I am at a lost.

---

The problem is not:
- Avast (free)
- Internet explorer
- The Launcher itself

I installed Windows 10 two days ago, I ran the launcher just fine, it updated FFXIV, and FFXIV DX10 launched just fine.

This appears to be directly a problem with DNS. I'd suggest you set your DNS to 8.8.8.8 on your Windows PC or router and see if that resolves it. Some ISP's run intercepting DNS (so they can serve custom "not found" pages for whatever the hell reason) so it results in very slow to updates, and that is in fact a change I deliberately make every time it seems like DNS is the culprit.

Quote:

---

Originally Posted by KisaiTenshi

This appears to be directly a problem with DNS. I'd suggest you set your DNS to 8.8.8.8 on your Windows PC or router and see if that resolves it.

---

That fixed it for me.

My DNS is always 8.8.8.8 8.8.4.4. Good thinking though!

Quote:

---

Originally Posted by Flaeb

My DNS is always 8.8.8.8 8.8.4.4. Good thinking though!

---

Interestingly enough, I actually managed to see this error (twice) when I logged out and logged back in later. So this might actually be a DNS cache issue.

I've just now got this today. I was able to login last night, but today I can't because of this error.

FIXED IT FINALLY! The problem is indeed WINDOWS DEFENDER. However, I couldn't disable Windows Defender because Avast was running, you need to disable Avast (or whatever Anti Virus program you're using), THEN you can disable Windows Defender. I'll post pics on OP.