fiza Posted November 11, 2021 Posted November 11, 2021 We have 8 HP 250 G8 laptops (not from DfE) that we are having issues imaging using MDT/WDS. I have downloaded the HP WINPE 10 drivers from their site and put these in our WINPE image. The image looks like it deploys but on first reboot we get a blue screen with "Inaccessible boot device" These laptops have Hynix NVMe drives. I have no idea what is going wrong. A quick Google and it seems we need to use F6flpy-x64 - VMD drivers which we have already done. Does anyone have any ideas please?
Duke5A Posted November 17, 2021 Posted November 17, 2021 Are you certain the install WIM has the storage drivers? Import the storage drivers from that WinPE pack into the WDS console and give it another go. If not it might be something to do with the disk configuration in the answer file. 1
Fluke Posted September 23, 2022 Posted September 23, 2022 We have 8 HP 250 G8 laptops (not from DfE) that we are having issues imaging using MDT/WDS. I have downloaded the HP WINPE 10 drivers from their site and put these in our WINPE image. The image looks like it deploys but on first reboot we get a blue screen with "Inaccessible boot device" These laptops have Hynix NVMe drives. I have no idea what is going wrong. A quick Google and it seems we need to use F6flpy-x64 - VMD drivers which we have already done. Does anyone have any ideas please? @fiza did you ever get this sorted? We seem to be in the same boat. Added the Intel Rapid Storage driver for 11th gen intel cpus (f6vmdflpy-x64) and winpe can see the C: drive and gets to first reboot. CMTrace looks mostly ok but oddly states not enough disk space to install x and y driver - although they are ~512GB nvme drives.
fiza Posted September 23, 2022 Author Posted September 23, 2022 @fiza did you ever get this sorted? We seem to be in the same boat. Added the Intel Rapid Storage driver for 11th gen intel cpus (f6vmdflpy-x64) and winpe can see the C: drive and gets to first reboot. CMTrace looks mostly ok but oddly states not enough disk space to install x and y driver - although they are ~512GB nvme drives. No we didn't. We ended up manually installing windows and then using PDQ to deploy all the apps.
Fluke Posted September 23, 2022 Posted September 23, 2022 No we didn't. We ended up manually installing windows and then using PDQ to deploy all the apps. That's not what I wanted to hear but thanks for the update!
hellgate24 Posted September 26, 2022 Posted September 26, 2022 I seem to recall having a similar issue with an HP G8 (we only bought one) and SCCM. Disabling secure boot, letting it image and then re-enabling it after it had built was the workaround. Might be worth a shot.
qwertyuiop1 Posted January 23, 2023 Posted January 23, 2023 Try changing the SATA mode to AHCI then redeploying. Sometimes when it's set as RAID, that happens
nwkeene Posted January 23, 2023 Posted January 23, 2023 as mentioned above.. but also look at this post as i had trouble with NVMe drives. It was to do with the Intel VMD mode in the bios, turn it off and the 'C' drive will appear for PXE use. you may need to use AHCI mode rather than raid mode as mentioned above.
Jakeno13 Posted January 23, 2023 Posted January 23, 2023 We have had similar issues with HPG9 units these required us to run the drivers as an exe in the task sequence I also followed this guide to check the appropriate drivers were installed during the task sequence https://www.deploymentresearch.com/add-driver-fallback-to-mdt-lite-touch/ hopefully this is of some use Thanks Jake
lparry Posted April 5, 2024 Posted April 5, 2024 Another workaround for this that we found - create a new task sequence (as we found the same issue affects some dells & lenovo thinkpads) and force the IsUEFI variable to true during the formatting stage (and disabling 'Format & Partition Disk (BIOS)') The issue we found is that some devices just seem to choose the BIOS version incorrectly, I believe there's another way to fix it via IP helpers but I found this easier to implement!
Passat1983ICTech Posted April 5, 2024 Posted April 5, 2024 Hello have you tried to update the bios then running the image again
WHOAMI3904 Posted May 13, 2024 Posted May 13, 2024 We had this with our G8's and G9's. I ended up updating the both ADKs to the latest versions and then loading the latest HP drivers into WDS and MDT. After this it seemed to Image 90% of the time. However I did notice there was less issues when installing windows 11 compared to 10. Hope this helps someone
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now