it may not the battle.net launcher that raise this error:
In the log, the first error is: E 2022-09-17 21:47:53.543096 [BSAgentManager] {184} Error reported by agent: target=agent code=2300 message=
result is BLZBNTAGT000008FC
Also interesting:
D 2022-09-17 20:04:06.661524 [BSAgentManager] {168} Starting agent
I 2022-09-17 20:04:07.692544 [Main] {168} Bootstrapper State: STATE_CHECK_AGENT
I 2022-09-17 20:04:07.692715 [Main] {168} Bootstrapper State: STATE_UPDATE_AGENT
D 2022-09-17 20:04:07.692753 [BSAgentManager] {168} Tracking agent progress for zone: ZONE_UPDATEAGENT
I 2022-09-17 20:04:07.698029 [Main] {1c0} Agent opted into beta successfully
I 2022-09-17 20:04:07.708577 [Main] {168} Progress zone changed to: ZONE_UPDATEAGENT
I 2022-09-17 20:04:09.569464 [Main] {1c0} AgentManager is now initialized
W 2022-09-17 20:04:12.119655 [Main] {1c0} Transport changed to NAMEDPIPE
W 2022-09-17 20:04:13.107380 [Main] {1c0} Transport changed to CURL
W 2022-09-17 20:04:15.191992 [Main] {1c0} Transport changed to NAMEDPIPE
E 2022-09-17 20:04:45.416263 [Main] {1c0} Failed to communicate with Agent after launch, attempts=288
E 2022-09-17 20:04:45.417523 [Main] {1c0} Agent launch exception, path='C:\ProgramData\Battle.net\Agent\Agent.exe' error=2
E 2022-09-17 20:04:45.417616 [BSAgentManager] {1c0} Error reported by agent: target=agent code=2 message=
E 2022-09-17 20:04:45.417699 [BSAgentManager] {168} Fatal error occurred while updating: 2
E 2022-09-17 20:04:45.417755 [Main] {168} Handling exception in state STATE_UPDATE_AGENT: AgentException(code=BLZBNTAGT00000002, details={filename=C:\ProgramData\Battle.net\Agent\Agent.exe}
W 2022-09-17 20:04:45.418617 [Main] {168} Exception converted to: BootstrapperException(code=BLZBNTBTS0000005C, details={}
E 2022-09-17 20:04:45.418662 [Main] {168} Posting exception to controller: BootstrapperException(code=BLZBNTBTS0000005C, details={}
D 2022-09-17 20:04:45.418689 [Main] {168} Bootstrapper thread completed
leads to BLZBNTBTS0000005C
it looks like thats something wrong with bnagent
For linux users, I have reported the update loop as a bug on the Winehq bugzilla. Sorry the forum doesnt allow me to post links. The title of the bug report is " Hearthstone/Battle.net caught in update loop" Please feel free to add anything I may have missed to the report.
For Blizzard here is the output when Battle.net is started in the terminal, its a section that repeats over and over while the game is waiting for other updates. I know you dont support linux, but this is also affecting windows users now.