So many of these reports... If you subscribe to new Workshop items (in my case Scenarios) you risk scorching your Train SIm installation. I know what's happening now (after a couple of days systematic and detailed analysis). Short Story: Subscribe to Workshop scenario(s). The more you do at one time the higher your risk! Try to open TS. It may die during initialization, or more commonly shortly after you see the Main Menu, boom! Temp Dump with 0cC000005 popup. Subsequent attempts to open TS will result in a nearly immediate Temp Dump and popup. What's Happening? When you subscribe to a Workshop item, Steam puts it into its workshop folder that is shared between all installed games. This process always succeeds. Each time TS starts, it looks at its own list of installed Workshop items vs the stuff Steam has in its shared area. If there is something new, TS will "auto-install" it from the Steam area into its own workshop area. This process of "auto-install" happens in the background and in parallel with the startup of TS, and it is this process that is unreliable. Sometimes, and I can't see any pattern to it, the installation process results in TS' copy of the workshop data being plainly corrupted. For scenarios (for example) a file called ScenarioProperties.xml is read from the Steam area, and then it is altered by TS which substitutes "real" values for "placeholders" in the original from the workshop. This is what randomly fails. Once TS has corrupted a workshop item during installation, Train Simulator is 100% dead. I have seen no pattern to the corruption. Sometimes garbage data and/or characters will be embedded in strings (the ones that are substituted by TS during installation). I've even seen a case where an entire chunk of 15-20 lines of the original ScenarioProperties.xml are simply missing from the "installed" one in TS. Clearly TS' startup process of "installing" the XML file is unreliable. I have reproduced this many times over the last week or so and I clearly understand what is happening, I just don't know why! ANd this has been happening for ages, based on the reports I have seen here and elsewhere over the last year or so. How to Mitigate the Problem - Don't subscribe to more than one Workshop item at once. It's really hazardous to install an entire collection. How to Recover from a TS Workshop Corruption Let's say you installed a Workshop Scenario. Open the File Explorer and navigate to C:\Program Files (x86)\Steam\steamapps\common\RailWorks\Content\Routes In the File Explorer's Search box (upper right) type ScenarioProperties.xml. You will get a lot of these files, one for each workshop scenario. Now sort this list by Date Modified descending with most recent at the top. The one at the top will most likely be the corrupted one. Right-click on this entry in the list and choose Open File Location. You should see something like this: In the above example, in the location field at the top of the Explorer, click Scenarios. This will put you in the scenarios folder of the correct route. Again sort the list by Date Modified descending. Now you should see the (e.g.) 8bb168eb-68b9-4c97-90d5-6dd340e884e9 folder at the top (newest scenario folder). Delete it (delete the e.g. 8bb168eb-68b9-4c97-90d5-6dd340e884e9 folder). This deletes the corrupted scenario. Keep the File Explorer open as it is. Now start TS. It will see that it needs to install this Scenario from the workshop. If it still dies, then delete the next oldest scenario folder, etc. If you have to delete more than 2-3 to get TS to start, then you should unsubscribe from those scenarios in Steam so your odds for getting them all to successfully install in TS will improve Let it initialize, then let it sit at the main menu for at least 30 seconds (enough time for the background installation process to complete), then try to enter Drive > Workshop. If you see a brief "Installing Workshop Items" then you're good and this time it succeeded. If you get another TempDump, go back to that File Explorer you left open in step 6. and delete the scenario folder again. It will still be at the top of the date-sorted list. Repeat (delete, restart) until you can run TS. It may take a few tries. There is nothing you can do (AFAIK) to "make" it install the scenario successfully. Just keep trying. Eventually it will succeed. For routes instead search for RouteProperties.xml. If you delete an entire route folder, though, all of the scenarios for that route will also be auto-installed and your chances for success are lowered (at least one will probably get corrupted). In this case unsubscribe from all of the scenarios for that route, then unsubscribe from the route, and delete the Routes\xxx-xxx-xxxx folder to allow TS to start. then start with subscribing to the route, keep trying until you get a good Route install, then once for each scenario, repeat until successful. I know this is complicated ... I just did my best to explain it. It's probably easier to actually do after you've dome it a few times. Of course if you're careless you could scorch your whole TS installation so be careful.