Running Portable Causes Hard Crash

[thedeuceII]

The problem:

When opening the MO2 v2.5.2 from a normal directory from the portable 7z release, it causes a dotnet framework error in the OMODFramework.dll. The exact error is related to CAS policy in the current version of dotnety framework (?) (I'm a developer, too, and I haven't come up against this myself with dotnet, so I have no suggestions there).

I am attaching the screenshot of the error. I have no further information. The application refuses to load further, and I have tried reinstalling the latest .net redist package as well. That didn't help.

To Reproduce:

1. Open the App
2. See Error
3. Hard Crash
4. ...
5. Get logs
6. ...
7. Profit?

Environment:

Machine Specs:

• AMD Ryzen 7 5800X 8-Core Processor
• 32GB GSkill FlareX (C14)(Binned)
• ASUS Crosshair VIII Hero
• ZOTAC Gaming GeForce RTX 4090 AMP Extreme AIRO

Operating System

• Windows 11 Professional
• Version: 23H2 (22361.3958)
  

Details:

Link to Mod Organizer logs:

N/A

USVFS:

https://gist.github.com/thedeuceII/9062853ce2ef49c7aad4c0187d2106f5

MO Interface:

https://gist.github.com/thedeuceII/d6168988ae548658b02aaa981ae6fd7b

[Liderate]

The mo_interface.log shows many of the files being blocked which is likely the problem. Unblock the archive from its properties then extract it.

[AnyOldName3]

The archive release isn't really meant to be used directly, it's meant for tools like Wabbajack that deal with unblocking the files automatically. Normal users should use the installer, which bypasses this problem.

[thedeuceII]

The mo_interface.log shows many of the files being blocked which is likely the problem. Unblock the archive from its properties then extract it.

I'll give this a try!

Thank you for looking through the logs. Anything special I need to do to unblock OMODFramework?

[Silarn]

https://bin95.com/articles/safety/unblock-downloads.htm

I recommend doing this to the archive before you extract it otherwise you'll likely need a script to automatically unblock all of the files since I doubt you want to do that manually.

Using the installer also avoids this issue.