Skip to content

Work around MO2's VFS breaking newer versions of WB #689

@badgerbadgerdroid

Description

@badgerbadgerdroid

Latest Nightly

  • [ X] I have tried the latest nightly build and the issue still occurs.

Asking on Discord/AFKMods

  • [ X] I have asked on Discord/AFKMods and posted as requested by Utumno

BashBugDump

BashBugDump.log

Details of the Issue

image (1)

Description

Replace this section with a description of the issue. Describe what you wanted
the program to do and what it did instead.

Step-by-step reproduction

Attempting to launch Wryebash causes the above error, even old versions that previously did work (12.1).

The only common theme I found was the affected devices were my 2 Laptops which had upgraded to 24H2 Windows 11 upgrade recently.
The same mod list on my other devices one Windows 10 and one Windows 11 23H2 both allowed Wryebash to launch successfully.

(This is launched through MO2 using a stock game install inside the MO2 folder for Fallout 4)

Metadata

Metadata

Assignees

Labels

A-filesystemArea: File operations, filenames handling, OSs support (everywhere)C-bugCategory: Bug, an acknowledged defect in the programM-relnotesMisc: Issue should be listed in the version history for its milestone

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions