Hi Community,
We are using the Dell Latitude 54XX series and have successfully created multiple Windows 11 23H2 images by injecting Dell’s latest Intel Rapid Storage Technology (VMD) driver using NTLite. However, when attempting the same process with Windows 11 24H2, we encounter a BSOD with the Stop Code: “INACCESSIBLE_BOOT_DEVICE.”
Interestingly, if we skip injecting the driver into the boot.wim using NTLite and instead manually load the driver during the Windows Setup wizard, the installation completes successfully. In this case, Windows boots normally without any crashes or BSOD.
Here’s the process we’ve followed:
Injecting the Intel Rapid Storage Technology (VMD) driver into boot.wim > Microsoft Windows Setup (x64) using NTLite (Version: 2025.1.10263, 64-bit): This approach works flawlessly with Windows 11 23H2 but fails for Windows 11 24H2, causing the BSOD.
What could be the root cause of this issue when the driver is injected with NTLite for Windows 11 24H2?
Is it possible that there are changes in the boot.wim structure for 24H2, or could there be compatibility issues with this specific driver and NTLite?
Looking forward to your insights and recommendations.
We are using the Dell Latitude 54XX series and have successfully created multiple Windows 11 23H2 images by injecting Dell’s latest Intel Rapid Storage Technology (VMD) driver using NTLite. However, when attempting the same process with Windows 11 24H2, we encounter a BSOD with the Stop Code: “INACCESSIBLE_BOOT_DEVICE.”
Interestingly, if we skip injecting the driver into the boot.wim using NTLite and instead manually load the driver during the Windows Setup wizard, the installation completes successfully. In this case, Windows boots normally without any crashes or BSOD.
Here’s the process we’ve followed:
Injecting the Intel Rapid Storage Technology (VMD) driver into boot.wim > Microsoft Windows Setup (x64) using NTLite (Version: 2025.1.10263, 64-bit): This approach works flawlessly with Windows 11 23H2 but fails for Windows 11 24H2, causing the BSOD.
What could be the root cause of this issue when the driver is injected with NTLite for Windows 11 24H2?
Is it possible that there are changes in the boot.wim structure for 24H2, or could there be compatibility issues with this specific driver and NTLite?
Looking forward to your insights and recommendations.
Last edited: