Install on win 10

**Kilohertzog** · September 30, 2022, 05:34 PM

Sorry if duplicate. My last post did not show up

I am on Win 10

Try #1 -
- installed vanilla, confirmed it works
- installed 6.3 to mods directory within MT2W main install directory
- installed 6.4 to same directory
- renamed executable

Result: I can launch SS, and get as far as campaign selection, but start campaign kicks me back go main menu. My understanding is because SS is trying to save the game to the install directory inside Program Files X86 directory, which is not permitted under win 10.

Try#2
- Uninstalled everything
- reinstalled vanilla, it works
- installed the combined package linked above in sticky to same M2TW install directory as Try #1
- all file validation etc passed.

When i launch SS it immediately crashes with a generic error (medieval 2 encountered an error)

When I try to launch vanilla same error is presented. Seems like SS installer corrupted vanilla too.

Any ideas?

**Gigantus** · October 01, 2022, 12:41 AM

Are you using this installation? Because that one takes care of the 'executable renaming' and looks up the correct installation path automatically via registry.

Proceed as follows:
- find the CFG file in the game's main directory and delete it.
- if on Steam: clear the game's custom launch option: right click the game's link in the library, choose 'properties' and then remove any entry in the custom launch option
- start the main game to check if the error persists
- remove\delete the existing SS installation
- re-install SS using the above link, note that there is a small patch as well

**Kilohertzog** · October 01, 2022, 07:53 AM

Yes that's what I used for try #2. I completely blew away the installation and ran both steam installer, and ss installer on a clean install.

The CFG file and steam custom launch - should I remove that after installing SS?

**Gigantus** · October 01, 2022, 08:36 AM

Before we proceed, let me address this:
"My understanding is because SS is trying to save the game to the install directory inside Program Files X86 directory, which is not permitted under win 10."
Not sure where you heard that, but it is incorrect, even the main game saves to the install directory. But that that would not have an effect on starting the game anyhow, only when saving it.
---------------
Your issue here seems to be the particular version of the Stainless Steel installer. Hence why I recommended that you try my installer. It's a 'click through' affair: you simply click 'next' all the time. Nothing else required. Then do the same with the small patch you will find in the second post of that thread.
Even though you seem to have uninstalled M2TW completely I would still recommend to check if there is an entry in Steam's custom launch option - if only to rule that out.
Delete the present SS6.3 directory and then use my installer. After that you should be fine to start the 'set up' launcher for SS where you choose your settings. After that start SS with the regular desktop icon if the launcher doesn't start it for you after your choices.

**Kilohertzog** · October 01, 2022, 09:59 AM

1) Windows not permitting apps to write to program files has been a security standard over a decade now. All modern apps keep their files in user/local/AppData. This is a well known windows development rule, like 101 type knowledge. Source: have been developing windows apps for 20 years.

2) When you create a new campaign the game immediately creates a save file, which was causing an issue using the old school installer.

3) For try #2 I am using your installer Gigantus and that seems to not even allowing me to launch the game. Are the CFG changes you suggesting to be done post install or pre install? (I was doing a clean install)

4) is there a debug log that TW produces that I can look at?

**Gigantus** · October 02, 2022, 06:36 AM

" All modern apps keep their files in user/local/AppData. This is a well known windows development rule, like 101 type knowledge."
I am fully aware of that - it's just not the case with this ancient game (2006), different story with the Mac release from a few years ago I believe. Saves are actually in the aptly named 'saves' sub directory of the game (or mod) and the configuration file is in it's main directory, with the mod having it's own (partial) CFG file that overrides settings in the main CFG file.

"When you create a new campaign the game immediately creates a save file, which was causing an issue using the old school installer."
Stainless Steel modifies assorted game files in it's directory when you apply\change settings with SS's launcher before starting a new campaign, but not a save game file (.sav) - even on autosave a save file only gets created when you press 'end turn' for this game.
Note: changing the settings via Stainless Steel's launcher has a high likelihood of crashing existing save games when loading.

Also see ...\mods\ss6.3\data\campaign\readme for more details on the launcher\settings modification system.

"Are the CFG changes you suggesting to be done post install or pre install? (I was doing a clean install)"
The main game's CFG file will not exist until you start the game for the first time, hence in this case the suggestion will not help. Only if you would get a 'CA_LIBS' error message.
My suggestion regarding Steam's custom launch option however should be looked at as I do not know if it would get removed totally when removing M2TW's installation.

"is there a debug log that TW produces that I can look at? "
As you are using my installation you will find the log (system.log.txt) in the game's main directory (old SS installations have it in a mod sub directory). It should be quite extensive as it is set to 'trace' - in this case the last 20-30 lines before the game triggers information section (if it exists) can give an idea at what point the game crashed, it's not often that there is a very clear message.

One question I have forgotten: when you start Stainless Steel with it's desktop shortcut do you get a splash screen with it's name or the medieval 2 splash screen?

And then there is the Virtual Store...for more on that read here from step three onward. Should you find M2TW files in VS don't forget to delete them.

**Kilohertzog** · October 02, 2022, 07:11 PM

Thank you for the detailed answer. I'll try another clean install and upload the trace file. I am launching SS from the desktop shortcut, not steam, and I am getting the SS splash screen.

**Gigantus** · October 02, 2022, 08:56 PM

Please zip the log - it will be fairly big.

**Kilohertzog** · October 09, 2022, 03:10 PM

Originally Posted by Gigantus

Please zip the log - it will be fairly big.

Here it is, very small. Looks like a bunch of data & graphics config files are missing. I followed step 3 in the link you gave to enable full control over the medieval 2 folder to the user in case this is the virtual store issue, but that did not resolve the problem.

Spoiler for log:

**Gigantus** · October 09, 2022, 09:14 PM

It's inconclusive - 'missing' (in the mod setup) is usually followed by 'found' (in the pack files). But there is also a 2 second gap between the last entry and the crash entry, that's an eternity where the log is concerned.

To figure out if it is a general issue or restricted to the stainless steel installation please install my small mod set up and start it from it's desktop short cut all the way to the campaign map.

**Kilohertzog** · October 14, 2022, 07:18 PM

Originally Posted by Gigantus

It's inconclusive - 'missing' (in the mod setup) is usually followed by 'found' (in the pack files). But there is also a 2 second gap between the last entry and the crash entry, that's an eternity where the log is concerned.

To figure out if it is a general issue or restricted to the stainless steel installation please install my small mod set up and start it from it's desktop short cut all the way to the campaign map.

Bare geomod worked just fine.

**Kilohertzog** · October 14, 2022, 07:22 PM

Originally Posted by Kilohertzog

Bare geomod worked just fine.

Interstingly enough, after existing Bare geomod and launching base game from steam, I got the same error again as above.

**Gigantus** · October 14, 2022, 08:49 PM

I am running out of ideas. Why would it work for BG and all of a sudden not work for the main game?

Have you tried setting the game's files (medieval2.exe and kingdoms.exe) to win7 compatibility and admin rights? As well as applying LAA to them?

You could also try using my desktop shortcuts to run the main game (and DLCs).

**Kilohertzog** · October 15, 2022, 02:51 PM

Launching from desktop fixed the launch issue for the base game. Any ideas on geomod vs SS?

**Gigantus** · October 15, 2022, 08:48 PM

I am still thinking it's an issue with the game's CFG file - the shortcuts and BG (as well as SS) have their own, limited CFG file whose entries override the main game's CFG entries.

Did you apply the compatibility settings as well as LAA?