CrossOver Support - Community Forums

Hello Community,

i just wanted to check if anyone has the same error.

Today i'm not able to start Diablo anymore as the Battle.net Client says there is a update available. When i click on update its starting but end in the following error message:

Something went wrong with a file. We're not sure what caused it, so please try again or click the code below for more information. Sorry about that!
BLZBNTAGT00000840

Yesterday night (or few hours ago) it worked fine so maybe its really a stuck update or another blizzard problem.
I already reinstalled the bottle and the Battle.net client.
Additional i used another version of Diablo IV from a backup which definitly worked in the past.

I Use Crossover 24.0.5.37094
Diablo IV version 2.0.5.60065. (D3D Metal + ESync is enabled)
Mac Book Air M3 16GB
Mac OS 15.2

I just wanted to check if i'm alone or if it's a new beginning of a new Season 7^^

Thank You in advanced
Stefan

Same exact issue (and software versions/settings). I went through a number of steps, such as restarting my computer, re-installing Diablo IV, and deleting and re-installing the bottle but always ending up with the same error.

Same here with D2 and D1. It's a bnet client issue.

Blizzard will have to fix it or Crossover somehow...

Same here did anyone submit a ticket? They need that from people having the issue it lets them track it.

I updated my Mac and wonder if this isn't what caused it - that the AI/ChatGTP function isn't messing with something. Did any of you do the update? I'm going to turn off the the AI and see if that helps.

I don't think its the AI feature.

Until last Sunday i used a Mac Book Air M1 with Sequoia 15.2 and Diablo worked.
Since Monday i use now the M3 Air with Sequoia with deactivated AI.

The chance is high that its a Battle.net related issue as we are not alone.

Cheers

Same thing on my end - stuck at 'Update' on BNet, relative to Diablo 4.

Deleted bottle, re-installed, and BNet couldn't complete with the same error. Stuck for now.

Over on Reddit, folks are having the same or similar problem with NATIVE installs of OSX BNet and OSX-native games.

Leads me to wonder if this is a BNet thing, or an Apple thing...

I turned off my AI, etc. It's a Blizzard thing. I wonder if it is because every time we want to play the game, we always have to click 'Update' (even though there is no update). Blizzard monitors their servers, etc. and I wonder if they don't appreciate the load us Mac players have when using Crossover. I am installing D3 through Battle.Net for Mac to see if I can play the Mac version of D3 to determine if it is a Crossover-Battle.net thing.

Fired up Diablo 3 native in BNet native and it worked fine. Looks like it's a BNet PC + Crossover issue.

I concur. I can play D3 on my Mac via Battle.net Mac native app. It IS a Crossover-Battle.net issue.

I am having exactly the same error. Very frustrating. I purchased the Crossover service specifically to play D4. Are we just stuck now?
Macbook Pro M1 Max, sonoma 14.6.1

I deleted the bottle and am reinstalling the game in an attempt to satiate my D4 needs.

O meu está dando o mesmo problema, ia comprar o software mas pelo visto nao vale a pena

Diablo 2 ressurect
MacStudio

Bradly Helm wrote:

I deleted the bottle and am reinstalling the game in an attempt to satiate my D4 needs.

Did it work? 👀

I'm having a similar issue trying to install d4 on a new Mac that I got and my error is BLZBNTAGT00000854 Im on the latest crossover as well. This used to work fine before so I don't know what is causing this issue now. Hopefully CodeWeavers can figure out what's going on.

This may be a repost (sorry if it is), but they are on it.

https://bsky.app/profile/codeweavers.com/post/3lfsau6jwa22e

I have the same issue, and I think this is not a real update for diablo iv, because I have never seen the update on my windows pc...stuck till now...

Nope. In fact, it won't download past ~30%...the error pops up.

Javo Esquivel wrote:

Bradly Helm wrote:

I deleted the bottle and am reinstalling the game in an attempt to satiate my D4 needs.

Did it work? 👀

Hey all they are working on a fix, that info has been said repeatedly on discord and their other media outlets and posts. Until they fix it nothing we do or try is going to make it work. How about we all give them time to address and solve the problem? :) I want to play my D IV as well but until it’s fixed there is nothing we can do.

See here

I am getting the same error.

Went to my Girlfriends PC and tried it and it works without a problem. Not sure why it works on the PC and not
crossover.

I just tried to download the MAC battle.net and the setup process fails with the same error. I think this is a Blizz problem.

Seeing the same issue on Mac M2, Sequoia, Crossover 24.0.5. Godspeed and good luck, Codeweavers!

Any news ?

Give them the time they just got this ticket and complaints a week or so ago. It takes developers who knows how long to fix the problem. They'll post on Discord or any number of their outlets or here as well. Be patient I don't get why people keep asking for updates or keep saying it doesn't work when trying X,Y,Z. It's broken they are working on it and again have posted this fact on multiple sources. I love this app and want to play my D IV but it's broken all we can do is wait.

I even posted a link above to their Instagram post they put out about the fact they know about it and are working to get it fixed. I have faith they will get it fixed we all just have to be patient.

THİS SOLUTİON WORK FOR ME !!
VİA:MrSniperik from reddit

Last working version: 8916

"Broken for CrossOver" version: 8988

Workaround:

Open CrossOver: If it's not already running, start CrossOver.

Quit the Battle.net client: Make sure the Battle.net client is fully closed.

Locate your Battle.net bottle: In CrossOver, click on the Battle.net bottle.

Access the C: drive: On the right-hand side, under "Bottle Actions", click "Open C: Drive".

Navigate to the Agent folder: Go to ProgramData > Battle.net > Agent.

Check for agent versions: You should see two folders: Agent.8916 and Agent.8988. If you don't, you'll need to obtain the older version (8916) from someone else.

Open the folder in Terminal: Go back one level to the Battle.net folder, right-click the "Agent" folder, and select "New Terminal at Folder".

Delete the broken version: Run the following command in Terminal: rm -r Agent.8988 (Don't worry - if anything goes wrong, the client will re-download it)

Create an empty placeholder file: Run: touch Agent.8988

Make file immutable: Run: chflags uchg Agent.8988 To undo this later, when CrossOver implements a fix, run: chflags nouchg Agent.8988 to remove the flag and allow overwriting the file.

Launch the Battle.net client: Open the client from the Battle.net bottle.

Click "Update" on your game and enjoy it :)

To undo these changes and allow Battle.net to update Agent.exe to version 8988, run the second command from step 10.

If Agent.exe is updated again before CrossOver releases a fix, simply repeat the same process for the newer version. Remember to back up the version that works.

I hope this helps anyone struggling with the issue!

Apparently the most recent version of the Battle.net application will not run in Crossover. Mert Eren's procedure above does this:
1- Restores an earlier version of the Battle.net application which does work in the current version of Crossover.
2- Creates a dummy file with the same name as the newer version of the Battle.net application which prevents a file of the same name from being written to that directory.
3- Changes the dummy file so that it cannot be deleted.

Eventually, that older version of Battle.net will fail to work so an updated version of Crossover is still necessary, eventually. And also needed right now for anyone installing fresh or who otherwise doesn't have the previous version of Battle.net available to restore.

Note also that while Diablo IV does not have an offline play mode and therefore requires Battle.net in order to connect to Blizzard's servers, Diablo II: Resurrected does have an offline play mode and can be launched directly. Use Crossover's RUN COMMAND to the D2R.exe executable in your Diablo II: Resurrected bottle to launch Diablo II: Resurrected directly without running the Battle.net application. Here is the file path:
*/drive_c/Program Files (x86)/Diablo II Resurrected/D2R.exe

Note that you must have run Battle.net and run Diablo II: Resurrected in online play mode at least once within the last 30 days for offline play mode to work.

Mert Eren wrote:

THİS SOLUTİON WORK FOR ME !!
VİA:MrSniperik from reddit

Hey, I appreciate you sharing my solution :)
But I think it's better to share the link to the original post, as it's well-formatted and easier to follow. I'm also answering questions and helping people there.
Link to Temporary Fix on Reddit

Thanks a lot for the workaround, unfortunately I don't have version 8916 as I deleted the bottle, in my attempt to make the game work.
Any idea how or where I could find that version ? Saw on reddit that you can't share it due to possible tos reasons, but maybe you could point me to a direction as to how to get it :)
Thanks again.

leo wrote:

Thanks a lot for the workaround, unfortunately I don't have version 8916 as I deleted the bottle, in my attempt to make the game work.
Any idea how or where I could find that version ? Saw on reddit that you can't share it due to possible tos reasons, but maybe you could point me to a direction as to how to get it :)
Thanks again.

Since there are no DMs on CrossOver forums, you can ask for tips on reddit's DMs ;)

Anyone can share the latest working Agent? Since mine did not have it? Thanks

Same here

experiencing the same issue.

experiencing the same issue.

Have same issue with D2R, using a m2 pro

WORKS!! I found an older Agent.XXXX in a backup. It is not Agent.8916 but Agent.8868 Find me on Reddit (Old_Manufacturer8160), and I will send you a link to download.

Richard Tirtadji wrote:

Anyone can share the latest working Agent? Since mine did not have it? Thanks

https://drive.google.com/file/d/1ffd-fmZW3YO8OrIa3dj6VhERJicsUwbj/view?usp=drive_link

Here is a folder with TWO versions:

https://drive.google.com/drive/folders/1zh0mpvyK9Ngnml9IhJBezKZFIFCPTNHP?usp=drive_link

Works great with old agent. Thanks

So, I ran into this issue in the afternoon of the 14th, which is when the offending battle.net was rolled out. Before I saw that others had the problem, I tried all of the regular fixes. Delete game, attempt reinstall. Delete game and battle.net and attempt to reinstall. When I say attempt, it would fail about 40% during install of game, and although battle net failed with an error, it would still run and allow me to try and install d4.

Then, I tried deleting bottle, and re-installing everything to make sure all the c++libraries from msft were fresh. Irregardless, nothing worked.

HOWEVER. (This is the bad omen mentioned in subject), during one of the attempts to reinstall battle.net, it launched and showed me a yellow caution triangle in the upper right hand corner of app. Clicking on it revealed the omen “this version of battle/net is not compatible with Mac”. In yellow writing there was also a tag line down under neath the update button that stated the same thing, “game not compatible with Mac”

This scare me. Why? Because it means blizzard can tell when they are running in a virtual machine and somehow it can see past the wine/crossover virtual to sense it is on a Mac!!!! This is a huge issue, because MSFT bought Blizzard and if they are trying to keep D4 as a killer app on windows only, not even as a virtual in windows 10 on a Mac, because ? I dunno, they hate Apple…. It could mean they will continue to release versions of battle/net for pc that can sense when they are in a virtual and will refuse to run.

What pisses me off is this. While blizzard sears no support for Msc users, I have never asked for it. Never needed it. Even when running the game porting toolkit with its myriad of installs and settings. YET, my money is still green. They had no problem taking it when I purchased the game years ago. They had no problem taking it when I bought the expansion. I a, sure this is the case for MOST MAC USERS! No support need, but they have paid for it. Translates into pure profit because they do not need to gear up support lines form us lowly mac heads.

If they institute a detection scheme and play cat and mouse we could be waiting for crossover team to fix every single patch update. SO, NOT COOL!!!

in closing, “heads up, Earnie, we’re in for a bummmpy ride!”

The munger

im not sure if we present a load issue when it comes to just being a Mac user. We already know up front (both Blizzard and users) that there will be ZERO support for mac players. This means we still paid for the original game, AND for the season 7 hatred update, AND the upcoming one and they have ZERO overhead cost other than a server port. Pure profit. I think it goes deeper though. Its not just that blizzard doesnt "want" mac players. It's most likely Microsoft protecting their windows gaming niche by trying to keep D4 EXCLUSIVELY on the Windows Platform.

Personally, I got one battle.net installed enough to run, so i went o install d4 (which failed by the way) and I noticed a small yellow warning triangle in upper right corner. At the same time, under the update button with the diablo iv in drop down, there was yellow text that stated "Not compatible with Mac".
I feel like it's an omen and Blizzard is going to start actively blocking mac players!

Also, side note, I found it weird that battle.net KNEW it was on a mac when its running in a walled garden.

Bradly Helm wrote:

Richard Tirtadji wrote:

Anyone can share the latest working Agent? Since mine did not have it? Thanks

https://drive.google.com/file/d/1ffd-fmZW3YO8OrIa3dj6VhERJicsUwbj/view?usp=drive_link

Thanks.. I actually get it from my Win11 Bnet.

Peter Richards wrote:

So, I ran into this issue in the afternoon of the 14th, which is when the offending battle.net was rolled out. Before I saw that others had the problem, I tried all of the regular fixes. Delete game, attempt reinstall. Delete game and battle.net and attempt to reinstall. When I say attempt, it would fail about 40% during install of game, and although battle net failed with an error, it would still run and allow me to try and install d4.

Then, I tried deleting bottle, and re-installing everything to make sure all the c++libraries from msft were fresh. Irregardless, nothing worked.

HOWEVER. (This is the bad omen mentioned in subject), during one of the attempts to reinstall battle.net, it launched and showed me a yellow caution triangle in the upper right hand corner of app. Clicking on it revealed the omen “this version of battle/net is not compatible with Mac”. In yellow writing there was also a tag line down under neath the update button that stated the same thing, “game not compatible with Mac”

This scare me. Why? Because it means blizzard can tell when they are running in a virtual machine and somehow it can see past the wine/crossover virtual to sense it is on a Mac!!!! This is a huge issue, because MSFT bought Blizzard and if they are trying to keep D4 as a killer app on windows only, not even as a virtual in windows 10 on a Mac, because ? I dunno, they hate Apple…. It could mean they will continue to release versions of battle/net for pc that can sense when they are in a virtual and will refuse to run.

What pisses me off is this. While blizzard sears no support for Msc users, I have never asked for it. Never needed it. Even when running the game porting toolkit with its myriad of installs and settings. YET, my money is still green. They had no problem taking it when I purchased the game years ago. They had no problem taking it when I bought the expansion. I a, sure this is the case for MOST MAC USERS! No support need, but they have paid for it. Translates into pure profit because they do not need to gear up support lines form us lowly mac heads.

If they institute a detection scheme and play cat and mouse we could be waiting for crossover team to fix every single patch update. SO, NOT COOL!!!

in closing, “heads up, Earnie, we’re in for a bummmpy ride!”

The munger
I will not worry about us trying to play their game on Mac, since we have to pay for the game anyway and further more you also need to pay for cosmetics etc. That only mean money money money? IF that not considered then Blizzard management is one of the most idiot team in history. Again we are not cheating in fact we have been left behind, even though we willing and able to spend on their game. Just my 0.2 cents

I run Battlenet both under Crossover and Windows 11ARM using Parallels and I never saw a yellow caution message that "this version will not work on macOS" (sorry if I quoted your message incorrectly). So perhaps your error message was caused by something else? Just wondering.

gave this a shot, and still no worky. I do get a different error message, but the end result is the same. Something about battle.net not closing correctly, scan and repair and try again. Well, scan and repair wont even get through all the way and it eventually just dies out with same error message.

I sure hope they are paying some overtime at Codeweavers. I am worried that because it is taking a long time to fix, that this is INDEED tied to Blizzard NOT WANTING D4 to run on mac hardware. If this is the case, there is active code checking if it is running in a bottle. That will not be as easy as throwing a more updated DLL or some other registry entry at the mix to keep it running. As a matter of fact it would probably take an active HACK of Battle.net code to avoid/skip the checks. This would be a giant NO NO for blizzard and they would consider the game pirated and go after the Codeweavers guys for hacking their code. Just because this is BASED on open source stuff with WINE, does not hold it harmless from copyright infringement.

My fingers are crossed! 2 days til new season starts .... cutting it close guys!

It is definitely a battle.net thing. How deep it goes is the question. Was it an innocent change and codeweavers just needs to toss an updated DLL or something into the mix. ORRRRRR, is it active malicious code designed to keep battle.net PC desktop from running in aa virtual on a mac. I feel like it is the later because one of the re-installs I managed to get battle.net installed and running gave me a yellow caution triangle at the top right of the screen with an exclamation point in it. Also below the update button was the text "Not compatible with Mac"

I think Blizzard is actively blocking Mac users, not because of the update "load' (a simnple version check uses so little bandwidth for a few bytes, they probably DON'T even log it.), but because Microsoft bought Blizzard and wants to keep d4 an exclusively PC game. This way it becomes one of their killer apps for windows gaming. MSFT is not going to help Apple do anything, even if the Mx architecture on their chips is far superior. D4 runs better on my M1 Max at full graphics settings than it does on my son's new PC with Nvidia 3090 rtx. Not a good look for MSFT OR Nvidia, a HUGE partner to Microsoft. To further the bad blood between NVIDIA and Apple, remember the 2014 Intel Macbook Pros? Yeah, they had discrete nvidia graphics for when they were plugged in, giving access to CUDA for video editing, etc. Then, one update during the first 6 months of the machines life, Apple unceremoniously dropped support for Nvidia chip on that machine. No mention of it. No updates for the graphics or CUDA moving forward. No ability to download new drivers form Nvidia. I had paid extra for a faster graphics capable Mac, and they just made half the hardware obsolete. I cant be the only one, so Im wondering why there was no class action lawsuit on this?

So, in short, Apple and Nvidia do not like each other AT ALL...and if Nvidia is made to look bad by M1 architecture, and MSFT is in a position to do something for a partner....why not disable D4 on mac? a theory...but pretty sound one.

Like I think I mentioned, that message only came up one time after I managed to get battle.net re-installed. I do have the Mac version of battle.net installed, and checked to make sure it was not the mac version running. I never saw that message again on any of the subsequent many retries. So, glitch in the matrix? Maybe I caught the one instance of battle.net downloaded with the messaging enabled because it downloads battle.net when you just use the exisint bottle recipe from the choices in crossover. WHO KNOW!?

All I am saying is I sure hope they are not doing this, actively blocking....however, it would explain why codeweavers is taking so long to fix this. Usually if it's a change in battle.net where they migrated to a newer library or something for the build, we just need to re-install battle.net to get that new library. Codeweavers would supply it in in the bottle updates. So far though, with NO word from Codeweavers a week later, and 2 days til end of season....this is not a good look for Blizzard OR Codeweavers.

If its Blizzard doing this, people will still get pissed (even though its not officially supported) and hate them even more. If its codeweavers, well, having this happen right by the end of the season is the worst timing in the world. That's my 2 cents.

Some really over the top comments here that are simply disconnected from reality. I know it’s frustrating to not be able to play a game you enjoy but it’s not happening because anyone is out to get Mac users, or Crossover users, or you individually; nor because someone isn’t doing their job properly.

Companies which produce Windows games want to make money and they’re happy to sell to players with Macs. Those companies will usually refuse to offer technical support to players running their games in a non-Windows OS but they will happily take your money and do not purposely change their code so that their games or supporting applications won’t work in the current version of Crossover or some other version of WINE. They do not make any effort to be sure any updates or changes will work with Crossover, though.

This is not the first time that an update to the Battle.net application has broken its ability to run in Crossover on a Mac. No one at Blizzard implemented these changes with the intent of preventing Mac users from playing Blizzard games which require WINE to run in MacOS but neither did anyone at Blizzard give a single moment’s thought or effort to ensuring it would. The Windows version of Battle.net is written for Windows only and the games which require the Windows-only version of Battle.net are written for Windows only.

Crossover specifically and WINE in general are one of the closest things to magic in the world of consumer computing. The ability to run many Windows applications, including high-end graphically intense games with API translation instead of requiring emulation? Amazing! But Crossover cannot run every Windows application and some it can run it does not run well. More importantly, the Codeweavers team has zero control over any changes made to the literally thousands of popular Windows games (among tens of thousands of other applications) that people play using Crossover on their Macs so any application that is running TODAY could stop working TOMORROW as a result of a change to MacOS by Apple or a change to the Windows application by that application’s developer.

When that happens to a popular Windows application, Codeweavers immediately puts effort into updating Crossover so that said Windows application can once again run in Crossover on Macs. Sometimes this is an easy fix and takes hours to days to accomplish. Sometimes it’s harder and takes days to weeks. Sometimes that application requires so many changes to Crossover that the “fix” doesn’t become available until the next full version of Crossover is released. And sometimes it’s just not possible for an application to work in Crossover, even an application that used to work in Crossover before some change to MacOS or that application occurred.

Game companies want your money. Crossover wants to keep its customers happy. But most game companies are simply trying to make their products as good as possible for their main customer base which runs Windows OS on PCs and sometimes when they do that their applications stop working with the current version of Crossover. And Codeweavers cannot and does not guarantee that any individual Windows application will work or will continue to work in Crossover on a Mac, even though they do their best to make Crossover as generally useful as possible for a wide variety of Windows applications and put special effort into supporting the most popular Windows games.

Try to be patient. And reasonable. No one is out to get you, Crossover users, or Mac users.

John,

"Codeweavers team has zero control over any changes made to the literally thousands of popular Windows games (among tens of thousands of other applications) that people play using Crossover on their Macs so any application that is running TODAY could stop working TOMORROW as a result of a change to MacOS by Apple or a change to the Windows application by that application’s developer." -- VERY Well Said!

I've been trying to get this very message out to users in other new posts about D IV. What I'm trying to squash out with common sense is met with more users acting as if this is Codeweavers fault and it should be fixed in a few hours.

I try to keep reiterating that it's kind of like a visit to a hospital (forgive this analogy but I'm a former Army Medic and it makes sense to me). You go there because something is wrong. Before you even get into the ER you are triaged to find your place in the queue (say this for the battle.net problem and its place in the priority list)

Second, you are sent back for your vitals (Codeweavers examining how Crossover is working in this situation), You may be sent back to the waiting room (not a high priority) or you may be sent back to a bed in the ER (high priority). Next vitals are taken and tests are done (blood, x-ray, whatever the test may be) This is Codeweavers probing the problem but not acting full force yet because they need results for their observation. Once the tests and diagnostics are done they can work on curing the problem. (you getting given to a specialist or doctor).

I used this analogy in another post to try to K.I.S.S. so people can think differently and not just expect them to have a fix right away. So thank you for your post I hope people read it and digest it :)

Two observations. First I believe the people frustrated with CodeWEAVERS have a right to be frustrated with the company. You have stated that Battle.net has had many times that it has broken the ability to play pc games on the battle.net platform. I have owned D4 since launch. Codeweavers did not add D4/Battle.net to its list of supported apps until a few months into the game's launch and after the Apple crew game out with the Game Porting Toolkit. In which case, support for D4 was free and pretty simple to setup if you had any knowledge of manipulating a few system files.

Getting to my point, Codeweavers added the same functionality into CrossOver. A lot of Mac users, whether they wanted to make life a little easier, or they didn't know how to install GPTK with all the time it takes and the commands from the CLI, they plunked down the $35 bucks (or whatever it was) to do JUST THAT! Click, install...launch. Also to my second point, in that time that Codeweavers had supported D4 on crossover, there has been EXACTLY ONE OTHER TIME that Battle.net did not work due to an update. That time, there was an easy fix by using a different version of battle.net to launch. This worked for a couple of days. The fix the new Battle.net
(a new build of C.O.) for it came out in a day or so. Hence the next version of Crossover was born.

The minute Codeweavers takes money for something that can pretty much be done for free (and I am talking about running D4 on a MAC built on the WINE subsystem (an open source system that is touted as being open source on their website) THEY ENTERED a contract with end users to keep that system in the same state as what we paid for. working, simple, and something we don't need to think about! Use whatever metaphors you want, gas lighting, entitlement, etc.... none of those apply when money has been exchanged. In that vein, none of the comments I have seen are any worse than the vitriol on other forums. Trying to light a fire under a developers butt on a 3 day weekend is not beyond expectation. Esp when that weekend coincides with a major event on the game that was literally a massive boon to the bottom line for Blizzard AND Codeweavers. Tell me sales didn't go through the roof when they announced support for D4 after having people as innocuous to computer tech as Whoopi Goldberg doing a little sniping on her national TV show to Blizzard for a Mac version (I assume for a relative in the family...although, maybe she plays, who knows.)

Considering the amount of information given to Codeweavers about the new version, and exactly WHEN it caused the issue, I am quite surprised their testing and Quality control systems in house wouldn't be able to nail down EXACTLY what has changed. I am quite sure there is a dev in house that has the sole job of reverse engineering battle.net, steam and other pc exes that represent a large portion of revenue for the company. This is why I am personally making comments (and they are only comments, not proven fact) that based on what I know about dev after 40 years of writing code, this is smells an awful lot like Blizzard is giving a giant middle finger to mac users. You can edit the battle.net exe or that would be a massive legal issue with Blizzard, so creating a trap or a outside system to respond to whatever battle.net is doing to check the system it is on, appears to be fairly robust. Rember, this is NOT happening on PC's. I tested this myself by installing a brand new install on a low end pc just to see if it would install and run. Spoiler alert, it installed and ran fine. soo......

So, we are ready to go!

https://bsky.app/profile/codeweavers.com/post/3lgb67m2xfc2q