Please bear with me as I am new in a PC Engineering/OS Delivery role. My company is currently demoing one of HP’s AI Laptops and I’ve had a difficult time using BigFix OSD to install our image on the machine. I can successfully PXE boot to the server and select the profile I want to deploy.
After selecting the profile to run, I am not met with any errors such as missing drivers preventing the image from installing, it will run through all the steps with no stops (Disc accessibility, Disk Format, Preparing deployment binaries, etc).
When the computer reboots to exit WinPE, that is where I am running into issues.
It will start to boot and show “Starting services” and “Getting device ready”. After that it will try to boot a few times and eventually fail with an Automatic Repair screen saying the PC did not start correctly. I am never able to reach Windows and finish out the deployment.
The first time I received this machine, I ran into the same errors but after disabling secure boot I was able to get into Windows and use it. I tested the computer out for a couple weeks, but then needed to reimage so I could send it to someone else for testing in another state. I have been unable to get the image loaded properly ever since then.
I can download the ISO from Microsoft and install Windows that way, but due to the complexity of our environment I need to get this consistently working in our BigFix server.
I’ve tried adding the Management Extender so I can import drivers and bind to the model as well to potentially rule out driver issues but still no luck. I want to say the issue might be with how I have the disk formatting set up on the image profile, but it has worked with no issue on every other model in our environment (over 200).
Details:
OS: Windows 11 Pro 23H2
Server version: 7.1.120.31128
Relay version: 10.0.1 (We will be upgrading these soon)
Computer model: HP ZBook Ultra G1a 14 inch mobile workstation PC
Please let me know what I can check for to help resolve this issue.
Thanks!
So it looks like your issue is in the Windows Setup procedure - I suggest you to open HCL Support Case
On the Repair Screen, you can access the Installation Drive and look for the Log Files - “Files for problem determination during Windows setup” - Log and trace files
I will have to get back to you on the Windows setup error logs, but yes I downloaded the right drivers from HPs driver matrix for the specific model.
It looks like sp158580 is for the ZBook G1i, this is a G1a. I grabbed sp157637 from HPs Driverpack Matrix x64 (I can’t post links yet), although this may not be the most up to date pack.
We’re having the same issues with our G1a, even using the drivers injected into our image still seems to boot into automatic repair. We have managed to narrow it down to the Integrated Camera, if we disable it via BIOS the machine will boot into Windows. Please could you try this on yours and let me know if you have the same result?
Interesting. Just tried this today on my demo unit and sure enough that worked. Ran it on a fresh image, received the automatic repair screen. Restarted and went to BIOS to disable the camera, saved changes and that worked.
Unfortunately even after HPIA and all driver updates, re-enabling the camera will still throw me into a repair screen (0xc0000001). It has to be completely disabled in BIOS for Windows to work.
I spoke with HP this morning and they asked for ImageDiag logs which I sent over. Waiting to hear back and see if it’s something that needs to be resolved on their end, however I may still open a case with HCL since you’re also seeing it.
What version of Windows are you using? Wondering if it may be tied to that.
We have been trying on 23H2 due to our company image has not moved to 24H2 just yet. The base Windows 23H2 build also is resulting in the same ‘Automatic Repair’ loop.
We currently have the G1a running on a Standard 24H2 build with a working camera! It seems the camera might be somehow linked with the AMD graphics drivers for certain features / effects. I have exported the current drivers running on 24H2 and might try to build using our 23H2 image with these drivers injected. I can upload these drivers if you wanted to test your end as well?
That’s good to know it is coming from 23H2. I’ve seen really random things not work on HP equipment with that specific Windows 11 version. We are in the same boat, can’t upgrade to 24H2 yet since our server is a bit behind.
I’ll try putting a 24H2 build to see if it also works for me with the camera enabled. I have a conversation already going with HP so I’ll let them know about this find on the OS version. They have yet to review my ImageDiag logs.
We have a driver harvest program so I can use that if need be but I appreciate the offer! Let me know if you find anything else.
@jrs1 I received an update this morning from HP. They tested with a plain 23H2 ISO from Microsoft and found the same issue. This is what they came back with as a workaround - I did test this just now and confirmed it did work for me.
"
Microsoft introduced a newer setting called Enhanced Security Sign-On. This setting was introduced within the HP BIOS in G11 and newer systems. It plays well with Win11 24H2, however doesn’t play well with 22H2 or 23H2. You are currently bypassing the Enhanced Security Sign-On setting by disabling the integrated camera.
The workaround would be to enable the integrated camera and disable Enhanced Security Sign-On inside the BIOS to allow the camera to work and allow the system to boot into Windows without throwing errors. Once you are ready to upgrade to Win11 24H2, this will no longer be an issue.
The Enhanced Sign-On Security Setting is a newer setting within the HP BIOS (G11 systems and newer) and it replaced “Enhanced Hello Sign-in” which was originally disabled by default in G9 devices and earlier. It is a setting that is required to be present for a PC to be considered a Secure Core PC but just needs to be capable of Enhanced Sign-On Security and not enabled. So, this setting is okay to disable, and it won’t affect the system being considered a Secure Core PC.
"
There is also an article posted by Microsoft (I can’t post links): Google Windows Hello Enhanced Sign-in Security
I found this in BIOS F10 > Advanced > System Options.
Hope this helps you. Yet again sounds like just another weird thing with HP and 23H2 but it looks like even pulling over drivers won’t work.