Been starting a HCSSF char… and was playing last friday… but i’ve keep getting this error 14403 all the evenings since…
I’ve opened a ticket at Battle.net but they keep sending me here… since their solutions arent working for me… such a Checking firewall, anit-virus, restart pc & router, disable background apps, flushing the DNS…
The 14403 code arent helping much, it doesnt say whats wrong… Hope you guys are able to help me, im start to get abstinences xD
Not sure, to be honest… look for error messages towards the end of the file… something that might give a clue about the problem. The D3Debug.txt file gets rewritten each time you launch D3… so you could launch it with the free trial account and save the debug info on your desktop… and then launch it with your normal account and compare the two debug files. Check if the debug file with the normal account is shorter for example…
That’s possible… there are also some cases on the Korean and Russian forums:
You can perform a soft reset of your account if you wish by changing the password:
exit Diablo 3 completely
exit Battle.Net
go into your Account Settings and change the password (https://account.battle.net/security)
Reload the BNet App and launch D3… see if it will let you log in.
No this is not related to parsec, ai is mixxing smth up there parsec error is 14003 and this is 14403 this is the root cause to this error: – CAuthHandler::OnGetLogonFormResult(14403, „JSON error: Status has no name.(14403) token: 2“, 0, )
sadly not yet, already tried like everything reseting winsocket, enable a firewall passthrough disable it completly reinstall os and drivers, start as other user, weird thing is that it’s since the bnet update on friday and tried it in a different network as well and with a account of a friend to test
if everyone which has the same erro could post theri d3debug file so i can compare, the onliest thing i saw with a working client is that the worker id on the server side is different, so would like to know what we all have in common, maybe only one worker is messed up or smth on bliz side or we have a special driver or smth if you could also sen me the input of msinfo32 to see maybe we have a special piece of hardware in common or smth
Suggested solution:
uninstall latest win updates (exact version when it’s working again will follow)
or update to Windows 11
If your system doesn’t meet the requirements for Win 11 go to your registry and add the following dword to: HKEY_LOCAL_MACHINE\SYSTEM\Setup
dword: AllowUpgradesWithUnsupportedTPMorCPU
and set value to 1
then download win 11 iso and install via there