Cities: Skylines won't launch in Windows 10!

[Meira93 0]

I upgraded from Win7 to Win10 yesterday, and when launching Cities: Skylines, the game closes itself after 2 seconds (nothing pops up)! I tried adding --noWorkshop and --disableMods , which worked, later to try removing Rush Hour mod, which allowed me to play the game with my mods as normal. However, today I the same issue as before. I tried --noWorkshop --disableMods again, and even then it doesn't launch! And yes, I've updated my video card's drivers. Can someone please help me? Thanks

[rsc204 21,804]

I know MS are telling world + dog how seamless the upgrade from older versions of Windows to 10 is. But every time I've done an OS upgrade in the past, something's needed to be re-installed. So I'd remove C:S and try installing again under Windows 10 before looking too deeply into the problem.

[Meira93 0]

I reinstalled it. Still doesn't run

[rsc204 21,804]

I've not heard of any major compatibility problems between C:S and Win10. If you've done a fresh install and disabled all mods/custom content, that's not a good sign.

Assuming the code for C:S works with Win10 (I believe it does), your hardware supports the game, neither Windows nor the install of C:S is faulty, then you are going to have to do some work to get to the bottom of this one. Since it has run at some point, there must be some factor that's preventing it happening now. Here are a couple things you could try to determine the cause:

• The latest Graphics Card drivers are not a magical fix to every problem. Some driver revisions have problems with some games, others don't. So if the latest one isn't working, perhaps try rolling back to previous versions to see if that fixes things.
• Conflicts - i.e. other applications running that interfere with C:S or Steam - are a common source of problems. Reboot your system and do not open any applications. Close everything you don't need in the system tray. Then try running C:S.
• Along the same lines, many programs will be running in Task Manager (under processes tab) that can potentially conflict with C:S. Here things get more tricky, for example I have 90+ processes on my machine, without any apps open. Many of these are related to drivers, i.e. to ensure you hardware works. It also includes my Antivirus and a number of Windows based programs required for correct operation of the OS. However, there will also be a number which do not conform to the previous categories. Using the System Configuration Tool you can choose which of these Processes are run during start up. You should try to remove as many of the non-critical ones as possible for the purposes of testing.

If either of the last two suggestions get's the game working, you have a conflict. But it's not as simple as thinking because it now works, you can leave them disabled. You need to go through them more thoroughly until you can determine exactly which application is causing the problem. Then you can decide if it's better to disable it permanently, try to find an updated version or manually disable it when running C:S. To make things even more messy, conflicts could come from more than one application too.