Ok. So. I’ve gone through every step. I have done ‘everything’ including a full factory reset. Nothing works. The error however has changed now. It still denies me access to Battle.net in full.
Battle.net.exe - No Disk
(X) There is no disk in the drive. Please insert a disk into drive D:.
I. do. not. have. a. D. Drive. I have just done a full factory reset.
The Extensive One. The 9 hour kind.
Why is it asking for a non-existant drive? Rollback the B.Net App. This is comically stupid, and the fact that people were saying it was due to the power outtage was even more ridiculous, what is really going on and when can we expect a tangible resolution?
Beyond that, issue is identical as Brerae defined it. System goes into an infinite loop of error messages. Control Panel action to shut down the B.Net app is required to proceed.
Pressing “cancel” , “try again”, or “skip” doesn’t do anything, and the error window locks you into an endless loop. I finally had to kill the Bnet app process through task manager to stop it. Tried all the troubleshooting steps mentioned to no avail.
I have also be plagued with this error, and it happens for Overwatch or anything from Blizzard I try to launch. It was working fine for months, and then on Sept 3rd it doesn’t work. Restarting the PC doesn’t help. The Windows OS is otherwise healthy and it can run chrome, MS Teams, Outlook and anything else just fine. This is a Blizzard problem. Even after a login to the Battle Net screen, this error continues to pop up and one never gets to the actual application. In my case I only see 4 Battle.net.exe apps in task manager. I’m not sure what is normal there. I have to kill them manually in there.
To reproduce this issue, I suggest playing around with a system where a phone might be plugged in and unplugged, or having USB card reader and plugging in some media and then unplug. In my case the error is happening with no media connected. But I did have an SD card and phone connected prior to seeing the error. Right now, just C: drive running Windows 8.1 all patched. I have a disks D, E, F and G all showing no media and the error can be experienced. There is only one user account on my PC.
I haven’t been having this same error, but ever since the same patch you’re referring to, my Win10 machine simply will not start the Battle.net desktop app. (See my unanswered thread at Unable to run Blizzard desktop app).
I uninstalled Battle Net. Then ran Overwatch which triggered a reinstall. This completed okay and then it ran. I was able to run Overwatch, but did see more of the same No Disk -> “Exception Processing Message” errors. I quit Overwatch and Battle Net. On launching Overwatch again (which triggers Battle Net start) I am back to square one with the errors. I can see the Battle Net login after a dozen or so errors, and after logging in, the application never starts - it is an endless loop of these No Disk errors.
Yeah, to chime in with Reveranditus, I do use my PC to charge my phone via a USB. That being said I am at a loss as to why after 2 full factory resets with only the mouse and keyboard plugged in, it is still occurring. I would of thought a PC fresh and ready for recycle would not have this issue.
I went through all of the steps the GMs proscribed. My issue has ‘changed back’ as a result and I am at square 1 again, where I was before I wiped my PC. Posting the steps in the off-chance it helps someone else.
Hey there XXXXXXX,
Tech Specialist XXXXXXXX at your service Reading over the incident it sounds like Battle.net was originally installed to a Drive that was removed from the computer. So we’ll want to clean some folders form the system and reinstall the app.
Hold CTRL and press R
In the box, type %ProgramData% then hit enter. This will open a folder on the computer.
Delete Battle.net and Blizzard Entertainment folders. Note, if you receive any errors with this process please restart the computer then retry. Closing any running Battle.net tasks in Task Manager may also work.
Note, please use the default install path instead of any custom file path.
If it’s still not working after that please provide us with updated system files so we can verify any new error reporting after these changes were made: https://battle.net/support/article/000012988
Ever since I booted up Battle.net absolutely fine yesterday and it did an update and asked me to restart battle.net, I am having the exact same problem as OP. Down to the details.
I also have Windows 8.1
I currently cannot log in and have made threads about this also.
down to the infinitely repeating No Disk error asking for drive D:, which I don’t have. Exactly the same. I also have Windows 8.1 (not Pro) x64.
Everything else works absolutely fine on my computer and I have changed nothing at all for a very long time except the Battle.net update it did when I logged in yesterday. Immediately after the update it started doing this.
The only other drives on the system have nothing to do with applications and gaming. Only phone and camera SD card. Battle net has only been on C: drive and will only be on C: ever.
I have a samba mounted drive to keep backups of photos, etc. It has been in existence since the OS was set up years ago. Applications are never installed to it.
I found a partial solution which has worked only twice.
The desktop icon points to “C:\Program Files (x86)\Battle.net\Battle.net Launcher.exe”
If you look in the same folder, there is a “Battle.net.exe”
Run “Battle.net.exe” from Windows Explorer. It produces a single instance of this error. Then I was able to login to Battle net and run Overwatch.
I went through the same process a second time with no Battle Net running in the task manager, but it did not work.
I killed all of the hanging processes for Battle net. Repeated this, still no go.
Okay, maybe switchback? I run “Battle.net Launcher.exe” again from Explorer location (not desktop), click Cancel on this No Disk error a bunch of times, login to Battle.net, and voila, I can launch Overwatch from the Battle net app again.
I’m just going to keep it running so at least there’s some fun. But give this switch a try and see if you get in.
(Edit: What I mean by switch is if "Battle.net Launcher.exe” is failing, try running “Battle.net.exe”, and vice versa. Somehow it helps to dodge the issue. It doesn’t dodge the error coming up, but it does dodge endless loop of them. I think you will get into Battle Net after a login, rather than seeing the error pop up dialog forever.)
Yeah, what I’ve had to do is just completely disregard Battle.net and play the game off of my SSD by accessing WoW from the file, like we used to do back in the day. I sure hope that Blizzard comes up with a solution, because I have no idea how we’ll update to Shadowlands or beyond if this goes unresolved.
I spoke to a GM again. This time it was one from the EU Forums evidently, who requested I download an exe called LogGoblin. I did so and it generated a mass of logs about Warcraft and Battle.net.
I would love to send them on to further arm Tech Support with info on this issue (which is still occuring), but I am not allowed to send Zip Files and I have no idea which files you guys need. Please refer to Ticket: US75107885 for more details and please advise.
I’m having the exact same problem as well, the 13 error message when I try to load the blizzard launcher. I restarted a few times and nothing’s changed. I guess I’ll come back in a few days and try to log in again.
Hey Gurdlesklech. It’s not a solution, but it is possible if you have the game already downloaded (like Warcraft), to just launch it directly from the Game Folder and thus bypass Battle.net completely. Not sure why this happened, or how long this will work since we will need Battle-net to patch us to the Shadowlands updates in 2 months… But it’s the best I can offer to you till a fix is found.
Sucks, I really wanted to help with the Beta Test and now that I’m in I can’t access it.
You can send those to techinfo@blizzard.com and I’ll look at them for you. Keep i mind this inbox isn’t monitored so please reply here after the email is sent to make sure someone knows to check for it.
Reading over the incident it sounds like Battle.net was originally installed to a Drive that was removed from the computer. So we’ll want to clean some folders form the system and reinstall the app.
