Skip to content
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

Windows 10/11 core isolation prevents the driver from loading #997

Closed
androidacy-user opened this issue Sep 17, 2021 · 6 comments
Closed

Comments

@androidacy-user
Copy link

androidacy-user commented Sep 17, 2021

Describe the bug
With core isolation (memory integrity) turned on, the kernel driver will not load, with windows presenting a popup saying that it's been blocked due to a vulnerability in the driver. The learn more button leads to a microsoft page on core isolation.

To Reproduce
Steps to reproduce the behavior:

  1. Enable driver loading
  2. Reboot

Expected behavior
Driver loads fine regardless of device security settings.

Screenshots
n/a

Desktop (please complete the following information):

  • OS: Windows
  • Version: 11/Insider build

Additional context
Please, do not just suggest disabling core isolation. Microsoft already did that, and it's never a good idea to say just disable these core windows security features for our software to work fully.

@dmex
Copy link
Collaborator

dmex commented Sep 19, 2021

windows presenting a popup saying that it's been blocked due to a vulnerability in the driver

Why hasn't Microsoft reported any vulnerabilities, contacted anyone or published anything about this?

never a good idea to say just disable these core windows security features

Microsoft hard-coded copies of our binary certificates into the Windows kernel CI and they cannot be removed from the operating system. It's been done entirely in secret without anyone knowing about it and I've tried contacting them but Microsoft hasn't replied or given an explanation or reasons for doing this yet.

@androidacy-user
Copy link
Author

Meant to comment not close, sorry lol

Anyway

Unfortunately I don't really know more than I posted originally. The last time I got a notice like that, it was windows 10 and an old driver that wasn't compatible with memory isolation. But that was awhile ago and doesn't make sense in this case.

@kristibektashi
Copy link

Microsoft hard-coded copies of our binary certificates into the Windows kernel CI and they cannot be removed from the operating system. It's been done entirely in secret without anyone knowing about it and I've tried contacting them but Microsoft hasn't replied or given an explanation or reasons for doing this yet.

Because you are competition to them. They have their own tool for viewing processes called Task ManagerProcess Explorer

@dmex
Copy link
Collaborator

dmex commented Oct 27, 2021

Because you are competition to them. They have their own tool

The reason they've provided us for blocking our driver is for the exact same feature bundled with Process Explorer. To say this isn't anti-competitive and illegal would be an understatement.

@Bartolomeus-649
Copy link

on my machine (Microsoft Windows [Version 10.0.19043.1348]) the kernel driver does not show up as problematic, still, I have other drivers preventing enabling memory integrity:

image

@dmex
Copy link
Collaborator

dmex commented Jun 14, 2022

#1142 (comment)

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

No branches or pull requests

4 participants