Skip to content

Bug: Files is not fully working when Memory Integrity is turned on on Windows #16343

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
BenCheung0422 opened this issue Oct 15, 2024 · 4 comments

Comments

@BenCheung0422
Copy link

Description

All the pinned entries and entries of Quick access, as well as recently used files do not show up in the app after turning on Memory Integrity. Is that something expected, that the app is incompatible with Memory Integrity?

Steps To Reproduce

  1. Turn on Memory Integrity in Core Isolation in Windows Security
  2. Reboot
  3. Start Files

Requirements

All the entries should show as normal.

Files Version

3.7.11.0

Windows Version

10.0.22631.4317

User ID

No response

Log File

debug.log

@Josh65-2201
Copy link
Member

Thanks for the report, We're tracking this in #15410. You can check there or click subscribe in the right sidebar for updates. Please try the workaround there. Memory integrity shouldn't be related to this issue.

@BenCheung0422
Copy link
Author

BenCheung0422 commented Oct 15, 2024

Okay thanks. It happened when I firstly turned on Memory integrity, and at the same time, a gigabyte driver was disabled by Security. The second time I reinstalled gigabyte center and returned on integrity. It does now show up. I doubt the issues here, but I did not restart Files after opening the app when the issue comes out and I do have starting on startup on.

@yaira2
Copy link
Member

yaira2 commented Oct 15, 2024

I don't think it's related to Memory Integrity since I have it enabled and haven't been able to reproduce this issue. That said, we're actively working to redo the relevant code and we're hopeful that'll help for this issue.

@BenCheung0422
Copy link
Author

BenCheung0422 commented Oct 15, 2024

I think so, since the second time everything goes fine surprisingly, after experiencing the issues in the first time. There might be a mixed factor that a driver (that is Gigabyte App Center driver, gdrv3.sys) was forcedly disabled by Windows with Memory Integrity, causing misfunctioning in the app, in which the factor had gone in the second time as I reinstalled that.

Turning on/off Memory Integrity requires a reboot, so I said them to be "first/second time" config change and reboot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants