Seite 1 von 1
UEFI install getting stuck on HP workstation/laptops
Verfasst: 29 Mär 2018, 17:16
von ttblum
Hello,
I am able to unattended install Windows 10 OK (win10-x64) on different models of Dell and HP worksations using an Opsi UEFI license.
However, when I deploy to HPs it boots to the following screen after Windows installs showing:
Code: Alles auswählen
X:\windows\system32>c:\opsi\startnet.cmd
The system cannot file the the path specified.
X\windows\system32>
I am able to deploy to Dell workstation and laptops OK, it boots straight to Windows at this point.
Re: UEFI install getting stuck on HP workstation/laptops
Verfasst: 29 Mär 2018, 17:49
von ttblum
If I go into BIOS and select:
Main-->Apply Custom Defaults and Exit
it then boots into an HP logo screen with 'Configuring devices 46%' etc. and boots up normally.
Re: UEFI install getting stuck on HP workstation/laptops
Verfasst: 30 Mär 2018, 12:13
von m.radtke
Hi
does your machine have an NVME or M.2 drive?
If yes, ist the storage driver integrated into your WinPE?
This is the most common cause for this error
Cheers
Mathias
Re: UEFI install getting stuck on HP workstation/laptops
Verfasst: 30 Mär 2018, 15:28
von ttblum
Hello,
The HP EliteBook 840 G4, EliteDesk 800 G3 TWR, and EliteDesk 800 G3 SFF all have the same NVMe controller:
Samsung NVMe SSD Controller SM961/PM961 controller
We are using the WinPE provided by Opsi:
https://download.uib.de/abo/winpe_uefi
Re: UEFI install getting stuck on HP workstation/laptops
Verfasst: 03 Apr 2018, 11:36
von m.radtke
Hi
this WinPE does not have the specific NVME drivers.
You will have to integrate them yourself.
We will talk about an update of the WINPE in the next developer meeting. Afterwards we will most probably update it.
Cheers
Re: UEFI install getting stuck on HP workstation/laptops
Verfasst: 10 Mai 2018, 02:07
von SisterOfMercy
There could also be an issue with your bios and boot order. I have something like that.
The installation goes fine, but then it reboots into the same opsi temporary PE. If I then go into the bios and set the hard drive priority to windows boot manager it will work fine.
Windows 10 might fall back on the default NVMe driver, I'm not sure.
So the question is, does the first part of the windows setup work correctly?