XPS

[Wesleyrpg]

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.

<Your purchased 1 year warranty expired on August 2, 2020. DELL-Admin>

[Tesla1856]

---

@prasathchan wrote:

I have the same problem. It's not only for Memory Integrity. If you Enable Virtual Machine Platform or Hyper-V or Hypervisor Platform, the system fails to boot and show Inaccessible Boot Device. Once you Disable Virtualization from BIOS, it boots flawlessly.

I believe Enabling Virtualization related service or app changes the Boot configuration and fails to boot.

Can anyone suggest a solution for this. This happens to me after upgrading to Windows 11 22H2

---

Do you also have a XPS-15 (7590) with the latest firmware?

Yes, it's my understanding that VT, Hyper-V, and Virtualization Based Security all use the same technology sub-system.

Are you running the machine in RAID/Intel-RST/ Intel Optane Memory and Storage Management mode, or AHCI ?

[Tesla1856]

---

@Wesleyrpg wrote:

Just wanted to report a minor bug with a fresh install on Windows 11 22H2 on XPS 15 7590.

---

Just verified ... it is on the list.

https://www.dell.com/support/kbdoc/en-us/000187485/dell-computers-tested-for-upgrade-to-windows-11#X...

[watnaron]

I also have XPS15 (7590) with everything up to date (also check with SupportAssist), but it is still inaccessible boot device after using windows 11 update to 22H2. Try twice with no luck.

[Saltgrass]

Several of the drives that might have come with that system, have firmware updates. 

The Intel Management Engine updates may also be important, but I will assume you already have that one.

[Aliomenti]

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.

[sheps89]

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]

Confirmed, disabling Virtualization --> VT for Direct I/O allows Virtual Machine Platform to be enabled.

[Aliomenti · Accepted solution]

Disabling Virtualization --> VT for Direct I/O also allowed Memory Integrity to be enabled. I suspect those having issues upgrading to 22H2 should be able to if they disable VT for Direct I/O only leaving Virtualization Enabled.

[Geeooff]

Thanks for this, you saved my day.
Unfortunately I've seen this after clean reinstall and BIOS factory reset... for nothing.

[d5123101]

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.