locked
Hard Drive not Available during Windows 10 install RRS feed

  • Question

  • Hello,

    I work in an enterprise environment, and we have been trying to deploy Win 10. I have an HP Z440 (new, stock, no customizations) and when trying to load our ISO from USB, we receive the error that it cannot format the drive. The problem is, the only drive windows sees is the flash drive. It is trying to format the drive that it is pulling windows from.

    I opened up diskpart and the only thing I see is the flash drive. If I restart and let the computer do it's thing, it will open Windows 7 without issue. The primary drive is seen in BIOS. I disabled UEFI boot options, enabled and disable DriveSecurity, I enabled and disabled TPM and DEP. The USB has been formatted with NTFS and exFAT neither made a difference. I even attempted to put in a second hard drive from another Z440 to load windows to and THAT drive wasn't recognized. I'm not sure what SHB or HP has going on, but I am unable to load Windows 10 on it. Also, I have wiped a drive completely and put that in AND STILL it could not be recognized.

    Side note:  we also have HP EliteDesks, and we can load Windows 10 on those no problem...

    Add-in:  I cannot send logs because these machines are on a closed network and I will not be able to transfer them down for review.


    • Edited by v0iceless Friday, March 1, 2019 1:32 PM
    Friday, March 1, 2019 1:30 PM

Answers

  • SOLUTION:

    It turned out to be something simple. The DRIVERS. The reason that the image kept failing was because the drivers for the computer were not established in the correct location in MDT.

    Of course, something simple causing a big problem. I have successfully built the image, now I have a whole new array of issues to tend to to make this enterprise ready. Thank you for all of your help!

    • Marked as answer by v0iceless Thursday, March 28, 2019 1:29 PM
    Thursday, March 28, 2019 1:29 PM

All replies

  • hi there,

    1. You have an M.2 SSD PCIE 3x4 not properly configured in BIOS. Windows 10 can't see the drive. Since your running DOS this is unlikely happening.

     

    2. The existing HDD or SATA SSD is formatted as MBR but you are booting to the USB using UEFI GPT or vice versa. Windows installer may not see the drive. Either start with a wiped HDD or format the drive using GPT. Then boot the Win 10 install media using UEFI boot source so you can use GPT.

    please vote if that helps

    Friday, March 1, 2019 1:44 PM
  • So, I had already tried a completely wiped drive and still had no luck previously.

    I had some success in getting the hard drive visible, changed the BIOS setting from RAID to AHCI and enabled Secure Boot and disabled Legacy boot.

    But now, the image keeps failing when "failed to run action:  SHB - set DEP OptOut"

    I went into BIOS and disabled Data Execution Prevention and that made no difference.

    Saturday, March 2, 2019 12:39 PM
  • The full error that I receive is this:

    "Litetouch deployment failed, Return Code = -2147467259 0x80004005
    Failed to run the action:  SHB - Set DEP OptOut.
    Incorrect function. (Error: 00000001; Sourc: Windows)
    The Execution of the group (Postinstall) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)
    Failed to run the last action:  SHB - Set DEP OptOut. Execution of task sequence failed.
    Incorrect function. (Error: 00000001; Sourc: Windows)
    Task Sequence Engine Failed! Code: enExecutionFail
    Task Sequence execution failed with error code 80004005
    SetNamedSecurityInfo() failed.
    SetObjectOwner() failed. 0x80070005.
    RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,
    SMSTSEndProgram
    GetTsRegValue() is unsuccessful. 0x80070002.
    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005"

    I'm guessing that this is likely an error in the ISO image?

    Saturday, March 2, 2019 2:39 PM
  • Hi v0iceless,

     

    So the Hard Drive can’t be recognized issue was resolved and now it’s focusing on Litetouch deployment issue, right? Are you using MDT to deploy the image? We can check the bdd.log and/or smsts.log file for the details, to narrow down this issue and look for potential factors that may lead to this failure.  

     

    If you still need help, please upload relevant logs to OneDrive and share the link here, modify the link as txt format or the link may be blocked.

     

    If there is anything else we can do for you, please feel free to post in the forum. Thank you for choosing Microsoft.

     

    Best regards,

    Zoe Mo


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, March 4, 2019 9:15 AM
  • Yes, the hard drive issue has been resolved and now the issue does appear to be with the image. Yes I am using MDT.

    The unfortunate thing is that because I am building this on a closed network, I can't actually transport the logs to the low side (my security team's call not mine) unless I transpose them by hand.

    The issue seems to catch at the DEP OptOut portion of the postinstall, the command is as follows:

    bcdedit.exe /store %EFIDrive%\efi\microsoft\boot\bcd /set {default} nx OptOut 2

    I'm thinking that there is an error within this - perhaps the 2 value following "OptOut" or an error in the EFI drive...

    Monday, March 4, 2019 12:19 PM
  • Hi v0iceless,

     

    Why do you use the “/store %EFIDrive%\efi\microsoft\boot\bcd” section in the command? I guess the “\efi\microsoft\boot\bcd” should be the default path and without a drive letter assigned?

     

    I tried to test this same command in my test MDT environment, not sure what’s the configuration in your environment, since I haven’t do this in my TS previously, I’m not very familiar with this, below is what I added in the PostInstall Group:

     

    And finally got below issue seems similar with yours, and got the result “OptIn”:

     

     

     

    But when I tried with “bcdedit.exe /set {default} nx OptOut 2”, the deployment completed successfully with no error reported, and got the result “OptOut”:

     

     

    Is this the expected result you want? If so, just remove the specific path section and go ahead with the remaining ones.

     

    If there is anything else we can do for you, please feel free to post in the forum. Thank you for choosing Microsoft.

     

    Best regards,

    Zoe Mo


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, March 5, 2019 9:48 AM
  • Hi v0iceless,

     

    What is your current situation? Have you tried the suggestions provided above? Please remember to mark the replies as answers if they help, any other questions please feel free to post back. Thank you for choosing Microsoft.

     

    Best regards,
    Zoe Mo


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, March 7, 2019 10:21 AM
  • Hi v0iceless,

     

    We haven’t heard from you for a couple of days, have you solved the problem? Would you mind letting me know the update of the problem? Please remember to mark the replies as answers if they help, any other questions please feel free to post back. Thank you for choosing Microsoft.

     

    Best regards,
    Zoe Mo


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, March 11, 2019 8:16 AM
  • Hello,

    I apologize. I just had a baby so I was out for a little while and just returned to work today. I will be reviewing the advice given and responding later.

    Tuesday, March 12, 2019 3:38 PM
  • Hey Zoe,

    I will try this. In my TS build this is what my Postinstall Menu looks like (the + symbol indicates folders):

    + Postinstall
         - Copy Scripts
         - Configure
         - Inject Drivers
         - Add Windows Recovery (WinRE)
        + SHB - Set DEP OptOut
              - SHB - Get EFI Drive Location
              - SHB - Set DEP OptOut
        + SHB - HideOOBE
              - SHB - HideOOBE
         - Next Phase
         - Restart Computer

    Not sure if the SHB implementation changes requirements, I am looking at a build that was given to me, so I did not build this TS. So, I am not sure if the requirements are that it needs to manually point to the EFI Drive?

    I can attempt a change and see if that fixes the issue.

    Tuesday, March 12, 2019 4:21 PM
  • Also, under the Get EFI Drive, it has a powershell script with a single parameter:

    PowerShell Script:
    %SCRIPTROOT%\DeployScripts\DS_Get-EFI-Drive\DS_Get-EFI-Drive.ps1

    Parameter:
    -SCCM False

    Tuesday, March 12, 2019 4:25 PM
  • Hi v0iceless,

     

    Wow, congratulations and best wishes on your new baby!!!

     

    Don't worry, just take your time and try the test, hope we can have some lucky.

     

    Best regards,

    Zoe Mo


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, March 13, 2019 9:17 AM
  • Hi v0iceless,

    I am also working with SHB, and stuck exactly where you are (at least the configuration is consistent, if frustrating...)

    Are you on an isolated/stand-alone system or on an isolated network?

    I am having to lay it down on a stand-alone system and the complications that come from that.

    v/r

    JW

    PS - congrats on the baby!!  First one?

    Wednesday, March 13, 2019 2:47 PM
  • Hey JW,

    Yes we are preparing this image for both stand-alone systems as well as closed network systems (secure environment). So, it's been a headache.

    Also, it is my second child. Have a 2-yr old as well. So, it's been a headache. :P

    Wednesday, March 20, 2019 6:13 PM
  • Ok, so. I tested the image out and it failed again on the machine...

    I decided to run the test on a VM just to confirm that it was indeed the image that was failing, but it succeeded. I ran it twice, once from the computer and again from the USB drive, both times were successful. So, I have to wonder what the difference is that is causing it to fail on the workstation vs. succeeding on the VM.

    Could there be some BIOS settings causing the failure?

    Thanks!

    Justin

    Wednesday, March 20, 2019 9:38 PM
  • Hi v0iceless,

     

    Have you tested what I’ve mentioned above? I've succeeded with that on my lab machine.

     

    Best regards,

    Zoe Mo


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, March 21, 2019 10:41 AM
  • I have also had it work on a VM, but fail on my hardware (Dell 7710)


    I've been through most options in the BIOS (TPM 2.0 vs 1.2, Legacy vs UEFI, etc with no change).  

    Was off with other tasking, but will try the above suggestions asap.

    JW


    Thursday, March 21, 2019 12:52 PM
  • Hey Zoe,

    YEs, I did attempt the fix you gave with no success on the physical machine, however, in the VM it ran successfully.

    I was told that what's probably happening is that the driver pack from HP sees the Win PE drivers  and starts the boot process, but the hard disk drivers are sometimes  wrapped in the driver package and not clearly identified so they are not seen as storage drives.

    Thursday, March 21, 2019 6:35 PM
  • SOLUTION:

    It turned out to be something simple. The DRIVERS. The reason that the image kept failing was because the drivers for the computer were not established in the correct location in MDT.

    Of course, something simple causing a big problem. I have successfully built the image, now I have a whole new array of issues to tend to to make this enterprise ready. Thank you for all of your help!

    • Marked as answer by v0iceless Thursday, March 28, 2019 1:29 PM
    Thursday, March 28, 2019 1:29 PM