#273 wine 7.3 staging broken with genshin?

So I've been trying to update to wine 7.3 and I've been having a massive headache with it, whenever I launch genshin with 7.3 staging I end up getting wine: Call from 000000007B0139D8 to unimplemented function combase.dll.RoSetErrorReportingFlags, aborting It's not always exactly that but its always wine: call from <address> to unimplement function combase.dll.RoSetErrorReportingFlags, aborting I'm not sure if its just me (im using a custom staging wine because it's the same wine I've been using to run roblox and it works fine. If you want to test youself I have the exact 7.3 pacman file if you want to install it and try it on your system (if you revert back to the previous wine version you were using it should start working again) https://www.dropbox.com/s/6x7ybqocsvy4fmq/wine-tkg-staging-fsync-git-7.3.r1.g8c4c65ff-326-x86_64.pkg.tar.zst?dl=0

Just if your wondering, I'm using a seperate wine version between roblox and genshin so it doesnt have the roblox mouse patch but I was saying I'm using a special staging version of wine and full log: https://hastebin.skyra.pw/tifeniyigu.pgsql

It's not just you, I also have the same problem using wine-tkg 7.3 -- wine-proton-tkg by extension. And it spews the exact same error message, which is wine: Call from 000000007B0138C8 to unimplemented function combase.dll.RoSetErrorReportingFlags, aborting. Also, here's the log in case anyone needs it.

@chocomint hmm, I wonder if it’s just that wine 7.3 staging works weirdly with Genshin and refuses to work?

You could try to re-create the WINEPREFIX or update it using wineboot -u. I however doubt that it will solve this issue.

Such errors are usually uncovered by other functions which unlock code that was previously skipped. @ stub functions cause Wine to abort immediately. RoSetErrorReportingFlags currently has no implementation. The easiest solution is to use an older Wine version, or to wait for an upcoming version to implement this function.

I could yet not find any Bugzilla entry but will file one if WINEPREFIX re-creation/update does not help.

@Krock yes, these are all steps I have tried to get wine 7.3 staging using these methods but it didn’t seem to work, so I’m not sure if it’s just that wine 7.3 staging is broken with Genshin but I’m not sure.

I reinstalled wine-tkg and it seems to work now? What I did differently this time was I installed the wine-tkg using makepkg -si from the wine-tkg-git and not the proton-tkg.

Edit: I also pulled the latest version from wine-tkg-git

@chocomint yeah, it seems recently it started working again, strange.

Mind re-opening this? I have the same exact issue with wine 7.3-vanilla/staging, 7.4-vanilla/staging, and 7.5-vanilla/staging. The thing is that I use winehq's debian package for such and not whatever wine/proton-tkg is.

Here's a stacktrace with non working wine-staging 7.5 https://freenote.biz/YSHjAX0ofb And here's a stacktrace with working wine-staging 7.2 https://freenote.biz/HXUKq6J5pP

Each one is killed right before/on the opening logo, which doesn't even open any windows or initiate the gpu on wine-staging 7.5

@servtestator123 My first guess ihis is due to a partially broken wineprefix.

1. Create a new wineprefix: WINEPREFIX=/absolute/path/to/new/directory wineboot -u
2. Install or update winetricks: winetricks --self-update
   • EDIT2: skip steps 2 and 3 if you're using the Nouveau driver
3. Install DXVK 1.10 via winetricks: WINEPREFIX=/same/path/again winetricks dxvk1100
4. Re-test using the new wineprefix

Good luck.

EDIT3: If the new wineprefix suffers results in the same error, I will submit a new entry on BugZilla so that this function is implemented someday.

EDIT4: The original reported RoSetErrorReportingFlags error is solved since Wine 7.4, however there are many other errors in your log.

Clean wineprefix fixed it, tyvm.

So updating to wine 7.3+ requires a prefix update from what I’ve experienced and what servtestator123 has experienced might be something worth noting

Thank you for the feedback. The solution is documented since 6980bb3.

Feel free to comment here in case this workaround needs revising.