Max Jan 23, 2017 @ 7:12pm
Steam Client on Server 2008 SP2 (Not R2) problem
Let's make it clear first I'm not talking about Windows Server 2008 R2 (NT6.1). I am talking about Windows Server 2008 SP2 (NT6.0). Second, I have already submitted a help request to steam support. This is just a reference for a temporary fix.

Steam Client on Server 2008 SP2 (Not R2) is literally unusable due to the browser does not support NT6.0 OS.

Since Steam detects Server 2008 SP2 as windows 7/2008 R2 (it's not). It use the windows 7 package. As a proof that Broadcasting feature is enabled on Server 2008 but instead it is blocked on Vista (it is fully functional on server 2008 and should on Vista).

The problem is the chromium browser in that package doesn't support NT6.0 (Vista) OS. SteamWebHelper.exe will just crash as soon as I started Steam Client. Crash windows will appear every few seconds if I keep closing them. Making the client literally unusable.

Deleting SteamWebHelper.exe in C:\Program Files (x86)\Steam\bin\cef folder as soon as I launched Steam will fixed the annoying crash windows. It isn't really a solution because the browser is not usable at all.

The real solution would be either put server 2008 in XP/Vista update branch (Which will lose the ability for broadcasting) or have Vista and server 2008 a standalone branch which use the XP chromium and able to use broadcasting feature as promised. (The Vista, linux & OSX support thing in the broadcasting FAQ)


Crash log in event viewer if you're interested
Faulting application steamwebhelper.exe, version 3.78.49.52, time stamp 0x58801653, faulting module KERNEL32.dll!QueryUnbiasedInterruptTime, version 6.0.6002.18881, time stamp 0x51da3e00, exception code 0xc0000139, fault offset 0x0006f52f, process id 0x7cc, application start time 0x01d275ec289c8caf.
In human language: The program just crash because it calls a non-exist module in NT 6.0's kernel32.dll.
Date Posted: Jan 23, 2017 @ 7:12pm
Posts: 0