none
Driver - Class Installer - Error 1392: The file or directory is corrupted and unreadable. RRS feed

  • Question

  • I am in the process of modifying an existing device driver. After making some organizational changes to the project build structure I was able to successfully compile and install the driver on a clean Windows 7 64 bit machine. I then proceeded to plug the device into the machine via USB. The Plug and Play manager kicked off and everything appeared to be going fine, but ultimately the device was NOT successfully installed. The only clue as to what might be happening was listed in thesetupapi.dev.log as follows:

         ndv: 12:37:20.307      Installing device...
         dvi: 12:37:20.307      {DIF_INSTALLDEVICE}
         dvi: 12:37:20.307           Class installer: Enter
         inf: 12:37:20.307                Opened INF: 'C:\Windows\System32\DriverStore\FileRepository\some.inf_amd64_neutral_9ab34af1e046559f\some.inf' ([strings])
         inf: 12:37:20.307                Opened INF: 'C:\Windows\System32\DriverStore\FileRepository\some.inf_amd64_neutral_9ab34af1e046559f\some.inf' ([strings])
    !!!  dvi: 12:37:20.370           Class installer: failed(0x00000570)!
    !!!  dvi: 12:37:20.370           Error 1392: The file or directory is corrupted and unreadable.
         dvi: 12:37:20.370      {DIF_INSTALLDEVICE - exit(0x00000570)}
    !!!  ndv: 12:37:20.370      Error(00000570) installing device!
         ndv: 12:37:20.370      Device install status=0x00000570
         ndv: 12:37:20.370      Performing device install final cleanup...
    !    ndv: 12:37:20.370      Queueing up error report since device installation failed...

    I have verified that the disk and files on the machine are NOT corrupt. I have spent hours searching for some clue as to what may be happening, but there does not appear to be a clear path forward in terms of investigation. How do I determine what is going on during the device installation process?

    Wednesday, November 4, 2015 6:22 PM

All replies

  • make sure the 64 bit version of the coinstaller DLL is in the driver package. Also, make sure all of the dependencies for the coinstaller are present, write a simple console application that calls LoadLibrary on the coinstaller DLL to make sure loads

    d -- This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, November 4, 2015 8:21 PM
  • @Doran Holan,

    Thanks.  I will give this a go and let you know how I make out.

    Thursday, November 5, 2015 3:38 PM