Guidelines
Are you having HotKey issues? Click here for tips and tricks.
Check out our WINDOWS 11 Support Center info about: OPTIMIZATION, KNOWN ISSUES, FAQs, VIDEOS AND MORE.
HP Recommended
Z Book Studio G4 Workstation
Microsoft Windows 10 (64-bit)

Hello:

I have some brand new Z Book Studio G4 Workstation notebooks.  From the state I received the units, I wanted to deploy the company image, instead of using what came loaded by the factory.

 

Deploying the WIM failed.  It's a Windows 10 WIM.  The WIM had the HP drivers added to it... if there was a problem with the drivers, I would expect a BSOD.  But that is NOT the problem as no BSOD is received.  

Here are the steps I took:

1. Press F9 to access boot menu

2. Connect USB DVD drive with WinPE disc inserted

3. Boot to WinPE (created with the latest version of the AIK/ADK or whatever MS is calling it these days).

4. Run the following diskpart commands:  select disk 0, clean, create partition primary, format fs=ntfs quick, assign letter=c:, and active

5. Run dism /apply-image /imagefile:e:\myWIM.wim /index:1 /applydir:c:\ 

6. Run bcdboot c:\windows /s c:

7. Exit WinPE and reboot.

On the reboot I get an error message stating no operating system is found.  In my experience, generally that arises from not running the bcdboot command.  But in this case I DID RUN IT!
 

Is there anything special about this Z Book -- BIOS settings, partitioning, etc., which is preventing this from booting for me?  I haven't had such problems on other vendor's notebooks -- just this HP Z Book.

Suggestions are greatly appreciated -- I'll name my firstborn after you if this gets working! 🙂
 
Thanks!
 
 

1 ACCEPTED SOLUTION

Accepted Solutions
HP Recommended

It's working now but make no mistake, I don't like the steps it took to get here... seems like a but of a clusterfudge to me!

 

I don't like it because with other Win 10 hosts I have, the drive is only a single partition. On the HP ZBooks, it looks like you need to have a recovery and reserved partition too.  It would be nice if someone could tell me why HP is different from the rest of the world.

 

So, here's the script I use with diskpart /s at the beginning of the deployment process:

 

select disk 0
clean
convert gpt
REM  1. System partition
create partition efi size=100
format quick fs=fat32 
REM  2. Microsoft Reserved (MSR) partition
create partition msr size=16
REM  3. Windows partition
create partition primary 
shrink minimum=500
format quick fs=ntfs 
assign letter="C"
REM  4.  Recovery tools partition
create partition primary
format quick fs=ntfs label="Recovery tools"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
list volume
exit

Just like last time, after laying the WIM down per the OP, I got a no OS found error.  Just like last time, I ran these commands:

 

 

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

 

 

HOWEVER, bootrec /rebuildbcd worked this time!

 

After answering Y to

"Successfully scanned Windows Installations Total identified Windows Installations: 1 Add installation to boot list? Yes/No/All:"

the command worked!

 

After rebooting, I got a no OS found error again!

 

Grr.

 

I had to boot into Win 10 installation media (which HP doesn't give you) -> click on Repair your computer -> Troubleshoot -> Startup Repair

 

I'm happy I can delpoy the company WIM now. I'm pretty irritated at why did Startup Repair work from the GUI but bootrec /rebuildbcd from the terminal didn't???

 

It would be nice to know that last question so I'm not booting to an install disk with every new computer just to click on Startup Repair.

 

I hope this helps anyone reading it. Feel free to comment further if you have better information! Thanks!

View solution in original post

1 REPLY 1
HP Recommended

It's working now but make no mistake, I don't like the steps it took to get here... seems like a but of a clusterfudge to me!

 

I don't like it because with other Win 10 hosts I have, the drive is only a single partition. On the HP ZBooks, it looks like you need to have a recovery and reserved partition too.  It would be nice if someone could tell me why HP is different from the rest of the world.

 

So, here's the script I use with diskpart /s at the beginning of the deployment process:

 

select disk 0
clean
convert gpt
REM  1. System partition
create partition efi size=100
format quick fs=fat32 
REM  2. Microsoft Reserved (MSR) partition
create partition msr size=16
REM  3. Windows partition
create partition primary 
shrink minimum=500
format quick fs=ntfs 
assign letter="C"
REM  4.  Recovery tools partition
create partition primary
format quick fs=ntfs label="Recovery tools"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
list volume
exit

Just like last time, after laying the WIM down per the OP, I got a no OS found error.  Just like last time, I ran these commands:

 

 

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

 

 

HOWEVER, bootrec /rebuildbcd worked this time!

 

After answering Y to

"Successfully scanned Windows Installations Total identified Windows Installations: 1 Add installation to boot list? Yes/No/All:"

the command worked!

 

After rebooting, I got a no OS found error again!

 

Grr.

 

I had to boot into Win 10 installation media (which HP doesn't give you) -> click on Repair your computer -> Troubleshoot -> Startup Repair

 

I'm happy I can delpoy the company WIM now. I'm pretty irritated at why did Startup Repair work from the GUI but bootrec /rebuildbcd from the terminal didn't???

 

It would be nice to know that last question so I'm not booting to an install disk with every new computer just to click on Startup Repair.

 

I hope this helps anyone reading it. Feel free to comment further if you have better information! Thanks!

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.