Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Stopping the nordvpn service (the service is running even if you have the app turned off) allows Sansar to start.
What a terrible piece of software though and a weird-ass conflict.
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.
It may have been a coincidence (following the build update) but I see that Steam didn't push an update before it worked.