
UNSOLVED
Closed
AY
And Ye Shall Find
2 Intern
•
117 Posts
0
3728
April 17th, 2023 19:00
XPS 8950, memory Integrity off, no incompatible drivers found
After a recent Reset (i.e., clean Windows 22H2 install from the cloud) Windows turned off Memory Integrity (under Core isolation). I'm running Win22H2, build 22621.1555. Windows Security (no 3rd party A/V). No incompatible drivers were found, either with the Scan in Windows Security or in the drivers tab of Sysinternals/autoruns (all drivers are Verified). I enabled Virtualization Based Security in Group Policy, but that didn't help (I've since restored this to "Not Configured"). I enabled Virtual Machine Platform, Windows Hypervisor in Optional features, but this also didn't help. Windows is up to date, SFC and DISM both come up clean. No issues shown in Device Manager, including hidden devices. All resident applications are also installed on another device, where Memory Integrity is running without issues. If anyone's had experience with this, any suggestions will be appreciated. Thank you.
1 person also has this problem
Responses (22)
Solutions (0)
@And Ye Shall Find wrote:
Core Isolation
Virtual Machine Platform, Windows Hypervisor in Optional features,
I thought it was one or the other. I didn't think you could be both concurrently.
See msinfo32.
Dell Rockstar
Microsoft Windows and Apple iOS Developer (Retired)
- Like many of you, I can appreciate a good game-engine.
- I answer questions here, but I'm not a Dell employee.
- Consider giving posts you like a "thumbs-up"
- Posting models-numbers and software versions speeds trouble-shooting.
- Click "Mark as Accepted Answer" on any post that answers your question best.And Ye Shall Find
2 Intern
•
117 Posts
1625
0
Posted April 18th, 2023 03:00
well I'm really not sure, but was able to add both in Optional Features - just trying different iterations suggested by others. So far, no joy!
Surprise, I hit this too on W11 Win22H2, build 22621.1792!!
It showed up in the Action Center a few days ago, probably after the last Patch Tuesday?
I did the SFC, DISM, and Autoruns too... nothing found. Even looked in Device Manager for possible Hidden drivers... nothing. Only driver related error is the Ethernet adapter. It does have a cable in it and attached to our router, but the device is DISABLED. I use it occasionally if I require faster speed, but since my ISP upgraded me to 1Gbps my wireless can reach the low 900bps (never get the max. 940bps though). I doubt that is doing it.
So, I decided to set it via the Registry editing. It seems to be staying set.

And Ye Shall Find
2 Intern
•
117 Posts
1362
0
Posted May 13th, 2023 17:00
Thanks for the input @ispalten . I was hoping for a more holistic solution vs modifying the Registry, but am running out of alternatives. I've already deleted several "old" drivers that I thought would do no harm (using RAPR) but haven't gone hog-wild there. The next thing I was going to try was uninstalling SupportAssist (which honestly, I've been itching to do anyway) which someone somewhere suggested might be the culprit.
Regarding the Registry mod, one point to note is that my other Dell - a Vostro 5620 - isn't showing the Memory Integrity error, and it does contain the
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity] "Enabled"=dword:00000001Registry Key / Dword. On my problematic XPS, the key is missing entirely This certainly supports adding this key as a solution.And Ye Shall Find
2 Intern
•
117 Posts
1342
0
Posted May 14th, 2023 07:00
A few people at ElevenForum thought that "old" drivers could result in Memory Integrity being disabled, yet not be flagged, which is why I was experimenting with RAPR. Saving space is nice, but not the objective. I'm not entirely confident that just because RAPR says it's old though, doesn't mean something somewhere isn't using it, so I didn't go too far down this road.
"the bigger question I can't find an answer to is "What is the actual reason it cannot be turned on, since it doesn't show any driver causing this, is there another reason?"
EXACTLY. My other thought was whether setting the Dword to "1" in the Registry actually does anything besides enabling us to check a box in Windows Defender. Is it then really on, or just "pretending"? Might it have been on all along, with Windows showing a bad message?
I view Memory Integrity as an incremental protection. I don't believe it's necessarily "needed" until something happens, and you wished it was on. Some techies at ElevenForum actually go out of their way to disable it.
At least one person did suggest SupportAssist could be the culprit. I've learned through much trial (and tribulation) there are 6 Services that need to be stopped - some in sequence - to truly disable SupportAssist, but even then, I see the greedy, resource-hogging, heavy-handed, intrusive app doing things in the background without permission or notification. It has to go! I'm away from my XPS for possibly weeks, but will give that a try, and let you know if it made a difference.
I hear you. I can be dangerous too, doing something I don't know or understand...
RAPR is just such a program. See my screen capture above. First I know Windows via Device Manager CAN back-level a driver. Good to know and do if you get a new driver that doesn't work too well.
However, just deleting what appears to be duplicate entries could be disastrous. First, the INF files, some have the same names even, and that means more than one copy exists on your PC.
First thing to do, on the title bar, RMB and CHECK all items... this will give you more info.
Now look at my list of BlueTooth items:
Note the highlighted line. That and the one below it, same version, same date, different name for the INF file. If I click OLD DRIVERS, all but the line with a Device Name entry is marked blue so you CAN delete them as they are checked (and so are all the others the program determines to be old). Now here is the RUB... they basically are the same...
One downside of deleting files, Device Manager KNOWS which one was the last and uses that to back-level the driver....
I'd ONLY consider using that program to SAVE SPACE if I needed it.
Some reading if you are interested:
https://www.edtittel.com/blog/rapr-v0-11-92-remains-a-real-gem.html (similar case with Intel files).
https://www.ghacks.net/2018/01/31/driverstore-explorer-manage-the-windows-driverstore/
Now this is what MS says about the Driver Store:
https://learn.microsoft.com/en-us/windows-hardware/drivers/install/driver-store
It clearly states in these 2 paragraphs what Driver Store is and contains:
Now reading those, two things stick out.. Driver SHOULD be good and trusted... AND it states in the last paragraph programs should not add or delete entries????
Reading this recent page explains the driver process as well, https://www.computerworld.com/article/3322513/how-to-reduce-windows-driver-bloat-remove-outdated-drivers.html
However, my thought, bottom line, is take out the wrong file you might not be able to roll-back a driver. Get a corrupted driver or one that doesn't work, you might have little or no recovery possible.
I'd use that program for information only.
Still doesn't answer WHY not driver was shown that was stopping Core Isolation, does it?
This link, https://www.elevenforum.com/t/unable-to-find-the-incompatible-driver-s-preventing-core-integrity.9790/ is interesting.... implies it could be somewhere not IN Driver Store... might not even be used?
Tool listed didn't seem to be of much help to me either?

And Ye Shall Find
2 Intern
•
117 Posts
1322
0
Posted May 14th, 2023 12:00
@ispalten Right - MSFT doesn't recommend removal, so it's probably best not to. Maybe they should force Intel and others to clean up some of their garbage as well. I can understand maybe 2 older versions of a driver for purposes for rollback, but 20? Also, if trying to make space, then nothing less than 10 MB is probably significant / worth the risk.
If MSFT security didn't fail to identify the offending driver (or didn't see an issue where none exists), we probably wouldn't even be having this discussion. They've had so many recent W22H2 issues with Windows Security (e.g., LSA, Core Isolation, Memory Integrity, Kernel-mode stack protection) it's hard to take any of their warning notifications seriously. Maybe best to just sit back, and wait for them to get their act together. They've obviously built something too difficult to maintain, and are clearly doing a horrible (i.e., irresponsible) job regression testing.
Well, 2 points:
- Intel might not know what level you are on, well they should, but not check it for processing older INF files? You, as the user can exercise those same INF files to put in older drivers... so they probably don't want to take a chance.
- Quite possible there ARE problem drivers, but NOT in places where Windows would check, but see one running? Why not tell you the name though? I'm thinking some utility. For instance, I have Revo Uninstaller, and it is NOT on C:. However, one of its drivers are in C:\windows\system32\drivers. RevoFLT.SYS, RAPR doesn't show it in its list. Even the SysInternals tool I've installed on a different drive doesn't appear and they have drivers.
RAPR and possibly MS Core Isolation only I think looks at the DriverStore in C:\Windows\System32\drivers. Ii seems RAPR just reads those subfolders in FileRepository?
Not knowing where Core Isolation looks, and it could be also looking at LOADED drivers, makes it hard to know if you actually have a suspect driver or not?
EDIT: Oh, open a CMD prompt with Administrator rights and run DRIVERQUERY /V /FO TABLE and probably redirect the output to file with >X:\DQUERY.TXT and then open it, it is/can be long, and it is easier to read. I had at least 2 off the C: drive. Run DRIVERQUERY /? to see all the options.

And Ye Shall Find
2 Intern
•
117 Posts
460
0
Posted May 14th, 2023 17:00
@ispalten You may be right - I have maybe 15 "local" apps populated on my D drie, including Revo and SysInternals, and I've noticed (to my unpleasant surprise) that some have written to the Registry and /or populated drivers in System32. It hardly lets MSFT off the hook, though - if Memory Integrity is being disabled based upon some search criteria, their reporting mechanism should key off that same criteria.
Re your point about Intel "not knowing", I use their Driver & Support Assistant, which actually contains a history of the installed drivers, so yes, they should. I believe it's more a matter of not caring, as well as the point you raised about enabling roll-back.
Thank you for DriverQuery, Very handy. The list generated seems quite different from what's shown in RAPR. Historically I've used "Get-WindowsDriver -Online -All" to return a (complete?) list of installed drivers.

ispalten
7 Practitioner
•
2652 Posts
•
9776 Points
1349
0
Posted May 14th, 2023 06:00
@And Ye Shall Find , I picked up RAPR, but was not able to make much out of it? That just showed the INF files. Many even were dup's. Not unusual for INF files to be left, that is how you can ROLL BACK a driver it appears. No indication any of those are the problem. Program is more to save space than anything else. Look at my Bluetooth drivers:
A lot of dup's and space used by all of them, minimal compared to my C: disk free space I have.
I had used the Registry path once before, so I had the key, but it was set to 0, which is off. Changed it to one, Core Isolation on.
Yes, that does make it work, but the bigger question I can't find an answer to is "What is the actual reason it cannot be turned on, since it doesn't show any driver causing this, is there another reason?"
I sometimes wonder if that is even needed? I've never seen something 'happen' that would have been 'saved' if I had that on that I know of? What is the HARM of manually overriding the setting?
I've had Support Assist IN and OUT of this XPS... I get some Event Viewer re-configuration warnings with it and the Remediation Server running. I'm wondering if that Service is part of my problem. I think once I turned it off, I got the Windows warning it was off. All those errors kicked in after the most recent version of SupportAssist was installed by Dell Update?
Before that last Update of SupportAssist I could NOT set System Repair n it. Somehow the last update enabled it and I got a 'surprise' Action Center message that a System Backup was done? Only then did I look at the settings for Support Assist and it was set much to my surprise. Once I disabled the Service, that no longer works or can be set, so the two are connected with System Repair and re-configuring being done on all application on each boot.
Possible that Core Isolation is connected with these?