Page 1 of 3

Unable to open any old scenarios using 1744

Posted: Sat Nov 22, 2025 4:39 pm
by DWReese
I installed the update and when I try to open up any existing scenarios using the 1774 Build, the program locks up, and I must exit the program.

I am able to Create a New Scenario using the 1774 Build, and that appears to work.

For trouble shooting, I reinserted Build 1728 but it would not load any of the old scenarios citing a database issue incompatibility issue.


I don't know if this is related, but I did receive a popup message when installing the update stating that Mircosoft Edge can't create a data directory. It states that:

Microsoft Edge can't read and write to its data directory.
C:\program files (x86)\matrix games\Command Modern
Operations\web view caches\EBWebView

Re: Unable to open any old scenarios using 1744

Posted: Sat Nov 22, 2025 6:17 pm
by thewood1
What is 1744?

edit...I just noticed it a typo in the title.

I was able to load any scenario in 1774 on Steam. Make sure db 514 is in the db directory.

Re: Unable to open any old scenarios using 1744

Posted: Sat Nov 22, 2025 6:23 pm
by Nikel
I guess is related with Webview and the game installed in a "Program Files" folder.

The same problem described by scott1393.


https://forums.matrixgames.com/viewtopi ... 0#p5250360

Re: Unable to open any old scenarios using 1744

Posted: Sat Nov 22, 2025 6:38 pm
by blu3s
You can edit the Command.ini file and add

CustomFolder_WebviewCache = C:\Users\USERNAME\AppData\Roaming

Make sure the user running Command has the permissions to write a folder in the directory, you can use:

C:\Users\USERNAME\AppData\Roaming

replace USERNAME by your user name

Re: Unable to open any old scenarios using 1744

Posted: Sat Nov 22, 2025 7:40 pm
by DWReese
blu3,

I am sill experiencing difficulty.

I inserted the line of text into the ini file as you directed. Does it matter where it is placed?

My users folder is dwree, and it does have a hidden sub folder titled "AppData", and another sub folder titled "Roaming"

But, I still can't get this to work.

I use Google Chrome as my Web Browser, and I don't have anything to do with MS Edge. Is that the problem?

Re: Unable to open any old scenarios using 1744

Posted: Sat Nov 22, 2025 7:47 pm
by DWReese
Nikel,

Yes, it seems as though it is the same problem.

I tried doing what blu3s said to do, but I must be doing something wrong because it still doesn't work for me. I've tried it several different ways with no luck.

Re: Unable to open any old scenarios using 1744

Posted: Sat Nov 22, 2025 8:15 pm
by blu3s
DWReese wrote: Sat Nov 22, 2025 7:40 pm blu3,

I am sill experiencing difficulty.

I inserted the line of text into the ini file as you directed. Does it matter where it is placed?

My users folder is dwree, and it does have a hidden sub folder titled "AppData", and another sub folder titled "Roaming"

But, I still can't get this to work.

I use Google Chrome as my Web Browser, and I don't have anything to do with MS Edge. Is that the problem?
I put the line there, and Command writes the webview cache there.
Image

No, webview is by default installed in all Windows OS, is used by different apps as an UI "render". In Command webview shows the database viewer, the briefing and scenario description windows. Is also used for display special messages.

With the change in your ini, this error pops up again?
Microsoft Edge can't read and write to its data directory.
C:\program files (x86)\matrix games\Command Modern
Operations\web view caches\EBWebView
Can you please clear your log folder and then launch command and attempt to open an "old" scenario ? Then upload the log here

Thank you

Re: Unable to open any old scenarios using 1744

Posted: Sat Nov 22, 2025 8:53 pm
by Nikel
Adding the text exactly in that place, it works.

I tried several places before in the file Command.ini and did not work.

So the place in the Command.ini file indeed matters.

Re: Unable to open any old scenarios using 1744

Posted: Sat Nov 22, 2025 9:13 pm
by DWReese
Nikel,

I did exactly as you said, and placed it exactly where you said, but I still had no luck.

Re: Unable to open any old scenarios using 1744

Posted: Sat Nov 22, 2025 9:14 pm
by DWReese
Blu3s,

Can you tell me how and where to find the file that you are requesting?

The program locks up as soon as I attempt to select a scenario file. I can move the cursosr around, but none of the buttons are responsive, and I can't exit the program. I have to reboot. Can I still get the file that you need? If so, how?

Re: Unable to open any old scenarios using 1744

Posted: Sat Nov 22, 2025 9:21 pm
by Nikel
DWReese wrote: Sat Nov 22, 2025 9:13 pm Nikel,

I did exactly as you said, and placed it exactly where you said, but I still had no luck.
The place is where blu3s posted in the screenshot, inside the file Command.ini

You have to create the folder if it does not exist.

Like the above

Code: Select all

C:\tmp
I my case was:

Code: Select all

C:\Temp

If the folder you write inside Command.ini does not exist, the game will create the folder "WebView Caches" inside CMO installation folder, by default.

And if you have the game installed in a "Program files" folder, it will not run properly as you described.

Re: Unable to open any old scenarios using 1744

Posted: Sat Nov 22, 2025 9:26 pm
by DWReese
Here is the contents of one log.

--------------- Starting new GUI-client session - 11/22/2025 9:11:41 AM Build v1.09 Beta - Build 1774 -----------------

Current DPI Awareness: 0

User's machine
Machine's name : DOUG
Thread's culture : en-US
Installed culture : en-US
Available virtual memory : 140732389.4Mo
Available RAM : 20735Mo
Total virtual memory : 140737488.2Mo
Total RAM : 33992.8Mo
OS name : Microsoft Windows 11 Home
OS platform : Win32NT
OS version : 6.2.9200.0
>>Running as administrator. <<


--------------- Starting new GUI-client session - 11/22/2025 11:01:05 AM Build v1.09 Beta - Build 1774 -----------------

Current DPI Awareness: 0

User's machine
Machine's name : DOUG
Thread's culture : en-US
Installed culture : en-US
Available virtual memory : 140732389.4Mo
Available RAM : 20428.2Mo
Total virtual memory : 140737488.2Mo
Total RAM : 33992.8Mo
OS name : Microsoft Windows 11 Home
OS platform : Win32NT
OS version : 6.2.9200.0
>>Running as administrator. <<


--------------- Starting new GUI-client session - 11/22/2025 11:04:41 AM Build v1.09 Beta - Build 1774 -----------------

Current DPI Awareness: 0

User's machine
Machine's name : DOUG
Thread's culture : en-US
Installed culture : en-US
Available virtual memory : 140732389.4Mo
Available RAM : 25481.7Mo
Total virtual memory : 140737488.2Mo
Total RAM : 33992.8Mo
OS name : Microsoft Windows 11 Home
OS platform : Win32NT
OS version : 6.2.9200.0
>>Running as administrator. <<


--------------- Starting new GUI-client session - 11/22/2025 11:11:29 AM Build v1.09 Beta - Build 1774 -----------------

Current DPI Awareness: 0

User's machine
Machine's name : DOUG
Thread's culture : en-US
Installed culture : en-US
Available virtual memory : 140732389.4Mo
Available RAM : 23438.4Mo
Total virtual memory : 140737488.2Mo
Total RAM : 33992.8Mo
OS name : Microsoft Windows 11 Home
OS platform : Win32NT
OS version : 6.2.9200.0
>>Running as administrator. <<


--------------- Starting new GUI-client session - 11/22/2025 11:14:41 AM Build v1.08 - Build 1728.2 -----------------

Current DPI Awareness: 0

User's machine
Machine's name : DOUG
Thread's culture : en-US
Installed culture : en-US
Available virtual memory : 140732395.9Mo
Available RAM : 24835.3Mo
Total virtual memory : 140737488.2Mo
Total RAM : 33992.8Mo
OS name : Microsoft Windows 11 Home
OS platform : Win32NT
OS version : 6.2.9200.0
>>Running as administrator. <<


--------------- Starting new GUI-client session - 11/22/2025 11:18:12 AM Build v1.08 - Build 1728.2 -----------------

Current DPI Awareness: 0

User's machine
Machine's name : DOUG
Thread's culture : en-US
Installed culture : en-US
Available virtual memory : 140732398Mo
Available RAM : 22974.1Mo
Total virtual memory : 140737488.2Mo
Total RAM : 33992.8Mo
OS name : Microsoft Windows 11 Home
OS platform : Win32NT
OS version : 6.2.9200.0
>>Running as administrator. <<


--------------- Starting new GUI-client session - 11/22/2025 11:22:31 AM Build v1.09 Beta - Build 1774 -----------------

Current DPI Awareness: 0

User's machine
Machine's name : DOUG
Thread's culture : en-US
Installed culture : en-US
Available virtual memory : 140732389.4Mo
Available RAM : 23079.1Mo
Total virtual memory : 140737488.2Mo
Total RAM : 33992.8Mo
OS name : Microsoft Windows 11 Home
OS platform : Win32NT
OS version : 6.2.9200.0
>>Running as administrator. <<


--------------- Starting new GUI-client session - 11/22/2025 11:44:23 AM Build v1.09 Beta - Build 1774 -----------------

Current DPI Awareness: 0

User's machine
Machine's name : DOUG
Thread's culture : en-US
Installed culture : en-US
Available virtual memory : 140732389.4Mo
Available RAM : 25041.2Mo
Total virtual memory : 140737488.2Mo
Total RAM : 33992.8Mo
OS name : Microsoft Windows 11 Home
OS platform : Win32NT
OS version : 6.2.9200.0
>>Running as administrator. <<


--------------- Starting new GUI-client session - 11/22/2025 11:46:23 AM Build v1.09 Beta - Build 1774 -----------------

Current DPI Awareness: 0

User's machine
Machine's name : DOUG
Thread's culture : en-US
Installed culture : en-US
Available virtual memory : 140732389.5Mo
Available RAM : 22567.1Mo
Total virtual memory : 140737488.2Mo
Total RAM : 33992.8Mo
OS name : Microsoft Windows 11 Home
OS platform : Win32NT
OS version : 6.2.9200.0
>>Running as administrator. <<


--------------- Starting new GUI-client session - 11/22/2025 11:57:29 AM Build v1.09 Beta - Build 1774 -----------------

Current DPI Awareness: 0

User's machine
Machine's name : DOUG
Thread's culture : en-US
Installed culture : en-US
Available virtual memory : 140732389.4Mo
Available RAM : 21823.3Mo
Total virtual memory : 140737488.2Mo
Total RAM : 33992.8Mo
OS name : Microsoft Windows 11 Home
OS platform : Win32NT
OS version : 6.2.9200.0
>>Running as administrator. <<


--------------- Starting new GUI-client session - 11/22/2025 1:43:28 PM Build v1.09 Beta - Build 1774 -----------------

Current DPI Awareness: 0

User's machine
Machine's name : DOUG
Thread's culture : en-US
Installed culture : en-US
Available virtual memory : 140732389.5Mo
Available RAM : 21011Mo
Total virtual memory : 140737488.2Mo
Total RAM : 33992.8Mo
OS name : Microsoft Windows 11 Home
OS platform : Win32NT
OS version : 6.2.9200.0
>>Running as administrator. <<


--------------- Starting new GUI-client session - 11/22/2025 1:59:45 PM Build v1.09 Beta - Build 1774 -----------------

Current DPI Awareness: 0

User's machine
Machine's name : DOUG
Thread's culture : en-US
Installed culture : en-US
Available virtual memory : 140732389.4Mo
Available RAM : 21871Mo
Total virtual memory : 140737488.2Mo
Total RAM : 33992.8Mo
OS name : Microsoft Windows 11 Home
OS platform : Win32NT
OS version : 6.2.9200.0
>>Running as administrator. <<


--------------- Starting new GUI-client session - 11/22/2025 2:03:34 PM Build v1.09 Beta - Build 1774 -----------------

Current DPI Awareness: 0

User's machine
Machine's name : DOUG
Thread's culture : en-US
Installed culture : en-US
Available virtual memory : 140732389.4Mo
Available RAM : 24697Mo
Total virtual memory : 140737488.2Mo
Total RAM : 33992.8Mo
OS name : Microsoft Windows 11 Home
OS platform : Win32NT
OS version : 6.2.9200.0
>>Running as administrator. <<


--------------- Starting new GUI-client session - 11/22/2025 2:16:19 PM Build v1.09 Beta - Build 1774 -----------------

Current DPI Awareness: 0

User's machine
Machine's name : DOUG
Thread's culture : en-US
Installed culture : en-US
Available virtual memory : 140732389.4Mo
Available RAM : 23279.4Mo
Total virtual memory : 140737488.2Mo
Total RAM : 33992.8Mo
OS name : Microsoft Windows 11 Home
OS platform : Win32NT
OS version : 6.2.9200.0
>>Running as administrator. <<


--------------- Starting new GUI-client session - 11/22/2025 4:05:25 PM Build v1.09 Beta - Build 1774 -----------------

Current DPI Awareness: 0

User's machine
Machine's name : DOUG
Thread's culture : en-US
Installed culture : en-US
Available virtual memory : 140732389.5Mo
Available RAM : 23051.9Mo
Total virtual memory : 140737488.2Mo
Total RAM : 33992.8Mo
OS name : Microsoft Windows 11 Home
OS platform : Win32NT
OS version : 6.2.9200.0
>>Running as administrator. <<


--------------- Starting new GUI-client session - 11/22/2025 4:14:41 PM Build v1.09 Beta - Build 1774 -----------------

Current DPI Awareness: 0

User's machine
Machine's name : DOUG
Thread's culture : en-US
Installed culture : en-US
Available virtual memory : 140732389.4Mo
Available RAM : 22266.3Mo
Total virtual memory : 140737488.2Mo
Total RAM : 33992.8Mo
OS name : Microsoft Windows 11 Home
OS platform : Win32NT
OS version : 6.2.9200.0
>>Running as administrator. <<


--------------- Starting new GUI-client session - 11/22/2025 4:21:51 PM Build v1.09 Beta - Build 1774 -----------------

Current DPI Awareness: 0

User's machine
Machine's name : DOUG
Thread's culture : en-US
Installed culture : en-US
Available virtual memory : 140732389.4Mo
Available RAM : 22313.9Mo
Total virtual memory : 140737488.2Mo
Total RAM : 33992.8Mo
OS name : Microsoft Windows 11 Home
OS platform : Win32NT
OS version : 6.2.9200.0
>>Running as administrator. <<

Re: Unable to open any old scenarios using 1744

Posted: Sat Nov 22, 2025 9:26 pm
by blu3s
DWReese wrote: Sat Nov 22, 2025 9:14 pm Blu3s,

Can you tell me how and where to find the file that you are requesting?

The program locks up as soon as I attempt to select a scenario file. I can move the cursosr around, but none of the buttons are responsive, and I can't exit the program. I have to reboot. Can I still get the file that you need? If so, how?
In your CMO installation, Log folder, there should be something called ExceptionLog with today's date

Re: Unable to open any old scenarios using 1744

Posted: Sat Nov 22, 2025 9:32 pm
by blu3s
Thanks, one more thing, in Options, can you enable the Log debug information to file ?

Image

Then, close Command, delete your Log file and launch command again. This time your Exception Log should show more information.

(Please, next time, if you can just attach the .txt in a zip would be better so the thread in the forum is not extremly long)

Thank you

Re: Unable to open any old scenarios using 1744

Posted: Sat Nov 22, 2025 10:19 pm
by DWReese
ExceptionLog_2025_11_22.txt
(11.79 KiB) Downloaded 33 times

Re: Unable to open any old scenarios using 1744

Posted: Sat Nov 22, 2025 10:27 pm
by blu3s
Can you please create a new folder in C:\ProgramData called CMO and change Command.ini entry of webview folder to


CustomFolder_WebviewCache = C:\ProgramData\CMO

Thanks,

It seems there's an issue with the webview2 initialization.

Re: Unable to open any old scenarios using 1744

Posted: Sat Nov 22, 2025 10:46 pm
by DWReese
I did everything that you said, and I rechecked everything but it still will not load any old scenarios, and it locks up upon reaching that screen.

Re: Unable to open any old scenarios using 1744

Posted: Sun Nov 23, 2025 8:06 am
by blu3s
I'm really sorry, but that's quite strange.

Let's recap:

Now that your Command.ini points to C:\ProgramData\CMO, do you get the pop-up saying “Microsoft Edge can't read and write to its data directory”?

Can you check if the EBWebView folder has been created in C:\ProgramData\CMO?

In 1728.2, this directory was: C:\Windows\Temp

You should have an EBWebView folder there. If it exists there, can you change the field from
CustomFolder_WebviewCache = C:\Windows\Temp

and launch CMO again?

Re: Unable to open any old scenarios using 1744

Posted: Sun Nov 23, 2025 8:22 am
by Nikel
IMO you should revert, and the "WebView Caches" folder should not be created, by default, inside CMO folder.

It will cause too much trouble when the official patch is released.

Re: Unable to open any old scenarios using 1744

Posted: Sun Nov 23, 2025 8:43 am
by blu3s
CMO folder is the writable folder where CMO writes the logs, the autosaves, etc

So it shouldn't have issues writing the folder if everything is working fine.

Additionally there are few places where you can point the caches like ProgramData, or C:\Users\user\AppData\Local that shouldn't have problems at all.