SCCM 2007 OSD Error - Windows 7 64bit - Lenovo M93p Tiny (10AB0015US)

Posted on 2014-04-15
Last Modified: 2015-06-19
Trying to deploy Windows 7 64bit to the Lenovo M93p Tiny (10AB-0015US) using SCCM 2007 OSD.

Error Message after OSD: (black screen, OS does NOT boot)

Windows failed to load ifm63x64.sys, Status: 0xc0000098


After creating a new/default WinPE boot image with no additional drivers, then injecting the correct Intel I217-LM Ethernet adapter driver (from Intel, not Lenovo), the OSD would install the Win7x64 custom OS image, and does boot, but the network driver is still not installed (so the OSD task sequence fails because the computer is unable to re-connect to sccm and complete the additional steps).

I have tried to install the network driver with multiple methods during OSD with no success. Driver packages, imported driver tasks. They always end up with the error code mentioned above after the computer reboots. (The OS is installed while running on WinPE, but no further progress after reboot)

This new device does utilize UEFI (secure boot), and seems to be blocking driver installation. I believe i have disabled secure boot in BIOS, and enabled compatibility mode. Not sure if there is something I am missing?

Any help or insight is appreciated.

Thank you,
Question by:Smizzong
  • 4
  • 4
LVL 31

Expert Comment

ID: 40003185
Do you have the Network Driver for the correct OS which you install?
Windows PE OS is not equal installed Windows in all cases

Author Comment

ID: 40003977
I created a new "default" WinPEx86 boot image for osd testing with this device, the properties show OS version 6.1 (Win7 correct?). The Intel I217-LM network driver that has been added to the image was specific for Win7x86.

The driver packages i am attempting to use include the Intel I217-LM network driver specific to Win7x64.

winpe props
LVL 31

Expert Comment

ID: 40005837
Ok PE works as it's getting the Image and applies it to the harddisk. The Problem is the missing Network Driver for the Windows 7 x64 Installation.
- Is it missing? Try a ipconfig in the F8 command prompt when Windows 7 has started.
- Is the Driver package applied? Check out the smsts.log if the step is executed.
- Install Windows 7 manually and try to load that Network driver

Author Comment

ID: 40007459
Thank you for your continued assistance merowinger. I agree that WinPE and the OS image install to hdd process appears to be working properly.

Quick rundown of my current setup for OSD Task Sequence process as I understand it:

-test computer imported to SCCM, added to OSD collection
(osd task seq advertisement in place)
-boot computer via PXE, connection established
-boot image downloads via network connection
-computer boots up, running WinPE(x86) at this point
-select/begin osd task sequence
-custom os image downloaded and installed
-install driver package (network driver only)
-computer restart
-computer boots to newly installed Win7x64 OS
-windows fails to boot - error message (ifm63x64 missing or corrupt, status 0xc0000098)

I have tried multiple driver packages (Lenovo/Intel), but if i leave the network driver package out completely, the installed Win7x64 OS does boot after restart without error, but there is no network driver installed. This will then cause the continuation of the task sequence to fail because the computer was unable to re-establish a network connection with SCCM.

No problem with "manual" install of the Intel Ethernet driver. Also, I would think that if the OS image is installing to the hdd, that there must not be any additional "storage drivers" required in the WinPE boot image.

Wondering if the cause of this problem could be due to the UEFI secure boot BIOS (settings), or if it could be a WinPE incompatibility with the driver?
Top 6 Sources for Identifying Threat Actor TTPs

Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

LVL 31

Expert Comment

ID: 40008335
After applying the Windows Image the Clients restarts and boots from it. The Driver packages are then applied in your deployed Windows, so i don't think this is caused from WinPE.
Are there other drivers in the Package? Like a SCSI Driver? If yes, remove it,update deployment package and try again.

Author Comment

ID: 40015948
merowinger, i am planning to scrap the boot images (x86 & x64) and the drivers/packages that have been imported for this test to get a fresh start.

More research and digging deeper into the driver packages (from Lenovo and Intel) appears to agree with your suggestion to look for a SCSI or other incompatible driver. The error message points out "IFM63x64.SYS" (or "IFP63x64.sys") file is missing, and this file is found in the driver packages from both Lenovo and Intel. (FCOE/SCSI and PROSET) I have also reached out to Intel and Lenovo for assistance, but will have to wait and see if they offer further assistance.

I hope that you can help to enlighten me in regards to the SCCM OSD and driver installation process. I do believe and agree with you that some problem drivers (eg. bluetooth, video?) may require special handling/packages for automated installation later on in the OSD process (after the image has been installed), but as for the network (Ethernet) driver - it must be installed during the initial WinPE stage.

During WinPE, if the proper network driver has been included in the boot image, the computer will be able to pull an ip address and communicate over the network with the SCCM PXE distribution point. The driver for the permanent OS install must also be installed during this stage, or else after the computer restarts then boots to the permanent OS, it will not be able to re-connect with SCCM over the network and continue the Task Sequence (install additional apps, ms updates, etc)

Please explain/correct my thinking on this?

Thank you,
LVL 31

Accepted Solution

merowinger earned 500 total points
ID: 40016724
I'm 99% sure, that you do not Need that Driver / file which is described in the error message.
The problem occurs after applying Windows 7 to the disk so WinPE isn't the Problem.
I think there was a Driver injected which is not compatible with your HDD configuration.
Just search for *IFM63x64* in your Driver package or Driver sources on the disk and then remove alll the independed files like IFM63x64.SYS, IFM63x64.INF, etc.

To your question:
Either the permanent Windows 7 has already included a matching Driver for your Hardware or you have to include it with a Driver package. This happens after the Windows 7 Image has been applied. On a later step Windows 7 installs and configures devices and search also in the packages for matching Drivers.

But as i said, i don't think you Problem has to do with a missing Network Driver.

Expert Comment

by:Justin Hyde
ID: 40218084
Try Removing all Network drivers from the Driver Package except for the Known good Network Driver.  I had the same issue with the Lenovo M83 and that was the ONLY way I could get around it.

Author Closing Comment

ID: 40839103
Apologies for leaving this hanging for so long. (over a year! - terrible)

Removing the offending driver files from the driver package did resolve the issue.

"Just search for *IFM63x64* in your Driver package or Driver sources on the disk and then remove alll the independed files like IFM63x64.SYS, IFM63x64.INF, etc."

Windows 7 x64 did boot successfully and continue the image process after the files were removed and the package was updated on the DPs.

The SCSI and FCoE files seem to be intended for Server 2012.

Thank you very much for your help,

Featured Post

Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

Join & Write a Comment

Suggested Solutions

You have seen this as an option on your internet browser before or it may be completely new to you.  But what does this mean and why would I use this?
In this guide, I outline 7 key steps to help technology professionals grow their careers. Whether you have been working in technology for 10 years or for 10 days, follow these steps to help you achieve your career goals and pursue your passions.
Windows 8 comes with a dramatically different user interface known as Metro. Notably missing from the new interface is a Start button and Start Menu. Many users do not like it, much preferring the interface of earlier versions — Windows 7, Windows X…
The viewer will learn how to successfully download and install the SARDU utility on Windows 8, without downloading adware.

708 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now