You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
install windows on Steam deck, install steam, install Resident Evil2 remake. Run it - great, it works!
keep using ntfs, but use quibble to boot now - the game crashes now.
switch back to native boot loader - works again
The issue appears regardless of the FS used. I was thinking it's WinBtrfs fault, but I don't have it installed. Tried to not load btrfs.efi at boot - same result.
Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program re2.exe because of this error.
Program: re2.exe
File:
The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.
Additional Data
Error value: 00000000
Disk type: 0
C000001D is STATUS_ILLEGAL_INSTRUCTION, so that's interesting. Maybe there's some sort of instruction set that Quibble should be initializing. Let me look into it.
Something I could easily reproduce:
The issue appears regardless of the FS used. I was thinking it's WinBtrfs fault, but I don't have it installed. Tried to not load btrfs.efi at boot - same result.
Here is the error message in application events:
followed by
report.wer content (not sure how useful)
The text was updated successfully, but these errors were encountered: