[Bug]: Diablo IV / Battle.net stuck in updating loop

[puja108]

Description

Just to I installed Whisky 1.0.1 (I'm on an MBP M2 Pro) and let it download Wine and linked it up with GPTK 1.0.2. Battle.net installed fine (changed the Win 10 version in registry) and after doing the DXVK dance (enabling, disabling hardware acceleration in the launcher, disabling) the No GPU error also dissapeared (with Esync on). I've folllowed all closed issues including https://github.com/IsaacMarovitz/Whisky/issues/198#issuecomment-1618979646

Once I click on start, DIV tries to update, and then it's back at a stopped game. Similarly the freshly downloaded Battle.net says there's an update available, but there's not.

I first thought it might be battle.net servers, but on my Windows Desktop it works fine.

Steps to reproduce

1. Install Whisky 1.0.1 with GPTK 1.0.2
2. Install battle.net
3. Do all the shebang mentioned in the closed issues
4. get stuck in update loop

Expected behaviour

start the game

Logs

Whisky Version: 1.0.1
Date: 8.7.2023, 18:39:26
macOS Version: Version 13.4.1 (Build 22F82)
Bottle Name: Battlenet
Wine Version: 7.7.0
Wine Binary Version: 4
Windows Version: win10
Bottle URL: /Users/puja/Library/Containers/com.isaacmarovitz.Whisky/Bottles/73214D43-3008-41C6-84BA-1C3C2BF2CC29

Arguments: start C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe 

Launched Wine (20966)
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
rface v1
		VK_EXT_pipeline_creation_cache_control v3
		VK_EXT_post_depth_coverage v1
		VK_EXT_private_data v1
		VK_EXT_robustness2 v1
		VK_EXT_sample_locations v1
		VK_EXT_scalar_block_layout v1
		VK_EXT_separate_stencil_usage v1
		VK_EXT_shader_atomic_float v1
		VK_EXT_shader_stencil_export v1
		VK_EXT_shader_viewport_index_layer v1
		VK_EXT_subgroup_size_control v2
		VK_EXT_surface_maintenance1 v1
		VK_EXT_swapchain_colorspace v4
		VK_EXT_swapchain_maintenance1 v1
		VK_EXT_texel_buffer_alignment v1
		VK_EXT_texture_compression_astc_hdr v1
		VK_EXT_vertex_attribute_divisor v3
		VK_AMD_gpu_shader_half_float v2
		VK_AMD_negative_viewport_height v1
		VK_AMD_shader_image_load_store_lod v1
		VK_AMD_shader_trinary_minmax v1
		VK_IMG_format_pvrtc v1
		VK_INTEL_shader_integer_functions2 v1
		VK_GOOGLE_display_timing v1
		VK_MVK_macos_surface v3
		VK_MVK_moltenvk v37
		VK_NV_fragment_shader_barycentric v1
		VK_NV_glsl_shader v1
[mvk-info] Created VkInstance for Vulkan version 1.1.0, as requested by app, with the following 2 Vulkan extensions enabled:
		VK_KHR_surface v25
		VK_EXT_metal_surface v1
04b8:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems
0514:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems
05bc:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems
05bc:err:ntlm:ntlm_LsaApInitializePackage no NTLM support, expect problems
libc++abi: 0264:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems
0994:err:winediag:ntlm_check_version ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.

What version of Whisky are you using?

1.0.1

What version of macOS are you using?

Ventura (macOS 13)

Issue Language

• [X] Yes my issue is written in English

[DCGlc]

The same problem, and after I try many times, I will occasionally enter the game, and then the game will suddenly exit, or a data error dialog box will pop up directly "Diablo IV detected corrupted data and was unable to automatically repair the damage. Please run Scan and Repair using the Battle.net Application. It can be found in the Options menu for the game.” The game doesn’t work at all.

[Madoc439]

I can confirm the same behavior.

[sethmackay]

same here, did anyone solve this issue?

[jakuzure]

same here, did anyone solve this issue?

not yet, but I think it might have something to with the Battle.net launcher wanting to update but failing to do so. at least mine shows there's an outstanding update, but restarting to install the update fails. I read in another issue (that I can't find right now unfortunately) that they tried to run a temp****.exe file that shows up in the battle.net folder and they could somehow upgrade through that, but it doesn't work for me

[ondrejmirtes]

I've had this problem and Diablo 4 started working for me after I turned on ESync. (I'm running through Crossover, not Whisky, but I think this fix is relevant anyway.)

Battle.net still shows Update Available anyway, but that doesn't seem to cause problems for now.

[jakuzure]

I've had this problem and Diablo 4 started working for me after I turned on ESync. (I'm running through Crossover, not Whisky, but I think this fix is relevant anyway.)

Battle.net still shows Update Available anyway, but that doesn't seem to cause problems for now.

that was it, works for me now! thanks for the tip

[Mayuqi-crypto]

Download battle.net in windows and copy the program directory to whisky directly

[Madoc439]

Download battle.net in windows and copy the program directory to whisky directly

I attempted this without success.

[sethmackay]

I've had this problem and Diablo 4 started working for me after I turned on ESync. (I'm running through Crossover, not Whisky, but I think this fix is relevant anyway.) Battle.net still shows Update Available anyway, but that doesn't seem to cause problems for now.

that was it, works for me now! thanks for the tip

I got a graphics utilization failed this time.ughh

[IsaacMarovitz]

Following the steps in the FAQ should resolve these problems

[danderosa]

Attempted the steps in the FAQ w/o any success it continues to loop through updating. Any other recommendations?

[htappen]

For those still stuck with this issue, you can resolve it by using an earlier version of the Game Porting Toolkit from Apple.

Make sure to download "Game_porting_toolkit_beta.dmg" (the first version, not beta 2 or 3)

If you already have Whisky installed, you can remove the existing installation by deleting "~/Library/Application Support/com.isaacmarovitz.Whisky/Libraries/*"

[Mrblutziii]

@htappen After installing the first beta instead of toolkits 2 or 3, I am still getting an "update and restart" for the launcher issue. When I click it to restart and update, it disappears and never comes back.

[htappen]

You don’t need to do the Battle.net update. Just press Play on Diablo IV and wait. It will show up with the same “Updating” thing, but the Diablo IV window should pop up in about 30 seconds

On Sun, Aug 6, 2023 at 3:23 PM Mrblutziii @.***> wrote:

@htappen https://github.com/htappen After installing the first beta instead of toolkits 2 or 3, I am still getting an "update and restart" for the launcher issue. When I click it to restart and update, it disappears and never comes back.

— Reply to this email directly, view it on GitHub https://github.com/IsaacMarovitz/Whisky/issues/224#issuecomment-1666981430, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABF7MVPOOJDKCGTE76XJ7ODXUAKNHANCNFSM6AAAAAA2C6IX7U . You are receiving this because you were mentioned.Message ID: @.***>

-- Thanks, Henry

[Mrblutziii]

Im primarily trying to get overwatch to work. But it continuously crashes and I thought it was because of the launcher update issue

[Hyde7548]

I saw that you reopened this issue. It indeed happens again for all Whisky versions >= 1.0 (Esync activated etc...). However, reverting to 0.3.1 resolves the issue, maybe that can help you narrow it down.

[IsaacMarovitz]

Superceeded by #554