I have uninstalled and re-installed the battle.net app multiple times but it still crashes on launch after hanging. I cannot even enter my email or password.
I have disabled the windows firewall, all antivirus, etc. generally made the system fully insecure.
Please help, I am unable to open a web ticket with any browser on multiple computers from multiple networks.
Please help…
Howdy Fodder,
In your situation, you may need to do a clean reinstall of the app. While you may have already attempted a reinstall, we would need to remove all the old files first as there could be corruption.
I have done all of that and I still cant get Battle.net to download. It hangs up on downloading new files, and all of this happened shortly after i rebooted my router and reset config. I have reset all factory network connections, still nothing. I can log in online just fine as i type this reply to you. Still not downloading, and it will stay where it is ALL DAY if you let it. I first noticed an issue when battle.net would not “GO ONLINE” after i reboot my route.
Hi Zenlaka,
I have performed all the steps you outlined as specified. Battle.net still just goes “Not Responding” just after it stats and then crashes.
The MSInfo is too large to pastbin, how can I transmit the debugging information to you?
Myself and others are unable to open a ticket with the support system, it just keeps taking us back to the top of the page whenever we submit despite having provided all required information. I have tried on multiple systems, both Mac and Windows, with IE, Firefox, Chrome and Safari.
I figured out why it would not download! I have an ASUS 802.11 AX / WIFI mode 6 router, My wireless network card in my computer is 802.11 AC / WIFI mode 5. I disabled (temporarily) the 802.11 AX function in my router settings. Also I accidentally hit the WPA encryption button on my WIFI settings on my router. turned off my WPA encryption function. Between these 2 actions within my router AND clearing all related %…% folders on my computer, I was able to run Battle.NET (AS ADMIN) and success has been achieved. So Fodder, double check your router WIFI settings as per stated above and you should be ready to rock and roll buddy. Good Luck and Happy Hunting!
P.S. I also verified that all battle.net and blizzard programs and games have been cleared from my system. I’ll have to reinstall everything, including any addons, but its working as intended right now!
Hi Wolfy,
My computer is wired…
Thanks.
Make sure the diagnostic files are in the .txt format instead of .nfo.
They are.
DxDiag.txt
MSInfo.txt
It then directs me to " Before submitting a ticket, try the following: ", hit submit there and back to the ticket submit page, with all fields still populated. No ticket is generated.
Have you tried a new admin account to see if it’s a setting on the current one blocking the install/patching?
New admin user, installed, updated, etc. Launched the login panel, spinner goes for a couple of seconds, hangs “not responding” and crashes.
You mentioned disabling the antivirus software you were using, but some of the third-party ones continue running in the background even when disabled. If it is one of their apps blocking the install, perhaps temporarily uninstalling them could help. Then you could reach out to them for assistance configuring it to stop blocking Battlenet.
Alternatively, how about another network? Do you have a smartphone you can tether and see if the connection happens?
Crash reporter popped up, please see 0351B546-74C2-4E1F-9453-CCEB2C4CFA54
Hey there,
Looks like some windows .dll files aren’t doing what they’re supposed to. Lets try the following:
Run a malware scan! Info on free anti-malware services (like Malwarebytes) can be found here.
Run this System File Checker.
Update the operating system, the crash is showing 18363 in the report but there is a newer 19042 available.
Hope the info helps. Let us know how things go!
Latest automated crash report id: 4F7D7B34-CD64-41D6-9EED-7E0F3714043D 12/4/2020 @ 2:50 EST
Please follow up with ticket US76754018. I have provided updated DxDiag and MSInfo files.
I have scanned my system with MalwareBytes and BitDefender, no issues identified.
I have upgraded to 20H2, uninstalled, cleaned, re-installed battle.net.
Battle.net starts, presents the login box, hangs “not responding” then crashes without an error message. Battle.net was started with “Run as Administrator”.
Thank you. I would really like to be able to get back to playing my 6+ toons…
@Kaldraydis I failed to run the SFC process, that has been completed per the MS instructions. No issues reported by the tools.
Battle.net continues to hang and crash…
Here are the last few lines of the battle.net log file
D 2020-12-03 00:23:24.159023 [ProductManager] {Main} Product modified: VIPR ProductChangeFlags(name_style,type_name,rank,65)
D 2020-12-03 00:23:24.159037 [ProductManager] {Main} Product modified: W3 ProductChangeFlags(name_style,type_name,rank,65)
D 2020-12-03 00:23:24.159052 [ProductManager] {Main} Product modified: WTCG ProductChangeFlags(name_style,type_name,rank,65)
D 2020-12-03 00:23:24.159066 [ProductManager] {Main} Product modified: WoW ProductChangeFlags(name_style,type_name,rank,65)
D 2020-12-03 00:23:24.159080 [ProductManager] {Main} Product modified: WoWX7 ProductChangeFlags(name_style,type_name,rank,65)
D 2020-12-03 00:23:24.159094 [ProductManager] {Main} Product modified: WoWX8 ProductChangeFlags(name_style,type_name,rank,65)
D 2020-12-03 00:23:24.159105 [ProductManager] {Main} Product modified: ZEUS ProductChangeFlags(name,name_style,type_name,selector_display_name,uid,rank,deprecated,supports_starter_mode,supported_regions,region_permission_flags,65)
D 2020-12-03 00:23:24.159248 [ProductManager] {Main} Products updated
D 2020-12-03 00:23:24.159632 [CatalogVarStorage] {Main} Setting var from catalog Client.Shop.SaleNotificationVersion=6
D 2020-12-03 00:23:24.159650 [CatalogVarStorage] {Main} Setting var from catalog Browser.DisableSiteIsolation=true
D 2020-12-03 00:23:24.159662 [CatalogVarStorage] {Main} Setting var from catalog Client.ActivisionAutoAccountCreation.Games=ODIN,ZEUS
D 2020-12-03 00:23:24.159675 [CatalogVarStorage] {Main} Setting var from catalog Client.Shop.SaleNotificationEnabled=false
D 2020-12-03 00:23:24.159689 [CatalogVarStorage] {Main} Setting var from catalog Client.OwlScreen.LiveCheckIntervalMS=300000
D 2020-12-03 00:23:24.159715 [CatalogVarStorage] {Main} Setting var from catalog Client.NewProfileWindowLayout=true
D 2020-12-03 00:23:24.159730 [CatalogVarStorage] {Main} Setting var from catalog Client.PromotedScreenVersion=2
D 2020-12-03 00:23:24.159743 [CatalogVarStorage] {Main} Setting var from catalog Client.Version.BetaAccessOverride=enabled
D 2020-12-03 00:23:24.159756 [CatalogVarStorage] {Main} Setting var from catalog Client.Version.BetaBranchOverride=beta
D 2020-12-03 00:23:24.159770 [CatalogVarStorage] {Main} Setting var from catalog Services.WhisperChannels.InactivityTimeoutMS=0
I 2020-12-03 00:23:24.168681 [CatalogLoader] {Main} *** LOAD COMPLETE default ***
D 2020-12-03 00:23:24.337548 [ClientServiceAlertMonitor] {Main} Maintenance remote content has been updated
D 2020-12-03 00:23:24.347407 [InstallManager] {Main} Game finished versioning battle.net
D 2020-12-03 00:23:24.944637 [UnifiedAuth] {Main} UAuth: finished loading. statusCode=200 state=Login
I 2020-12-03 00:23:28.334663 [GameSessionList] {Agent} Reporting process: TrackingInfo(uid=battle.net, type=game, opStatus=On, reqId=0, running=5, oldRunning=1)
And the top of the crash report
==============================================================================
Battle.net.exe: (build 12511)
This application has encountered a critical error:
ERROR #1 (0x13370001) Fatal Exception
Program: C:\Program Files (x86)\Battle.net\Battle.net.exe
Exception: 0xe0000008 (unknown exception) at 0023:75A09AB2
Crashed Thread: 0x000038a4
Battle.net
<BlizzardError.ProjectId>127
<BlizzardError.Module>Phoenix 1.0
<BlizzardError.BuildNumber>Phoenix 1.29.0.12511
<BlizzardError.Platform>All PC
<BlizzardError.DesktopOS>Win
<BlizzardError.IssueType>Exception
<BlizzardError.Priority>None
Exception.Summary:
0xe0000008 (unknown exception) at 0023:75A09AB2 : error 1: ERROR #1 (0x13370001) Fatal Exception
<:Exception.Summary>
Exception.Assertion:
DBG-ADDR<6aace98d>("")
DBG-ADDR<6ab1aaca>("")
DBG-ADDR<6b2a39f1>("")
DBG-ADDR<6ab2543e>("")
DBG-ADDR<6e108c54>("")
DBG-ADDR<6ab09a2c>("")
DBG-ADDR<6ab0977c>("")
DBG-ADDR<6ab099f5>("")
DBG-ADDR<6ab09b74>("")
Howdy Fodder,
Can you try disabling the Hardware Acceleration in the Blizzard app? To do this, right click on the Blizzard app icon and select the properties to view the app settings. Locate the section titled “Target” within the Shortcut settings tab. In the target section you will see the location of the application files which should end like this \Battle.net Launcher.exe"
Once located please add " --disable-gpu" after the quote mark so that the end of the target looks like this \Battle.net Launcher.exe" --disable-gpu
Hi,
So, I dropped $900 on an EVGA 3070 and I have fully reinstalled my system using Windows 10 recovery media. Battle.net still crashes in exactly the same way as before. This is a Battle.net bug.
This system played WoW fine before 11/21/2020 so some change to Battle.net between then and 12/4/2020. This entire issue started with a “restart battle.net” prompt. Please have someone focus on the changes in that time frame as to why this is happening.
I have manually copied WoW from another persons computer to my system using an external USB drive. WoW runs fine on my system.
PLEASE FIX BATTLE.NET so I can stop driving 10 miles round trip every time there is a patch…
My system exceeds all requirements for WoW and Battle.net
Crash report 866F780E-553F-48D5-AD2B-3562A6B64538
Updated Battle.net
Crash report 75D772D0-3850-4907-A547-0C26EDC1725F
Thanks and please excuse my frustration.
Hey there,
So far we are not receiving large volumes of these errors which typically suggests the problem is more localized instead of a bug in the system. It may be ideal at this point to submit a ticket. There we can go into much more detail on the problem and work with you more directly.
Thank you for working with us on this. Cheers!
I have submitted multiple tickets regarding this issue. They have suggested I submit a bug report.
Can someone please look into whatever change was made during the time frame indicated?
This is a battle.net bug plain and simple.
Sounds like blizzard needs to do their job