16 Posts
10
43820
XPS 15 7590, Memory Integrity on causes an inaccessible boot device
Hey all,
Just wanted to report a minor bug with a fresh install on Windows 11 22H2 on XPS 15 7590.
When trying to turn on Memory Integrity under Device Security / Core Isolation, upon next reboot i get a blue screen with Inaccessible Boot Device.
Yes, I'm using the latest Intel Chipset Drivers and XPS 15 7590 firmware.
Yes my Windows 11 is up to date.
expired on August 2, 2020. DELL-Admin>
sheps89
3 Posts
2
September 28th, 2022 08:00
Good to see this issue getting traction here on the Dell forums too. There's a post on the Windows Insider forums with a few of us confirming this issue on our XPS 7590 (looks like you found it already @Aliomenti
I'm currently booting fine on 22H2 with WSL2 running, by disabling Virtualization Direct I/O in my BIOS. Thankfully I don't need this for my use cases. I'm also running the Windows Subsystem for Android fine with this option disabled. Virtualization (VT-x) is of course enabled.
I also have the latest drivers, firmware, BIOS, etc installed.
Aliomenti
4 Posts
1
September 28th, 2022 08:00
I have the same issue on XPS 15 7590.
BIOS is configured in RAID mode which is the default on 7590. I have not attempted reinstalling in AHCI mode to see if that works.
I first encountered this error on the Windows 11 insider beta channel when 22H2 was released 6 months ago, disabling virtualisation enabled Windows to boot. I logged a feedback report with Microsoft at the time and left Memory Integrity disabled.
Today I re-enabled virtualisation in order to take advantage of the Windows subsystem for Android which has just been released to Windows insiders in the UK but again faced a stop code on reboot with error 'Inaccessible Boot Device'. Disabling virtualisation allowed Windows to boot.
BIOS firmware is up to date.
I have submitted a new feedback report to Microsoft, but this seems to be a specific incompatibility between the XPS 15 7590 and Windows 11 22H2. Obviously with 22H2 now being released to the general public, this is a much bigger issue that Microsoft and Dell need to solve ASAP.
Aliomenti
4 Posts
2
September 28th, 2022 09:00
Confirmed, disabling Virtualization --> VT for Direct I/O allows Virtual Machine Platform to be enabled.
Geeooff
2 Posts
0
September 28th, 2022 16:00
Thanks for this, you saved my day.
Unfortunately I've seen this after clean reinstall and BIOS factory reset... for nothing.
d5123101
457 Posts
0
September 28th, 2022 17:00
If this issue was caused by going from 21H2 to 22H2 on WIndows 11, it is better just to wait out upgrading till issues like this are patched.
watnaron
4 Posts
0
September 28th, 2022 20:00
After I tried twice and failed before found this discussion.
Now I am able to upgrade from Windows 11 21H2 -> 22H2 with Windows 11 Instaltion Assistance succesfully by just disabling Virtualization Direct I/O in BIOS.
nzcoder
5 Posts
0
September 29th, 2022 21:00
Unfortunately, if I disable the Virtualization Direct I/O in BIOS, it enters a recover mode which asks me to input the bitlocker key.
I have to enable it. At least I can use windows 11.
watnaron
4 Posts
0
September 29th, 2022 22:00
I also too. But you should have BitLocker Key already, right? You can grab your bitlocker key before you change the setting from microsoft account.
nzcoder
5 Posts
0
September 30th, 2022 15:00
Does that mean I need to recover the system so I would lose my data?
watnaron
4 Posts
0
September 30th, 2022 16:00
Nope. Bitlocker is asking because you have change a setting and after key in, it is just allow you to change. All your data will be intact.
Saltgrass
3 Apprentice
3 Apprentice
•
4.3K Posts
0
October 1st, 2022 05:00
There is a new update available, KB5017389. It mentions repairing a problem. I do not know if this situation is involved in what you are seeing.
Addresses an issue that affects some processors. This issue occurs when you turn on Hyper-V and kernel Direct Memory Access (DMA) protections.
Frank_Just
18 Posts
1
October 1st, 2022 13:00
I have tested it. It doesn't solve the issue
zo0ok
2 Posts
0
October 2nd, 2022 00:00
I tried KB5017389 on my XPS 15 7590, Windows 11 22H2.
It did not help. I still get Blue Screen on startup and need to use a Restore Point.
I am thinking about disabling Virtual Direct I/O... but I think I need it for Hyper-V to run windows servers in docker.
zo0ok
2 Posts
0
October 2nd, 2022 02:00
Yes, Disabling Virtual Direct I/O works for me. I wanted to run Docker with Hyper-V on Windows 11 22H2, on XPS 15 7590, and now I can do it.
Bios settings: SATA=AHCI, Virtualization=ON, Virtual Direct I/O=OFF.
I also installed KB5017389.
After turning Virtual Direct I/O OFF I had to give my recovery key to be able to start Windows, but after that everything was ok and nothing changed.
For me it works with AHCI, I do not know about RAID.
nzcoder
5 Posts
0
October 2nd, 2022 16:00
Ok I tried to disable Virtual Direct I/O. After entering the bitlocker key I can enable Core Isolation in win11. I use RAID in bios, not AHCI.