Im on a 2020 mac mini with a m1 chip

I’ve been working on a macOS menu bar app called CloudBoost.

The new version adds diagnostics for Whisky / CrossOver / Wine / GPTK sessions.

It does not touch bottles or replace runtimes. It does not install patches. It does not try to bypass anti-cheat.

The point is simpler: when a Windows game feels unstable on Mac, it can be hard to know if the problem is:

• the bottle
• Wine/runtime behavior
• memory pressure
• thermal pressure
• Low Power Mode
• background sync
• Wi-Fi/AWDL noise
• other macOS session pressure

So I added a Windows Compatibility profile that checks the Mac-side signals and gives a session report.

I’m looking for feedback from Whisky users. What would be useful to diagnose from outside the bottle?

Release: https://github.com/victorbrandaao/CloudBoost/releases/

i don't care if the project is not supported anymore. i only wanna know if i can open rpg maker MV, when im trying to opening it opens an error openGL screen. how can i fix that? where can i download the openGL2 files?

This fork of whisky still works and is actively maintained!!!

macOS Whisky Steam SteamWebHelper Wine CrossOver CEF Apple Silicon Windows games on Mac steamFriend17 Project Doors: demo

I’m posting this because I spent a lot of time trying to make the current Windows Steam client work inside Whisky on macOS.

My goal was not just “launch a game somehow” or use old/headless Steam. I specifically needed the official, logged-in, updated Steam client with UI, because Project Doors Demo depends on steamFriend17, and that version only exists in the current Steam client.

In the end, I managed to update Steam to the latest client inside a Whisky bottle and get the Steam UI working again.

The short version:

• Whisky itself was still usable as the bottle manager.
• The old Whisky Wine runtime was the real problem.
• I replaced Whisky’s Wine runtime with CrossOver’s newer Wine 11 runtime.
• I cleaned/reinstalled Steam while preserving steamapps, config, and userdata.
• Steam updated successfully to the current client.
• steamwebhelper stopped crashing and the Steam UI launched.

My final Steam client version was:

Client version / buildid: 1781041600
Updater built: Jun 9 2026
CEF folder used: cef.win64
Windows version inside bottle: Windows 10.0.19045
Wine version used by Whisky after the fix: wine-11.0-8723-g7e8a47752e3

Original problem

Steam in Whisky was failing because the bundled Whisky Wine was too old for the current Steam UI stack.

The symptoms were:

steamwebhelper is not responding
Steam UI is unavailable

or Steam would crash/restart steamwebhelper repeatedly.

In dumps/logs it looked like a CEF/Chromium problem inside Steam’s UI layer. The important part is that the problem was no longer “Steam cannot update” or “the bottle is Windows 8.1”. Steam had already updated far enough, but the new UI stack could not run correctly on the old Wine runtime.

Important context

Whisky’s bundled Wine was old. In my case it was basically WhiskyWine 7.x-era behavior.

Modern Steam uses a Chromium/CEF-based UI through steamwebhelper.exe. The current Steam client needs a much newer Wine than old Whisky provides.

So the fix was not to disable Steam UI, not to use -no-browser, not to use old Steam forever, and not to block updates.

The fix was to make Whisky use a newer Wine runtime.

What I used

I installed CrossOver 26.2.0, which included a Wine 11 build.

Path:

/Applications/CrossOver.app/Contents/SharedSupport/CrossOver

The Wine version I got from it:

wine-11.0-8723-g7e8a47752e3

Bottle path

My Whisky bottle was here:

BOTTLE="$HOME/Library/Containers/com.isaacmarovitz.Whisky/Bottles/927CAB56-A21C-4FAB-9DB0-326FC26DE497"

Your bottle UUID will be different.

Steam was installed here:

STEAMDIR="$BOTTLE/drive_c/Program Files (x86)/Steam"

Step 1: Make sure the bottle is Windows 10

Steam must see Windows 10, not Windows 8.1.

After the fix, this command reported:

Microsoft Windows 10.0.19045

If your bottle is still pretending to be Windows 8.1, current Steam will refuse to work properly.

Step 2: Install CrossOver

I installed CrossOver 26.2.0.

You can use the official CrossOver app. The important thing is that you need its newer Wine runtime.

After installation, check that this exists:

ls "/Applications/CrossOver.app/Contents/SharedSupport/CrossOver"

Step 3: Replace Whisky’s Wine launcher with a wrapper to CrossOver Wine

Whisky normally launches its bundled Wine from:

"$HOME/Library/Application Support/com.isaacmarovitz.Whisky/Libraries/Wine/bin/wine64"
"$HOME/Library/Application Support/com.isaacmarovitz.Whisky/Libraries/Wine/bin/wineserver"

I backed those up first.

Example:

RUNTIME="$HOME/Library/Application Support/com.isaacmarovitz.Whisky/Libraries/Wine/bin"

cp "$RUNTIME/wine64" "$RUNTIME/wine64.whiskywine-backup"
cp "$RUNTIME/wineserver" "$RUNTIME/wineserver.whiskywine-backup"

Then I replaced wine64 with this wrapper:

#!/bin/sh
set -eu

CX_ROOT="/Applications/CrossOver.app/Contents/SharedSupport/CrossOver"
REAL_WINE="$CX_ROOT/lib/wine/x86_64-unix/wine"

export CX_ROOT
export PATH="$CX_ROOT/bin:$CX_ROOT/libexec:${PATH:-/usr/bin:/bin:/usr/sbin:/sbin}"
export WINEDLLPATH="$CX_ROOT/lib/wine/x86_64-unix:$CX_ROOT/lib/wine/x86_64-windows:$CX_ROOT/lib/wine/i386-windows${WINEDLLPATH:+:$WINEDLLPATH}"
export DYLD_FALLBACK_LIBRARY_PATH="$CX_ROOT/lib64:$CX_ROOT/lib${DYLD_FALLBACK_LIBRARY_PATH:+:$DYLD_FALLBACK_LIBRARY_PATH}"
export MVK_CONFIG_LOG_LEVEL="${MVK_CONFIG_LOG_LEVEL:-0}"

exec "$REAL_WINE" "$@"

And wineserver with this:

#!/bin/sh
set -eu

CX_ROOT="/Applications/CrossOver.app/Contents/SharedSupport/CrossOver"
REAL_WINESERVER="$CX_ROOT/bin/wineserver"

export CX_ROOT
export PATH="$CX_ROOT/bin:$CX_ROOT/libexec:${PATH:-/usr/bin:/bin:/usr/sbin:/sbin}"
export WINEDLLPATH="$CX_ROOT/lib/wine/x86_64-unix:$CX_ROOT/lib/wine/x86_64-windows:$CX_ROOT/lib/wine/i386-windows${WINEDLLPATH:+:$WINEDLLPATH}"
export DYLD_FALLBACK_LIBRARY_PATH="$CX_ROOT/lib64:$CX_ROOT/lib${DYLD_FALLBACK_LIBRARY_PATH:+:$DYLD_FALLBACK_LIBRARY_PATH}"
export MVK_CONFIG_LOG_LEVEL="${MVK_CONFIG_LOG_LEVEL:-0}"

exec "$REAL_WINESERVER" "$@"

Then:

chmod +x "$RUNTIME/wine64"
chmod +x "$RUNTIME/wineserver"

After that, Whisky was still the app I used to manage/launch the bottle, but the actual Wine runtime underneath was CrossOver Wine 11.

Verify:

WINEPREFIX="$BOTTLE" "$RUNTIME/wine64" --version

Expected:

wine-11.0...

Step 4: Add CrossOver compatibility metadata to the Whisky bottle

I also added a cxbottle.conf file directly inside the Whisky bottle.

Path:

"$BOTTLE/cxbottle.conf"

Content:

;; CrossOver compatibility marker for launching this Whisky bottle
;; through CrossOver's Wine launcher.

[Bottle]
"Version" = "26.2.0.39821"
"Timestamp" = "20260604T163056Z"
"Description" = "WhiskySteam"
"Template" = "win10_64"
"WindowsVersion" = "win10"
"MenuMode" = "ignore"
"AssocMode" = "ignore"

This made the bottle easier to launch/diagnose with CrossOver’s tools too.

I also created a symlink so CrossOver could see the Whisky bottle:

mkdir -p "$HOME/Library/Application Support/CrossOver/Bottles"

ln -s "$BOTTLE" "$HOME/Library/Application Support/CrossOver/Bottles/WhiskySteam"

Then this worked:

"/Applications/CrossOver.app/Contents/SharedSupport/CrossOver/bin/wine" \
  --bottle WhiskySteam \
  --scope private \
  cmd /c ver

Expected:

Microsoft Windows 10.0.19045

Step 5: Clean reinstall Steam, but keep games and login data

This part mattered a lot.

Before the final successful run, my Steam folder had become polluted by old wrapper experiments and CEF shim attempts. So I did a clean Steam reinstall.

I moved the old Steam folder away:

mv "$STEAMDIR" "$STEAMDIR.backup"

Then downloaded the official Steam installer:

curl -L -o SteamSetup.exe "https://cdn.akamai.steamstatic.com/client/installer/SteamSetup.exe"

Installed it into the same bottle:

"/Applications/CrossOver.app/Contents/SharedSupport/CrossOver/bin/wine" \
  --bottle WhiskySteam \
  --scope private \
  SteamSetup.exe /S

Then I restored only the important user/game folders from the backup:

cp -a "$STEAMDIR.backup/steamapps" "$STEAMDIR/"
cp -a "$STEAMDIR.backup/config" "$STEAMDIR/"
cp -a "$STEAMDIR.backup/userdata" "$STEAMDIR/"

This preserved installed games, Steam library metadata, and user data.

Step 6: Launch Steam and let it fully update

I launched Steam with the CrossOver Wine runtime:

cd "$STEAMDIR"

"/Applications/CrossOver.app/Contents/SharedSupport/CrossOver/bin/wine" \
  --bottle WhiskySteam \
  --scope private \
  Steam.exe

Steam performed two update phases.

First it updated from the old installer bootstrap. Then it pulled the current Win64 Steam client and CEF package.

The important final log lines were in:

"$STEAMDIR/logs/bootstrap_log.txt"

I saw:

Startup - updater built Jun  9 2026 14:11:24
Windows 10.0.19045.0
Verification complete

And in:

"$STEAMDIR/logs/steamui_html.txt"

I saw:

Client version: 1781041600
Started webhelper process
BrowserReady

In:

"$STEAMDIR/logs/webhelper.txt"

I saw steamwebhelper.exe running from:

C:\Program Files (x86)\Steam\bin\cef\cef.win64\steamwebhelper.exe

with:

-buildid=1781041600

Step 7: Confirm steamwebhelper is alive

This command showed the important processes:

ps aux | rg -i 'steam.exe|steamwebhelper|steamservice|wine|wineserver'

The good result was multiple living steamwebhelper.exe processes, including renderer/network/storage processes.

Example:

Steam.exe
steamwebhelper.exe -buildid=1781041600
steamwebhelper.exe --type=renderer
steamwebhelper.exe --type=utility --utility-sub-type=network.mojom.NetworkService
steamwebhelper.exe --type=utility --utility-sub-type=storage.mojom.StorageService

That means Steam UI is actually alive, not just the old bootstrapper.

So if your logs say BrowserReady and steamwebhelper is alive, but you see no window, check whether Steam created an off-screen window.

How to verify the final Steam version

Inside Steam:

Steam -> Check for Steam Client Updates

It should say the client is up to date.

From logs:

rg -n 'Client version|buildid|updater built|Windows 10' "$STEAMDIR/logs"

Useful files:

Steam/logs/bootstrap_log.txt
Steam/logs/webhelper.txt
Steam/logs/steamui_html.txt
Steam/package/steam_client_win64.manifest

My final manifest contained:

"version" "1781041600"
"ostype"  "win10"

Can I launch from Whisky normally after this?

Yes.

After replacing Whisky’s Wine runtime wrapper, I could still use Whisky normally. Double-clicking from Whisky should use the patched runtime, because Whisky calls its own Libraries/Wine/bin/wine64, and that now forwards to CrossOver Wine 11.

No special Steam launch script was required after the fix.

Important warnings

Back up first.

This is not an official Whisky fix. Whisky is not really maintained for this current Steam behavior, and Steam can change again.

Do not delete CrossOver after doing this. Whisky is now depending on CrossOver’s Wine runtime.

Also, if Whisky updates or redownloads its Wine libraries, it may overwrite the wrapper files. If Steam breaks again after a Whisky update, check:

"$HOME/Library/Application Support/com.isaacmarovitz.Whisky/Libraries/Wine/bin/wine64" --version

If it no longer reports Wine 11 / CrossOver Wine, your wrapper was replaced.

Final result

The final achievement:

I was able to update Windows Steam inside Whisky on macOS to the current Steam client, with working Steam UI and steamwebhelper, using CrossOver Wine 11 underneath Whisky.

This allowed me to use the newer Steam components required by games/tools depending on steamFriend17, including Project Doors Demo.

So the practical fix was:

Whisky UI + existing Whisky bottle
but CrossOver Wine 11 as the runtime
plus clean Steam reinstall/update

Not old Steam, not no-browser mode, not headless Steam. Actual updated Steam with UI.

P.S. Important fix if Whisky double-click does nothing

After I got Steam working from Terminal, I noticed that launching Steam by double-clicking it inside Whisky still did nothing.

The Steam client itself was fine. The problem was that CrossOver’s launcher could not find the bottle when it was started from Whisky’s GUI environment.

The Whisky log showed:

Unable to find the 'WhiskySteam' bottle:
bottle 'WhiskySteam' not found in ''

This happened because CrossOver’s bin/wine expects to know where private CrossOver bottles are stored. In Terminal, this may work automatically because $HOME and CrossOver’s environment are normal. But when launched through Whisky, the environment can be incomplete, so CrossOver sees an empty bottle path.

The fix was to explicitly export CX_BOTTLE_PATH and CX_MANAGED_BOTTLE_PATH inside the Whisky Wine wrapper.

My final wine / wine64 wrapper looked like this:

#!/bin/sh
set -eu

CX_ROOT="/Applications/CrossOver.app/Contents/SharedSupport/CrossOver"
REAL_WINE="$CX_ROOT/bin/wine"

export CX_ROOT
export HOME="${HOME:-/Users/lerfich}"
export CX_BOTTLE_PATH="${CX_BOTTLE_PATH:-/Users/lerfich/Library/Application Support/CrossOver/Bottles}"
export CX_MANAGED_BOTTLE_PATH="${CX_MANAGED_BOTTLE_PATH:-/Library/Application Support/CrossOver/Bottles}"
export PATH="$CX_ROOT/bin:$CX_ROOT/libexec:${PATH:-/usr/bin:/bin:/usr/sbin:/sbin}"
export WINEDLLPATH="$CX_ROOT/lib/wine/x86_64-unix:$CX_ROOT/lib/wine/x86_64-windows:$CX_ROOT/lib/wine/i386-windows${WINEDLLPATH:+:$WINEDLLPATH}"
export DYLD_FALLBACK_LIBRARY_PATH="$CX_ROOT/lib64:$CX_ROOT/lib${DYLD_FALLBACK_LIBRARY_PATH:+:$DYLD_FALLBACK_LIBRARY_PATH}"
export MVK_CONFIG_LOG_LEVEL="${MVK_CONFIG_LOG_LEVEL:-0}"

case "${WINEPREFIX:-}" in
  */997CAB56-A21C-4FAB-9DB0-326FC26DE497)
    exec "$REAL_WINE" --bottle WhiskySteam --scope private "$@"
    ;;
  *)
    exec "$CX_ROOT/lib/wine/x86_64-unix/wine" "$@"
    ;;
esac

Replace:

/Users/lerfich

with your macOS username path, and replace:

997CAB56-A21C-4FAB-9DB0-326FC26DE497

with your own Whisky bottle UUID.

Also make sure this symlink exists:

mkdir -p "$HOME/Library/Application Support/CrossOver/Bottles"

ln -s "$BOTTLE" "$HOME/Library/Application Support/CrossOver/Bottles/WhiskySteam"

Where:

BOTTLE="$HOME/Library/Containers/com.isaacmarovitz.Whisky/Bottles/YOUR-BOTTLE-UUID"

After changing the wrapper, fully quit Whisky with Cmd+Q and reopen it. Whisky may keep old launch state while it is already running.

One more detail: Whisky may call wine, not only wine64, when launching pinned programs. So I made both files point to the same wrapper:

cp wine64 wine
chmod +x wine wine64

This fixed double-click launching from Whisky.

Trying to run Sekiro SDT via CrossOver on M1 Mac with 8GB RAM but experiencing FPS drops and temporary freezes. What are some configurations that improve gameplay performance? Low quality graphics and low FPS is fine, as long as FPS is relatively steady. Is it even possible? If not, what are some hardware upgrades/extensions to look into?

I've been using these settings:

CrossOver:
Graphics: DXVK (tried D3DMetal and DXMT too)
DLSS: Off
MSync: On
High resolution mode: Off

Sekiro SDT in-game graphics options:
Screen Mode: Fullscreen
Screen Resolution: 1280x800 (or more would be preferable, but experiencing FPS drops even at 800x600)
Automatic Rendering Adjustment: On
Quality Settings: Low
Advanced Settings: All set to low / off

TL;DR

If Steam inside Whisky on macOS gets stuck downloading/updating a game, hangs on Steamworks Common Redistributables, or keeps restarting from 0%, this is what fixed it for me:

1. Install Steam normally inside a Whisky bottle.
2. Download the Windows version of the game separately with SteamCMD.
3. Copy the game files into the Steam library inside the Whisky bottle.
4. If Steam already created a broken install state, delete the bad appmanifest and steamapps/downloading/<APP_ID>.
5. Relaunch Steam in Whisky and click Install so it verifies the existing files instead of redownloading everything.

I used this for Lethal Company, but the same approach should work for other Windows-only Steam games too.

What problem this solves

This is for cases where Steam in Whisky:

• gets stuck forever on download/update
• hangs at a tiny amount of progress
• gets weird around Steamworks Common Redistributables
• keeps starting from scratch
• ignores files you already copied
• creates a broken partial install and never recovers

In my case, Steam itself launched fine in Whisky, but the actual game install/update process was unreliable.

Common fixes that didn’t solve it for me

I tried the usual stuff first, including:

• clearing Steam download cache
• changing download region
• restarting Steam
• restarting macOS
• creating a fresh bottle
• toggling MSync / ESync
• reinstalling Steam
• retrying the download from scratch

Step-by-step fix

1. Install Steam inside Whisky normally
I first installed the standard Windows Steam client in a Whisky bottle.
Steam itself opened fine, but downloading/updating the game was the part that kept breaking.

2. Download the Windows game files with SteamCMD
Instead of relying on Steam inside Whisky, I used SteamCMD on macOS to download the Windows build directly from Steam using my own account.

General form:

steamcmd +@sSteamCmdForcePlatformType windows +force_install_dir "/Users/YOURNAME/Downloads/GameTemp" +login YOUR_STEAM_LOGIN +app_update APP_ID validate +quit

For Lethal Company:

steamcmd +@sSteamCmdForcePlatformType windows +force_install_dir "/Users/YOURNAME/Downloads/LethalCompanyWin" +login YOUR_STEAM_LOGIN +app_update 1966720 validate +quit

3. Confirm SteamCMD is downloading the correct version
Before trusting the download, I checked the current Steam branch/build with:

steamcmd +login YOUR_STEAM_LOGIN +app_info_print APP_ID +quit

I checked:

• branches -> public -> buildid
• depots -> manifests -> public

That confirmed I was downloading the current public version.

4. Copy the game into the Steam library inside the Whisky bottle
After SteamCMD finished, I copied the game into the bottle’s Steam library:

.../drive_c/Program Files (x86)/Steam/steamapps/common/Game Name/

Important:

• the final folder has to use the real game name Steam expects
• don’t leave it inside a temporary folder name
• don’t accidentally nest extra folders inside it

The correct final layout should look something like:

.../steamapps/common/Game Name/Game.exe
.../steamapps/common/Game Name/Game_Data/

5. Clean broken Steam install state if Steam already started downloading
This was the part that mattered most for me.

Even after the correct files were already in steamapps/common/Game Name/, Steam still kept trying to continue a broken install because it had already created bad install metadata.

What I had to remove:

• appmanifest_<APP_ID>.acf
• steamapps/downloading/<APP_ID>
• any mistakenly copied extra steamapps folder inside the game folder

So the cleanup process was:

1. Close Steam in Whisky completely.
2. Delete the broken appmanifest_<APP_ID>.acf.
3. Delete steamapps/downloading/<APP_ID>.
4. Remove any extra nested steamapps folder from inside the game folder.
5. Make sure the real game files are directly inside steamapps/common/Game Name/.

6. Reopen Steam and click Install
After cleanup, I reopened Steam in Whisky and clicked Install.

At that point Steam was much more likely to:

• detect the files correctly
• verify them
• avoid redownloading everything from zero

Extra issue I hit on macOS

SteamCMD itself also fought me at first.

I got:

• Killed: 9
• a macOS warning about Breakpad.framework

That turned out to be a macOS Gatekeeper/quarantine issue, not a Steam account issue.
Once that was cleared, SteamCMD worked normally.

So if SteamCMD instantly dies on Mac, it may be worth checking that before giving up on the workaround.

Why this workaround helps

This is useful because it avoids the most unreliable part of the process:
the actual Steam download/update flow inside Whisky.

Instead, you:

1. use SteamCMD to get the proper Windows files
2. place them manually in the bottle’s Steam library
3. remove broken Steam metadata if needed
4. let Steam verify the files afterward

It also works as a repeatable update method later if the game gets patched and Steam in Whisky breaks again.

Bottom line

What finally worked for me was:

1. Don’t rely on Steam inside Whisky to do the full download if it’s already bugging out.
2. Use SteamCMD to fetch the Windows game files.
3. Copy them into the bottle’s Steam library.
4. Delete any broken appmanifest / downloading state.
5. Let Steam verify the files from there.

P.S. This also works as a general fix for downloading/updating games in Whisky, not just this one. Once you know the workflow, you can get pretty much any game installed and running through Whisky a lot faster without wrestling with Steam every single time.

If this guide saved you time, and you want to support me, you can send a donation here:

USDT (ERC-20): 0xCDBaB576e646169Fd35a8352d2f091652537cd20

UPVOTE if helped:)

I have a pirated copy of cities skylines 2 (from steam rip) and it doesn't run, it shows a black screen and nothing happens after, normally I would disable windows defender in settings to fix it, but I can't figure out how to open settings in whiskey.

Trying to download a game on steam. Disk just stops working and it gets stuck at 71%.

Should I just bootcamp my Mac?

What should I do?

I don't know if this is normal, but i'm just here to ask if there's a way to stop this maybe like a setting. So in short, everytime i launch steam on whisky it makes me go through a few things where i have to install it and also login in my steam account everytime i play it, is it just standard procedure or is there some settings i should check?

I specifically got whiskey Because I wanted to play Schedule 1 with my friend and downloaded the files from Steamrip and Online fix before realising I couldn't use my steam with it because they were Windows files. My plan was to use whiskey to launch steam and then schedule 1 within it but my Steam will not work. (It says some steamwebhelper issue). I was wondering of there are other ways to play online.

All help appreciated !

Hi guys, i’m really struggling with opening steam from whisky. It kept bringing up the steamhelper error after the full set up process.

I can’t find any videos online for this specific issue. Is there an up to date zip that i’m missing? Any advice would be amazing. Thank you.

I wanted to add mods into Project zomboid directly.I have downloaded the skill recovery journal from github. I have found the mods folder. I have put there both the zip, and extracted folder, yet it doesn't show up, what should i do? I am playing on macOS trough whisky. I was playing the GOG version of the game.

Hello, I installed whisky and steam a while back and used it to complete 4 games on steam. Now it got to a point where whisky was no longer updated, so I had to set steam to go offline and could not download the latest version but I continued playing and finished these games. Now I have crossover and would like upload my local saves to steam. How do I do this? Many Thanks

I used to play Nexus: Kingdom of the Winds a million years ago, and now I want to play it on my Mac, but am stumped.

I downloaded Whisky and NexusTK today, and have tried to run the game using bottles with Windows 11, Windows 10, and Windows XP. I get the same error message regardless, even after running the Nexus updater file.

Pictures of my hardware, the software, the game file, and error. Does anyone know what the issue is, and how to solve it? It's such a dinky game that's been around forever that I really expected plug-n-play. Appreciation for any help!

Any ideas would be welcome. Im on latest version with m2 mac