WineHQ

StarCraft

The original StarCraft with 1.18 patch onward including updates from StarCraft Remastered.

This version does not include the remastered graphics and audio.

Application Details:

Version: 1.18+
License: Free to use
URL: http://blizzard.com/games/sc/
Votes: 11
Latest Rating: Platinum
Latest Wine Version Tested: 2.15-staging

Maintainers: About Maintainership

Link Version notes Free Download Installer Free Download StarCraft® Anthology

Test Results

Selected Test Results

What works

Everything seems to be working just fine. Changed OS with winecfg from 2003 to XP and 10 and encountered no problems at all.

What does not

Unknown, all seems OK.

Workarounds

What was not tested

Installation as the game's already installed.

Hardware tested

Graphics:

  • GPU: Nvidia
  • Driver: proprietary
  • Additional Comments

    selected in Test Results table below
    Operating systemTest dateWine versionInstalls?Runs?Used
    Workaround?
    RatingSubmitter
    CurrentopenSUSE Leap 42.3 x86_64Sep 04 20172.15-stagingN/A Yes NoPlatinumEmil Kaczmarek 
    ShowopenSUSE Leap 42.3 x86_64Aug 22 20172.14-stagingYes Yes YesGoldEmil Kaczmarek 
    ShowUbuntu 16.04 "Xenial" amd64 (+ variants like Kubuntu)Aug 17 20172.14-stagingYes Yes YesGoldIgor Polyakov 
    ShowArch Linux x86_64Aug 16 20172.14-stagingYes Yes YesGoldVíctor 
    ShowDebian 10.x "Buster"Aug 14 20172.14-stagingYes No GarbageThomas Ross 

    Known Bugs

    Bug # Description Status Resolution Other apps affected
    37594 World of Warcraft in-game browser does not work NEW View
    38960 Multiple applications need 'kernel32.SetFileCompletionNotificationModes' implementation (Steam 'steamwebhelper.exe' CEF v3.2+/Chromium v44+ crash in Win7 mode, Sony Xperia Companion 1.7.x) STAGED View
    42741 StarCraft I: 1.18 PTR fails to initialize ClientSdk.dll STAGED View
    43011 StarCraft Brood War 1.18 significant delays in CEF Browser UNCONFIRMED View
    43434 StarCraft: Brood War doesn't run without setting the Windows version to 2003 or Vista UNCONFIRMED View

    Show all bugs

    Comments

    The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

    StarCraft-Setup.exe Installation hangs
    by Taras on Monday September 4th 2017, 9:34
    Installation hangs on the "Updating blizzard Agent..." window infinitely.
    The error log is below. Also I installed staging, as recommended in thread.
    Will appreciate any reasonable advice.


    >>> WINEPREFIX=~/win32 wine StarCraft-Setup.exe

    fixme:wininet:InternetSetOptionW Option 77 STUB
    err:wininet:open_http_connection create_netconn failed: 12029
    fixme:wininet:InternetSetOptionW Option 77 STUB
    err:wininet:open_http_connection create_netconn failed: 12029
    Object moved
    Object moved to here.

    fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
    fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
    fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
    fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
    fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
    fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
    fixme:module:load_dll Loader redirect from L"wined3d.dll" to L"wined3d-csmt.dll"
    fixme:wbemprox:wbem_locator_ConnectServer unsupported flags
    fixme:wbemprox:client_security_SetBlanket 0x7d7ec82c, 0x1500e0, 10, 0, (null), 3, 3, (nil), 0x00000000
    fixme:wbemprox:client_security_Release 0x7d7ec82c
    fixme:wbemprox:enum_class_object_Next timeout not supported
    fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
    fixme:ver:GetCurrentPackageId (0x1abe9a8 (nil)): stub
    fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
    err:winediag:wined3d_adapter_init GL_ARB_compatibility not supported, requesting context with GL version 3.2.
    fixme:wininet:InternetSetOptionW Option 77 STUB
    err:wininet:open_http_connection create_netconn failed: 12029
    fixme:heap:GetPhysicallyInstalledSystemMemory stub: 0x33f888
    err:winediag:wined3d_adapter_init GL_ARB_compatibility not supported, requesting context with GL version 3.2.
    fixme:heap:GetPhysicallyInstalledSystemMemory stub: 0x33f548
    fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
    fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
    fixme:wininet:InternetSetOptionW Option 77 STUB
    Test results are current
    by Víctor on Thursday August 17th 2017, 11:06
    It seems like current test results are flagged as very old, when in fact they were done a day or two ago.
    Game playable again (1.19.5.*) with Wine 2.14-Staging
    by Gian Paolo Mureddu on Sunday August 13th 2017, 20:55
    I chime in to confirm the game works as expected in Wine Staging 2.14, how ever two things are notorious, you HAVE to use Windows 2003 as the windows version, otherwise, if you try WinXP you get the old GetProcessWorkingSetSizeEx error message (Vista threw no error, but as 7 did get status c0000094, and .dll initialization error).

    I was curious, though, has anyone running the game under Wine been able to run in fullscreen mode (no sidebars [letter box], and aspect set to widescreen)? Also all the Video settings in the 1.19 version seem to be greyed out, except for the double-buffering (I understand the HD graphics, as those are reserved for the Remaster).

    Battle.net also works, as expected.

    I guess we'll have to wait and see if the Remastered, when released tomorrow, will also run on this version, or if we'll have to wait another two cycles to get it... In the meantime, I keep my fingers crossed.
    RE: Game playable again (1.19.5.*) with Wine 2.14-Staging
    by Erick on Tuesday August 15th 2017, 23:27
    Did Remastered ran?

    D:
    RE: Game playable again (1.19.5.*) with Wine 2.14-Staging
    by Gian Paolo Mureddu on Wednesday August 16th 2017, 12:56
    Sorry I missed your comment.

    YES!!! It runs just fine, with the same conditions.

    HOWEVER, since Remaster now launches from the Blizzard App, you have to run the app with Windows XP mode, otherwise you won't see the PLAY button because you are presented with a banner which has to be closed. Once you close that, you can run in any other Windows version mode and see the Play button.

    EVERYTHING works, campaign, single-player custom, Battle.net and LAN, I'll add a WineAppDB entry for the Remaster.
    Successfully installed and played on Battle.net
    by Allan Tokuda on Saturday May 20th 2017, 14:48
    I'm on Ubuntu 16.04. I was able to install and run the game and play on Battle.net, after some updates.

    I downloaded the now-free Brood War 1.18 installer here:
    starcraft.com/en-us/articles/20674424

    At first when I tried an older version of Wine, I was able to install the game but could not run the game.
    "The application encountered an unexpected error"

    I tried using the "StarCraft Launcher.exe" and that alone did not work either.

    I installed wine-staging (2.8) based on instructions here:
    wine-staging.com/installation.html

    After upgrading Wine I found I had to kill my existing wine server and related processes to use the newer version.
    ps aux | grep wine | awk '{ print $2 }' | xargs kill

    Running my existing install with wine staging still didn't do the trick. I had the error below.

    fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
    fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
    fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
    Object moved
    Object moved to here.

    Object moved
    Object moved to here.

    ^Cfixme:console:CONSOLE_DefaultHandler Terminating process 18f on event 0

    These docs explained how to create a fresh wine directory configured for 32-bit architecture.
    wiki.archlinux.org/index.php/wine#WINEARCH

    Following those, I made a new wine directory like this:
    WINEARCH=win32 WINEPREFIX=~/win32 winecfg

    Then ran the StarCraft installer using that wine prefix:
    WINEPREFIX=~/win32 wine StarCraft-Setup.exe

    And everything ran perfectly from there, launched directly from the installer. I connected to Battle.net and played a multiplayer game.

    Was also able to re-run the installed game again later like this:
    WINEPREFIX=~/win32 wine ~/win32/drive_c/Program\ Files/StarCraft/StarCraft\ Launcher.exe

    So in the end I did several things and am not sure which things were required, but I'm happy for now!
    Game doesn't launch
    by CheshireCat on Sunday May 7th 2017, 9:14
    Distro: Devuan GNU/Linux ascii
    Kernel: 4.9.0-2-amd64 x86_64 (64 bit)
    Desktop: i3 4.13
    Graphics: Card: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480]
    Display Server: X.Org 1.19.2; Driver: amdgpu; Resolution: 1920x1080@60.00hz
    GLX Renderer: Gallium 0.4 on AMD POLARIS10 (DRM 3.8.0 / 4.9.0-2-amd64, LLVM 3.9.1)
    GLX Version: 3.0 Mesa 13.0.6
    Wine version: wine-2.7 (Staging)

    When I try to run the game (32bit wineprefix with corefonts), It first tries to update, after updating it lets me click "Launch" but the game doesnt launch.
    I have enabled "Hide Wine version from applications" in the "Staging" tab. Here is what I get in terminal when I try to launch it: paste.debian.net/hidden/8e3d6c82/

    by Sigz on Tuesday May 2nd 2017, 11:09
    you can use this wine fork github.com/awesie/wine-starcraft/ then starcraft 1.18 will work flawlessly
    RE:
    by Jonathan on Saturday May 6th 2017, 15:42
    I'm getting this all the time using wine-starcraft:

    wine: Call from 0x7bc5a0d9 to unimplemented function kernel32.dll.GetTickCount64, aborting

    Error appears as soon as I set "Hide Wine version from applications"

    Working intermittently and only if I run the Launcher.

    Any ideas?
    RE:
    by Igor Polyakov on Sunday May 7th 2017, 1:48
    What I did is I set everything to use Windows 7, but have an exception for StarCraft.exe to use Windows XP and "Hide Wine version from applications" enabled. That way I don't get the error.
    RE:
    by Jonathan on Sunday May 7th 2017, 3:17
    I use this exception as well in winecfg. However, I can't load the Launcher when "Hide Wine version from applications" is set. It gives me an error. After I load the launcher, I then need to enable it before launching Startcraft. Then it works 50% of the time.
    RE:
    by Igor Polyakov on Sunday May 7th 2017, 3:41
    Why do you need to use the launcher? Just load StarCraft.exe directly. It will update your game if it's out of date even if you start there.
    RE:
    by Jonathan on Sunday May 7th 2017, 4:43
    It fails to launch if i just use the standard .exe. If I use the Lancher, it attempts the update, let's me launch Brood Wars and then I can use Battle.net
    RE:
    by Igor Polyakov on Sunday May 7th 2017, 4:03
    I haven't been able to use Battle.net even with the fork, I have no gateways and the OK button is grayed out. I am using Windows XP and hiding Wine version from applications.
    RE:
    by Jonathan on Sunday May 7th 2017, 4:44
    This is working for me, using the method I explained above.
    RE:
    by Igor Polyakov on Sunday May 7th 2017, 4:50
    Like I said, the game launches fine for me already without the launcher. Using the launcher did not solve the issue with Battl.net.
    RE:
    by Tim on Sunday May 7th 2017, 15:41
    Had the same issue with battle.net because of secur32 override. Just dropped it and now I can connect and login.
    RE:
    by Igor Polyakov on Sunday May 7th 2017, 17:03
    OK, I found out what the issue is. It takes about 30 seconds to actually get the interface populated with elements! I have to wait and stare at it until it gives me gateways. Then I have to wait another 30 seconds to get the login modal populated...
    RE:
    by Adrian Petrescu on Sunday May 7th 2017, 21:54
    Yes, I have this exact issue as well. It takes an absurd amount of time for Battle.net menus to populate with text, but once they do, everything is fine. In-game latency is totally normal.
    RE:
    by Horațiu Mlendea on Monday May 8th 2017, 0:25
    Hmmm... does this also happen on a clean WINE prefix with just Battle.net installed? Mine doesn't have this problem but it is an old install, gonna start clean and try it like that when I get home.
    RE:
    by Igor Polyakov on Monday May 8th 2017, 1:11
    I made something like 5 different wine prefixes and installed fresh each time. I used my own compile in one of them, some binaries in another, I tried the Lutris version, I tried recompiling, etc.

    I just get the same issue, the game itself works, but the CEF browser thing is really slow for some reason.
    RE:
    by Adrian Petrescu on Monday May 8th 2017, 8:45
    Wait, CEF? Battle.net is seriously using CEF?
    RE:
    by Horațiu Mlendea on Monday May 8th 2017, 10:04
    Not an expert at all but wouldn't that improve torrenting? AFAIK Battle.net is/was downloading game data via torrents, which is why it is usually very fast.
    RE:
    by Igor Polyakov on Monday May 8th 2017, 16:36
    It runs cef/SceneCefBrowser.exe and then loads assets from localhost to display battle.net menus

    it will load pages like 127.0.0.1:38097/gamedata/webui/dist/GatewayPanel/GatewayPanel.html?port=38097&guid=41
    this will load GatewayPanel.js also from localhost

    this is what's really slow in Wine
    RE:
    by Adrian Petrescu on Monday May 8th 2017, 20:17
    Wow, that's really interesting. I bet that's not how the 1996 version worked, haha :)

    I'm not sure I follow why that's really slow in Wine. Why would Wine be so much slower at serving some HTML/JS on localhost than Windows?
    Back