I’m done the back and forth here Marroc. This forum isn’t official support - it was designed as a player help player. Which is what I’m trying to do. The forum agents you see only pop on as their normal duties permit. If you want official support open a ticket.
1 Like
I didn’t actually ask for help. Just added my voice that it’s happening to multiple people.
All I did was point out that the suggesting people remove their anti-virus to fix a video game problem isn’t an acceptable solution and was met with hostility. If you wanted to help you could have tried asking questions instead of presuming me incompetent 
This isn’t a widespread issue at all. If it was the forum here is on fire. The solution will be on the client side. Usually a clean install of the Bnet clears these up. I’m just going down the troubleshooting list hoping something sticks.
If you have some ideas put them up here - how the forum works.
1 Like
I never said it was widespread.
It’s a minor inconvenience that most people are probably just ignoring since the game runs just fine.
It’s pure presumption that it’s the local machine. The last time constant patching happened was in BFA and was entirely an issue with the game client/launcher.
A clean install clearly isn’t working if you actually read the 3-4 other users posts in this thread.
If I knew why it was doing it I’d share, but as mentioned I’ve completely reinstalled the game, the launcher, and the user it’s running as. The fact that it’s persisting beyond that means that it’s either an introduced bug with the launcher/wow (because it was just fine until recently and nothing else has really changed on my system) or some combination of hardware / software / game client that is causing problems.
I totally understand the need to run through a list of troubleshooting steps. Just maybe actually trust people when they say they’ve done what was suggested and that it’s still happening.
I just came here to see if anyone else was having the issue and to add my voice to it if they were. I’ve already submitted a bug report.
No offense but you really don’t know that. I’ve been a tech for 30 years and even with 2 totally different machines (PC/MAC) this issue is there. This is not a client only side issue seeing that it’s exactly the same on 2 totally separate operating systems. I’m inclined to agree with the comment before while I agree the “help” was cool the simple fact is you should do a bit more research on something before you even step into help as well.
BTW when something is an issue on 2 totally separate operating systems it’s not some “client side” type of issue when it’s exactly the same and it’s only happening with 1 application which is Bnet and auto update. Marroc is actually correct you really should read what others have said a clean install/new admin account did nothing to fix the problem. I get you trying to help but helping also means you actually read prior posts and not just skip to something that looks like a problem that you “think” you can fix. This is a Bnet issue just like stated before with it happening in BFA which even I noticed and looked at into trying to fix and never could outside of turning off auto update.
Please if you’re going to “try and help” then read what’s actually been said from everyone.
Edit.
Also I’d love for this to ACTUALLY get fixed. However there are somethings that just are not fixable client side when it’s not a client issue. Permissions being written wrong on either OS is not client side. And permissions is honestly what this is coming down to (Mac side at least)
I found this thread on the Bnet app forum. Bnet was running a scan and repair loop. Worth taking a look at. I linked direct to the solution.
It would be good if the OP let us know how the re-install went. Looks like Raalia has reinstalled on a number of occasions. Were those fresh reinstalls or copy of old installs.
They did 
That said, thank you for that link. It eventually led me to https://us.battle.net/support/en/article/000028923 which contained a link to the log collection utility for battle.net, which in turn actually got the log files.
Running that and then digging through the resulting zip file is rather enlightening. It’s a little hard to parse without some specific context so I’ll wait for it to happen again and grab logs immediately afterwards. (Not sharing here in full because they contain things like account name).
At first blush however the logs show an error at the end of most (at least the few I’ve looked at so far) of the ‘ghost patches’ that looks something like this:
E 2021-04-25 05:40:44.427508 [TactVersionWatcher] {Main} Catalog tact query failed. request=http://us.patch.battle.net:1119/catalogs/cdns?nocache=16193292442576673 httpCode=0
It also looks very strange (in a general sense, maybe it’s normal) but the patches all have several ‘blank’ ProductState lines and then jump to finalizing.
D 2021-04-25 05:31:46.997455 [ProductState] {Main} InstallState (wow): currentOperationStatus=Initializing progress=0 playableProgress=0
D 2021-04-25 05:31:48.016754 [InstallManager] {Main} Update started: wow
D 2021-04-25 05:31:48.507383 [ProductState] {Main} InstallState (wow):
D 2021-04-25 05:31:50.027400 [ProductState] {Main} InstallState (wow):
D 2021-04-25 05:31:55.086899 [ProductState] {Main} InstallState (wow):
D 2021-04-25 05:31:55.597560 [ProductState] {Main} InstallState (wow):
D 2021-04-25 05:31:56.617142 [ProductState] {Main} InstallState (wow): currentOperationStatus=Finalizing progress=1 playableProgress=1 thresholds=(1,1)
You mentioned you submitted a bug report. You could get a ticket open see what comes of that.
Contact Support - Blizzard Support (battle.net)
(The OP on their last post said that they were going to reinstall BC beta on a different drive. That is what I was curious about. I assume it didn’t help. )
Will do. Couldn’t find the ticket page for the launcher when I went looking. Thanks for the link!
You might want to try the LogGoblin as well Raalia. You may see something there:
Gathering Blizzard Battle.net Desktop App Logs - Blizzard Support
Adding some insight gained via support case.
See if it happens if you uncheck “pause downloads when I’m playing a game” in the battle.net launcher. The second I uncheck this option it ceases to happen and the problem immediately returns when I recheck it.
Not quite a solution since there’s performance implications to leaving that option off, but it’s at least a direction to go in.
1 Like
For all of those waiting for the OP (me) to report on the latest status…
I uninstalled all 6 flavors of WoW from my SSD, Retail, Classic, Retail PTR, Classic PTR, Shadowlands Beta, and Burning Crusade Classic Beta. I installed 5 flavors of WoW on a different drive (3TB hard drive), no Shadowlands Beta. I had to reinstall all of my addons (Classic and Retail) and reconfigure all of them (which is the reason for the long delay between posts).
THE ORIGINAL PROBLEM STILL EXISTS!
Note: I have been playing World of Warcraft since it was released. I will now open a support ticket as a last resort. Over all these years I never had a problem until a month ago (about the time I was accepted into the Burning Crusade Classic beta and downloaded it).
Here’s a crazy idea (and since you apparently haven’t gone crazy yet): if you have a spare SSD, yank all the cables to your existing drives and reinstall Windows 10 on the spare. THEN reinstall your WoW versions one by one on the spare to see which one is causing bnet to go haywire.
I have Windows 10 installed on an SSD (512GB) and a separate SSD (1TB) for my games which includes WoW. There’s also a 3TB HD which was used as the temporary home of the fresh installs of WoW in this thread.
The version of Windows 10 has been a constant since before this problem started and the only way I’m starting over with a fresh install is if hell freezes over or I get a new motherboard, CPU, and GPU.
The problem remains and apparently, I’m not the only one as others have reported it in this thread. I’m fairly confident that there’s a “silent group” of others that just live with it and I guess I’m about to join that group as well.
Edit: I think I opened a support ticket. What a painful process. It won’t accept .zip files like the LogGoblin output. I clicked the Submit button but it doesn’t show as an active ticket so who knows where it went.
Edit: Thanks for sending the log files! I’ll update this thread when the review is completed.
Been using DOS/Windows for ~30 years so I’m used to doing new installs when problems like that pop up. Usually simpler and faster. lol
Hey there,
In the log files I found the following error:
Error opening container archive file 'D:/World of Warcraft/Data/data/data.006'. (reason: The process cannot access the file because it is being used by another process)
If this error has persisted beyond reinstalling the game to a different folder, it means another program is interacting with the game files. We’d want to:
- Remove the
WoWUP.iosoftware - Remove the
zygor.exesoftware - Remove the
wtf.weakauras.companionsoftware
Keep in mind these are all separate programs on the computer that are not removed when uninstalling or reinstalling the game.
Other recommendations based on the msinfo file in the log are as follows:
- Update Windows from 18363 to 19043 build
- Disable the secondary network adapter labeled
Microsoft KM-TEST Loopback Adapteror try a Windows Network Reset
I do hope the info helps. Let us know how things go!
1 Like
Rather than remove the three listed software packages, I have disabled them.
I’d love to update Windows 10 to the latest build but every time I try, my system becomes very sluggish. I have successfully updated all my other Windows 10 systems to the latest released build but this one, my main gaming system, doesn’t like the latest build (and every build past 1909 (18363), I have tried each one).
I can’t find the network adapter you mention.
Disabling the listed software packages didn’t have any effect. Problem still exists.
Since there’s trouble disabling the extra adapter, try a windows network reset as described here. If the problem persists beyond that please go ahead and create a support ticket. Link them to this thread so they know what’s been done already.