Sansar
NicoCaldo Jun 25, 2020 @ 8:50am
Game won't start
I click play but nothing happen.
< >
Showing 1-10 of 10 comments
Fuster Jul 2, 2020 @ 11:55am 
same here... have you found solution?
Fuster Jul 2, 2020 @ 12:29pm 
I found a solution.... there is some sort of conflict between Sansar and NordVPN
Stopping the nordvpn service (the service is running even if you have the app turned off) allows Sansar to start.
krylke Aug 23, 2020 @ 12:14pm 
I tried this but it didnt work. Sansar still wont work. I dont want to uninstall NordVpn to get this to work. Hoping for a fix soon
krylke Aug 23, 2020 @ 12:27pm 
Ok so killing NordVPN did not work. The only thing that worked is uninstalling NordVpn completely. Please fix this
da yolo masta Aug 28, 2020 @ 9:15am 
Same exact issue. Nothing but uninstalling Nord VPN seemed to work
clamsforever Aug 29, 2020 @ 4:20am 
Disabling the Nord service worked for me. What a headache. Thanks Fuster.

What a terrible piece of software though and a weird-ass conflict.
dexia Aug 29, 2020 @ 10:30pm 
It's been this way since maybe March for me.

I don't use NordVPN but I do have other VPN software installed. Removing it (and its related components like openvpn, ikev2, or wireguard services) completely had no effect on the inability to run Sansar or its updater.

Running the Sansar executable itself (sansarclient.exe) leads to "Please update to the latest version by running the sansar updater". Running as an administrator makes no difference.

Running the updater flat-out fails, whether it's as an admin or not. In the Windows Event Viewer's "Application" subsection Sansar,exe (whether invoked from Steam or directly) causes an "Error 1000":

Faulting application name: Sansar.exe, version: 5.1.13.32, time stamp: 0x5cb76399
Faulting module name: Sansar.exe, version: 5.1.13.32, time stamp: 0x5cb76399
Exception code: 0xc0000409
Fault offset: 0x000e1d62
Faulting process ID: 0x1538
Faulting application start time: 0x01d67e8a1a444c7c
Faulting application path: (redacted)\SteamLibrary\steamapps\common\Sansar\Updater\Sansar.exe
Faulting module path: (redacted)\SteamLibrary\steamapps\common\Sansar\Updater\Sansar.exe
Report ID: ad4a1495-bd60-42bc-a33d-f4d9c230de41
Faulting package full name:
Faulting package-relative application ID:

Running their installer (freshly downloaded directly from their website) also fails with an "Error 1000":

Faulting application name: SansarInstaller-22085050692666977118-notrack.exe, version: 5.1.13.32, time stamp: 0x5cb76399
Faulting module name: SansarInstaller-22085050692666977118-notrack.exe, version: 5.1.13.32, time stamp: 0x5cb76399
Exception code: 0xc0000409
Fault offset: 0x000e1d62
Faulting process ID: 0x22d0
Faulting application start time: 0x01d67e88c1f6c6a5
Faulting application path: (redacted)\scoped_dir5936_1138642357\SansarInstaller-22085050692666977118-notrack.exe
Faulting module path: (redacted)\scoped_dir5936_1138642357\SansarInstaller-22085050692666977118-notrack.exe
Report ID: fed64cf9-dffa-4098-a673-b0cc7c46062b
Faulting package full name:
Faulting package-relative application ID:

No other concurrent or obviously related errors (from things like missing DLLs) are in the event logs.

Also note that there are people on Sansar's own community site reporting similar problems. At least one example lead to someone from Sansar opening a support ticket for the person but the forum thread dies there.
Last edited by dexia; Aug 29, 2020 @ 10:38pm
dexia Sep 14, 2020 @ 1:25am 
Update 2020-09-14: as soon as I forced Windows (10) to upgrade to version 2004 (build 19041.508) the updater ran correctly and I can now login.
It may have been a coincidence (following the build update) but I see that Steam didn't push an update before it worked.
Duskerz Sep 25, 2020 @ 9:09am 
an issue for months i guess this thing is dead lol
Sininside Nov 4, 2020 @ 9:53pm 
YAY another pos has my email and this doesn't work! that's great smh... WHEN ARE DEAD GAMES GOING TO BE REMOVED FROM STEAM!? A-HOLES
< >
Showing 1-10 of 10 comments
Per page: 1530 50