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
By booting Windows into Safe Mode, you're ensuring no other programs are running in the background when you install. From what I've been able to discover, programs like Razer's Comms/Cortex/Synapse/Booster or Logitech Gaming/SetPoint software can interfere with the installation.
For the next version of the mod, I'm making a change to the scripting in the installer to try and mitigate this issue. (In other words, it's an issue with the installer software itself and I'm going to try and see if I can work around it.)
Looking forward to the update. I hope someone posts in this thread when it comes, since I'm subscribed to this!
Since Safe Mode eliminates all extraneous background processes that could interfere with the install, it would have to be something else. Maybe a particular piece of hardware, like a certain storage device. I'm trying to pin down the cause of this, and the best I've come up with is Razer and Logitech software as causes in some cases.
That's great to hear. :)
It's unfortunate, that in some cases, booting to Safe Mode is necessary. Again, I'm trying to work around the issue in the next mod update.
Update: I got it to install. I disconnected my external USB drive originally but decided to disconnect everything except the keyboard and the mouse. I did reinstall the game and follow the instructions again but I'm pretty sure it was having an issue with one of my USB devices.
Issue lays both in faulty installer logic and outdated nircmd. Probably it has some troubles with external drives since my game installed on external one.
I've been doing installers and patchers for more than decade. Can you publish source code of installer scripts to see what exactly it does to find part where logic should be changed?
I've already tested the installer on 4 different computers, all with different versions of Windows (XP through 10), different installed software, and different hardware. I can't replicate the hang. This seems to be a flaw with the installation software itself, that manifests itself due to some specific software or hardware that I don't have that's interrupting the install process, and the installer doesn't handle it gracefully. I've already explained this elsewhere. I have to attempt changes to the scripting and create a workaround to mitigate this.
This is troubling, because - again - it's a flaw with the installer software itself. That would mean it scans all drives on your system, and hangs if it accesses an external USB drive or (what it believes to be) other USB storage device. I'll have to see if there's anything I can do to mitigate it.