Known Issues

See this page for known issues, please contact [e-mail] if you cannot fix the issue.

---

Current

• Updater: No Authorisation method provided

• DLL Fault

• Spaces in paths

• Run out of storage

• Windows defender false positive

• Firewall blocked

• VPN support

---

Updater: No Authorisation method provided

Example of the Error

The Marso Updater shipped with 25.1.0 had an authorisation issue that has been solved with 25.1.1

To resolve this issue, download the latest version of the updater, copy it to your install folder, and run it directly. This should prompt you to login and install the latest version.

DLL Fault

Users may sometimes experience an application fault. This will not appear in the log and will look like the application has just closed without any further information. To confirm you can look in the event viewer and you should see an error like this:

Faulting application name: M-XR_Marso.exe, version: 0.0.0.0, time stamp: 0x67aa8eb2 
Faulting module name: tcl86t.dll, version: 8.6.2.13, time stamp: 0x6547c47c 
Exception code: 0x80000003 

Resolution

To resolve just relaunch the application and continue. If any job was running during the crash it will have to be restarted.

---

Spaces in paths

Currently having spaces in paths is not supported. So most steps will fail if a path includes a space. This covers calibration and processing. As a solution for the time being it is recommended to move the data to a location where there are no spaces in the path.

---

Run out of storage

If the scratch directory drive fills up (due to Marso or other programs) then windows will throw a Storage Warning, and jobs in Marso will fail.

If the scratch directory is on the C: drive and there is insufficient free space, Marso will fail to launch.

Resolution

To resolve you must clear space on the drive, usually we aim for 250GB of free space. Then the program can be relaunched and job can be restarted safely.

---

Windows defender false positive

Windows defender has an AI based threat detection system that on some systems detects a portion of Marso as a threat. The threat should look like Trojan:Script/Wacatac.B!ml

Resolution

To resolve, you will need to add an exception on this path %LOCALAPPDATA%/M-XR/Maestro/Unpack

If you are unable to add an exception due to security policy please contact [e-mail]

---

Firewall Blocked

If you have your firewall blocked and set not allow any connections then Marso will crash and will not provide a clear error. Marso requires external internet connection to run in order to connect to our DRM system.

To resolve, add a whitelist to your firewall for the Marso program and any program in this directory %LOCALAPPDATA%/M-XR/Maestro/Unpack

You may also need to add exclusions for the endpoints Marso needs to connect to:

1. https://api.keygen.sh/* - HTTP/HTTPS (80/443) - License validation

2. *.mongodb.net - TCP ports 27015-27017 - Database

3. *.backblazeb2.com - HTTP/HTTPS (80/443) - Binary hosting

---

VPN Support

Currently based on our testing, Marso does not work with VPNs. They can tried at the user’s own risk but we do not expect them to work.