Friday, July 26, 2013

Windows failed to load ifm63x64.sys Status: 0xc0000098


When I was building HP DL380 G5 server with Windows Server 2008 R2 using SCCM 2007 OSD task sequence, I have received the below error
Error:
Windows failed to load ifm63x64.sys Status: 0xc0000098
Info: Windows failed to load because a requested file is missing or corrupt
I have received this error after adding new drivers for IntelI350 network card drivers. So obviously some of the drivers for the NIC have caused the issue. So I looked into the drivers package for HP DL380 G5 server and noticed there was a driver for SCSI Adapter. 
When I looked into the properties of the driver file, it says Intel Enternet FCo E SAN Stack for Windows.
So I decided to remove that driver from the package, updated the DP’s then tested.
The error msg gone and built the server without any issue.
Posted by at

19 comments:

  1. AnonymousAugust 6, 2013 at 8:26 PM

    I am having similar issue with of my server build and your solution worked for me.
    thanks buddy :)

    ReplyDelete
  2. AnonymousOctober 5, 2013 at 2:47 AM

    Thanks..this helped me too!

    ReplyDelete
  3. AnonymousJanuary 10, 2014 at 6:41 AM

    good one. I ran into similar issue

    ReplyDelete
  4. UnknownJanuary 21, 2014 at 6:24 PM

    Thanks. Worked for me to on a Toshiba Portege Z30A

    ReplyDelete
  5. AnonymousFebruary 8, 2014 at 7:08 AM

    I had the same problem using MDT 2012 building a Lenovo T440 using a USB boot disk.
    Thanks for the fix. You saved me a ton of time!

    ReplyDelete
    Replies
    1. UnknownApril 17, 2014 at 2:30 AM

      Hello, did you have to create a new driver package or did you simply 'disable' thme, its not working for T420 and T430 models.

      Delete
  6. AnonymousMarch 1, 2014 at 7:09 AM

    Thanks so much this saved me a great deal of time.

    ReplyDelete
  7. lexiosMarch 27, 2014 at 8:32 PM

    Although I removed the driver the problem persists.

    ReplyDelete
  8. Venu SingireddyMarch 28, 2014 at 2:32 PM

    Lexios, after removing the drivers from the package, dont forget to update the package in all the DP's.
    Have you updated the package on all the DPs?

    ReplyDelete
  9. AnonymousMay 2, 2014 at 6:13 AM

    This worked very well. Cheers

    ReplyDelete
  10. AnonymousJuly 17, 2014 at 10:44 PM

    Thank you.
    I needed an installation medium with integraded drivers for a panasonic toughbook cf-c2 mk2. i integraded all the drivers i had, including the one that cause this problem. after removing everything from the installation dvd that was related to scsi and network stuff (just to be sure) it worked.

    ReplyDelete
  11. AnonymousJuly 29, 2014 at 4:34 PM

    Guys!!!

    Look out for a driver called "Intel(R) Ethernet LLDP Protocol Driver" as it refers to the ifm63x64.sys file. Update your driver packages to your DP's and hopefully you should be good to go (about to test it now).

    ReplyDelete
  12. AnonymousAugust 23, 2014 at 4:11 AM

    Worked on a Dell E6440 laptop. Thanks a bunch!

    ReplyDelete
  13. Lou GouberApril 23, 2015 at 4:45 PM

    Thanks buddy. This pointed me in the right direction. After turning on the Show Inf heading in the driver view, I finally managed to get rid of this error. Lenovo T420s

    ReplyDelete
  14. AnonymousMay 7, 2015 at 4:33 PM

    I got the same error
    ifm63x64.sys was removed from my driverpackage and DP updated.
    Same error occours. This is a Lenovo T450s.
    I'm running out of options...

    ReplyDelete
    Replies
    1. AnonymousMay 19, 2015 at 4:55 AM

      Same situation here with a T450. Any chance you found a fix?

      Cheers

      Delete
    2. AnonymousMay 19, 2015 at 4:58 AM

      Same situation here with a T450. Any chance you found a fix?

      Cheers

      Delete
  15. SenaJanuary 27, 2016 at 12:45 PM

    I updated my MDT version from 6.0.x (MDT 2012) to 6.3.x (MDT 2013) updated my DS/regenerated my Lite Touch Windows PE image and imported same to WDS, (You will realise the OS version for the boot image will be 10.0.xxx instead of 6.1.xxx) and this worked perfectly even without deleting any driver.

    ReplyDelete
  16. UnknownFebruary 16, 2016 at 10:30 PM

    cheers for the info :)

    ReplyDelete

Subscribe to: Post Comments (Atom)