Not working as intended with Black Ops 4 about bnetlauncher

[dafzor]

Are you running battle.net client as administrator? or does Call of Duty: Black Ops 4 require administrator rights to launch?

[slagliano]

Are you running battle.net client as administrator? or does Call of Duty: Black Ops 4 require administrator rights to launch?

I have tried running Steam and Battle.net client both with and without admin privileges. I don't think CoD itself requires privileges on its own as far as I know.

[dafzor]

Could you enable logging (see instructions.txt) and post the resulting file here?

[slagliano]

Could you enable logging (see instructions.txt) and post the resulting file here?

[2018-10-15 19:01:09.4839]: Battle.net Launcher for Steam version 1.22.6832.4843 started
[2018-10-15 19:01:09.4899]: Environment: Microsoft Windows NT 10.0.17134.0 (4.0.30319.42000), 64bit
[2018-10-15 19:01:09.4909]: Getting Machine details:
[2018-10-15 19:01:09.5409]: OS: Microsoft Windows 10 Home (10.0.17134, 64-bit, 1033)
[2018-10-15 19:01:09.5419]: CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz; RAM: 16384MB
[2018-10-15 19:01:09.5429]: GPU: NVIDIA GeForce GTX 970 (4095MB, 25.21.14.1634)
[2018-10-15 19:01:09.5429]: HDD: WDC WD1003FZEX-00MK2A0, Samsung SSD 850 EVO 250GB
[2018-10-15 19:01:09.5449]: ClientExe = 'C:\Program Files (x86)\Battle.net\battle.net.exe'
[2018-10-15 19:01:09.5449]: Checking for other bnetlauncher processes
[2018-10-15 19:01:09.5459]: No other bnetlauncher detected
[2018-10-15 19:01:09.5469]: Given parameter: codbo4
[2018-10-15 19:01:09.5489]: Known key for game 'Call of Duty: Black Ops 4'
[2018-10-15 19:01:09.5939]: Issuing game launch command 'VIPR' at '07:01:09.5939'
[2018-10-15 19:01:09.7228]: Searching for new battle.net child processes for the game
[2018-10-15 19:01:09.8148]: No child process found.
[2018-10-15 19:01:10.4040]: No child process found.
[2018-10-15 19:01:10.9938]: No child process found.
[2018-10-15 19:01:11.5846]: No child process found.
[2018-10-15 19:01:12.1755]: No child process found.
[2018-10-15 19:01:12.7663]: No child process found.
[2018-10-15 19:01:13.3561]: No child process found.
[2018-10-15 19:01:13.9459]: No child process found.
[2018-10-15 19:01:14.5357]: No child process found.
[2018-10-15 19:01:15.1255]: No child process found.
[2018-10-15 19:01:15.7133]: No child process found.
[2018-10-15 19:01:16.3021]: No child process found.
[2018-10-15 19:01:16.8910]: No child process found.
[2018-10-15 19:01:17.4929]: No child process found.
[2018-10-15 19:01:18.1247]: No child process found.
[2018-10-15 19:01:18.7415]: No child process found.
[2018-10-15 19:01:19.3793]: No child process found.
[2018-10-15 19:01:20.0141]: No child process found.
[2018-10-15 19:01:20.6429]: No child process found.
[2018-10-15 19:01:21.2727]: No child process found.
[2018-10-15 19:01:21.9105]: No child process found.
[2018-10-15 19:01:22.5507]: No child process found.
[2018-10-15 19:01:23.1924]: No child process found.
[2018-10-15 19:01:23.8322]: No child process found.
[2018-10-15 19:01:24.4630]: No child process found.
[2018-10-15 19:01:24.9659]: No child process game found, giving up and exiting
[2018-10-15 19:01:27.2511]: exiting with error: Couldn't find a game started trough battle.net Client.
Please check if battle.net did not encounter an error and the game can be launched normally from the battle.net client.

bnetlauncher will now exit.

-Here ya go, thanks!

[dafzor]

Log doesn't seem to point out anything that might be going wrong. So all I have are some guesses of what might be happening (assuming everything is running under the same user with same permissions).

My first hunch is that it's looking for the game under the wrong "battle.net.exe" process (possible but never actually saw it happen), and that can be tested using the latest beta which wouldn't have that issue.

The other hunch would be that cod:bo4 retail added some sort of anti-cheat protection that could interfere with bnetlauncher, which i can't say for sure without having someone confirm bnetlauncher is actually working on the game.

I have no plans to buy a CoD game so can't really test the current release.

[slagliano]

That beta link is broken. It's possible they wouldn't allow overlay but that seems unlikely.

[dafzor]

Sorry about that, I've fixed the link.

[slagliano]

Using that copy of the client fixed the issue! Thank you so much! Love the program bunches.