OSD Booting hung up on Client showing Windows Logo

Hi, I’ve followed the IBM Knowledge center documentation version 9.2 and implemented our environment for OS Deployment on Windows computers. I’ve imported Windows 8.1 64-bit image into Image Library instead of capturing from Capture Images Dashboard and deploy it to a Windows 7 64-bit client runnning on Innotek VirtualBox 1.2. But the Windows 7 client hung up showing the Windows 8 logo.

Is it something with the drivers as I’ve not imported any drivers before deploying. When I checked the drivers from Check Driver tab of Driver Library Dashboard, below driver is missing.

Missing Driver : Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (8086.2668.8384.7680)

Are drivers really mandatory to import before deploying an image to any computer?

Please provide any workaround for above problem.

Below is the screenshot of the Missing driver.

@jgstew, @JasonWalker, @AlanM… Do you guys have any solution to provide? Is it something to do with the Drivers?

As a matter of best practice, you should always resolve any driver issues before trying to capture/deploy. You are missing an audio driver so that should not cause the issue you are reporting.

Are you performing bare metal imaging or an in-place re-image? If the latter, then I think your issue is that you cannot go from Windows 8.1 back to 7 using the in-place re-image technique. This is not a matter of having downgrade rights - it is technical matter. I think we have protections in place to prevent doing this, but not sure off the top of my head. Anyway, to downgrade from 8.1 to 7 you would want to take the bare metal approach which would wipe the drive and then lay down a fresh Windows 7 image. Give us a little more detail about what you are doing and we can help more.

Reference: https://www.dell.com/support/article/us/en/04/sln294589/an-understanding-of-both-your-microsoft-windows-downgrade-rights-and-downgrading-from-windows-8-81-and-10?lang=en

This is an re-image which I’m trying on a windows 7 client. Here I’m trying to deploy Windows 8.1 on a Windows 7 client and If I’m not wrong then, this is possible. After deploying the image to win7 client, the client stuck showing Win8.1 logo. unable to find the root cause of this problem. Is there any other issues other than drivers?

Sure, there can be lots of issues setting up Windows 8.1, no matter the deployment technology.

Troubleshooting steps would begin with the usual Windows Install troubleshooting. Try booting the system from a Windows PE boot media (such as a normal Windows 7/8/10 setup disk or flash drive), ooen a command prompt, navigate to C:\Windows\Panther (noting the WinPE may mount it on a drive letter other than C:), and check the setupact.log, setuperr.log, and setupapi.log files for any errors. There may be several instances of these logs in different subdirectories such as Unattend or UnattendGC, so check each subdirectory and note the file modification dates for each of the log files to determine which ones to examine.

Hi @JasonWalker, I tried to capture Windows 8.1 image from a client using Capture Image Dashboard, the capture action completed successfully but didn’t capture it to the specified network path, just logs have captured. I have checked the logs and found below errors.

  1. In LTISysPrep.log and BDD.log,

    i. Expected image state is IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE, actual image state is IMAGE_STATE_UNDEPLOYABLE, sysprep did not succeed.

  2. In LiteTouch.log and BDD.log,

    i. Litetouch deployment failed, Return Code = -2147467259 0x80004005.

  3. In smsts.log,

    i. Could not find CCM install folder. Don’t use ccmerrors.dll.
    ii. Failed to run the action: Execute Sysprep. Unknown error (Error: 00001830; Source: Unknown)
    iii. Failed to run the last action: Execute Sysprep. Execution of task sequence failed. Unknown error (Error: 00001830; Source: Unknown)
    iv. Task Sequence Engine failed! Code: enExecutionFail
    v. Task sequence execution failed with error code 80004005

  4. In setuperr.log and setupact.log under sysprep/panther directory,

    i. [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn’t update the recorded state, dwRet = 0x1f
    ii. [0x0f00ae] SYSPRP WinMain:Hit failure while processing sysprep cleanup external providers; hr = 0x8007001f

Any idea, what is causing above issues?

I’m afraid not, you’d need to open a PMR or check support resources at Microsoft.

Okay, Let me google it for some more time, if I can find something which is helpful.

I guess it was the Sysprep rearm count which was causing above issue. I have skipped the rearm count and the Sysprep completed successfully and system rebooted. But while rebooting it got stuck showing the Windows logo. Neither it created any logs nor captured the image to the specified network share. I’m unable to determine what actually causing the issue.

@jgstew, @AlanM, @Rafael… Do you guys know what actually causing the issue and where should I look for it?

Hi @JasonWalker, can you check the steps I’ve performed are correct or am I missing something?

  1. Installed MDT Bundle Creator.
  2. Created MDT Bundle and OS Resource and uploaded it.
  3. Captured Image from a reference computer.

While capturing the PE is failing I guess. I have skipped the driver importing as I’m unable to find the exact driver for the specified Model.

Correct me If I’m missing something.

Steps look ok to me. What I usually find is that the Microsoft part of the capture process is buggy. I had some problems running a capture after upgrading 1607 to 1709, and it turns out I had to reset some Windows Store applications before running sysprep.

All of the errors you posted are Microsoft MDT or Sysprep errors. You could try opening a ticket with Microsoft, or a PMR with BigFix.

Do we need to have deployment media in place?

I don’t know how to make this more clear. There are a million things that can go wrong with sysyprep. You have posted about three lines from a log, that sum up to “something went wrong”.

Here are a few things that can go wrong in sysprep. Try working through these, or google some more with your error codes

https://support.microsoft.com/en-sg/help/2769827/sysprep-fails-after-you-remove-or-update-windows-store-apps-that-inclu

https://www.google.com/url?sa=t&source=web&rct=j&url=https://redmondmag.com/articles/2016/03/04/sysprep-work-with-windows-10-2.aspx%3Fm%3D1&ved=2ahUKEwjAxq-0ne_dAhUNPK0KHQ11DCkQFjABegQICBAB&usg=AOvVaw32t3zwrhZN1sgRqbZX510B

https://www.google.com/url?sa=t&source=web&rct=j&url=https://windowsreport.com/windows-10-sysprep/amp/&ved=2ahUKEwjAxq-0ne_dAhUNPK0KHQ11DCkQFjACegQIBxAB&usg=AOvVaw1NkXFrSfv-vCB9k3svNUiF&ampcf=1

https://www.google.com/url?sa=t&source=web&rct=j&url=https://www.linkedin.com/pulse/how-prepare-windows-10-sysprep-benjamin-blacklock&ved=2ahUKEwjAxq-0ne_dAhUNPK0KHQ11DCkQFjADegQIABAB&usg=AOvVaw1X4g4YUk40mYX95ny19Psq

Let me go through these links and let’s see if they can help to resolve this issue. Thanks