How to Make Windows 7 Drivers Work on Windows 8 (INF Modding)

Windows 8 has been officially launched and the most common problems that are encountered when you use a new OS are related to driver compatibility issues. Some drivers do not support Windows 8 and when you force to install the driver, Windows 8 will reject it. Different with previous versions of windows, the regulation of the drivers on Windows 8 is very tight, and you need more effort when you install a driver that does not officially support Windows 8. This time I will share my experience installing driver from a Prolink PCM100 USB Modem on Windows 8.

A few weeks ago I tried to install a driver from Prolink PCM100 on Windows 8 RTM x64. I used the “compatibility mode” on the setup.exe file and install it normally. After that I checked in the Device Manager and found the device status was “unknown device” then I tried to update the driver manually (still in the device manager) using the “.inf” file and the Windows 8 RTM accepted the “.inf” file, though the file is designed only for Windows 7.

Yesterday I installed the latest version of Windows 8, the Windows 8 Pro x64. Then I tried to install driver from USB Modem PCM100 on that Windows by using the “compatibility mode” on the setup.exe file and the installation seemed to run normally, but at the end of the installation process it apparently came out an error message “Fail to install modem”.

I tried to check the device manager, there was a device with status “unknown device” and then I tried to update the driver manually using the file “.inf” as I did before, and the error message “Driver is not intended for this platform” appeared.

driver is not intended for this platform - screenshot

Then I tried to edit the “.inf” file using notepad. The entire “NTia64” was replaced by “NTia64.6.2” and all “NTamd64” was replaced by “NTamd64.6.2” then I tried to update the driver with the “.inf” file which has been modified and the error message “The hash for the file is not present in the specific catalog file. The file is likely corrupt or the victim of tampering.” appears.

[Version]
Signature="$WINDOWS NT$"
Class=Modem
Provider=%ZTEMT%
CLASSGUID={4D36E96D-E325-11CE-BFC1-08002BE10318}
DriverVer=05/13/2010,2.0.5.6
Catalogfile = ztemtusbser.cat

[Manufacturer]
%ZTEMT%=Models, NTia64, NTamd64

[ControlFlags]
ExcludeFromSelect = *

[SourceDisksNames]
1000 = %ZTEMTSrcDisk%,"",,

[SourceDisksFiles]
CT_U_USBSER.sys = 1000

[Models]
%ZTEFFFF% = ModemRevA, USB\VID_19D2&PID_FFFF&MI_00
%ZTEFFFE% = Modem2, USB\VID_19D2&PID_FFFE&MI_00
%ZTEFFFD% = Modem2, USB\VID_19D2&PID_FFFD&MI_00
%ZTEFFFC% = Modem2, USB\VID_19D2&PID_FFFC&MI_00

%ZTEFFFB% = Modem2, USB\VID_19D2&PID_FFFB&MI_00
%ZTEFFFA% = Modem2, USB\VID_19D2&PID_FFFA&MI_00
%ZTEFFF9% = Modem2, USB\VID_19D2&PID_FFF9&MI_00
%ZTEFFF8% = Modem2, USB\VID_19D2&PID_FFF8&MI_00
%ZTEFFF7% = ModemRevA, USB\VID_19D2&PID_FFF7&MI_00
%ZTEFFF6% = ModemRevA, USB\VID_19D2&PID_FFF6&MI_01 ; MI_00 is Used for USB Disk
%ZTEFFF1% = ModemRevA, USB\VID_19D2&PID_FFF1&MI_00
%ZTEFFF0% = ModemRevA, USB\VID_19D2&PID_FFF0&MI_04
%ZTEFFEF% = Modem2, USB\VID_19D2&PID_FFEF&MI_00
%ZTEFFEE% = Modem2, USB\VID_19D2&PID_FFEE&MI_00
%ZTEFFEC% = Modem2, USB\VID_19D2&PID_FFEC&MI_03
%ZTEFFEA% = Modem2, USB\VID_19D2&PID_FFEA&MI_01
%ZTEFFE9% = Modem2, USB\VID_19D2&PID_FFE9&MI_00
%ZTEFFE8% = Modem2, USB\VID_19D2&PID_FFE8&MI_00
%ZTEFFE7% = Modem2, USB\VID_19D2&PID_FFE7&MI_00
%ZTEFFE4% = Modem2, USB\VID_19D2&PID_FFE4&MI_00

[Models.NTamd64]
%ZTEFFFF% = ModemRevA, USB\VID_19D2&PID_FFFF&MI_00
%ZTEFFFE% = Modem2, USB\VID_19D2&PID_FFFE&MI_00
%ZTEFFFD% = Modem2, USB\VID_19D2&PID_FFFD&MI_00
%ZTEFFFC% = Modem2, USB\VID_19D2&PID_FFFC&MI_00

%ZTEFFFB% = Modem2, USB\VID_19D2&PID_FFFB&MI_00
%ZTEFFFA% = Modem2, USB\VID_19D2&PID_FFFA&MI_00
%ZTEFFF9% = Modem2, USB\VID_19D2&PID_FFF9&MI_00
%ZTEFFF8% = Modem2, USB\VID_19D2&PID_FFF8&MI_00
%ZTEFFF7% = ModemRevA, USB\VID_19D2&PID_FFF7&MI_00
%ZTEFFF6% = ModemRevA, USB\VID_19D2&PID_FFF6&MI_01 ; MI_00 is Used for USB Disk
%ZTEFFF1% = ModemRevA, USB\VID_19D2&PID_FFF1&MI_00
%ZTEFFF0% = ModemRevA, USB\VID_19D2&PID_FFF0&MI_04
%ZTEFFEF% = Modem2, USB\VID_19D2&PID_FFEF&MI_00
%ZTEFFEE% = Modem2, USB\VID_19D2&PID_FFEE&MI_00
%ZTEFFEC% = Modem2, USB\VID_19D2&PID_FFEC&MI_03
%ZTEFFEA% = Modem2, USB\VID_19D2&PID_FFEA&MI_01
%ZTEFFE9% = Modem2, USB\VID_19D2&PID_FFE9&MI_00
%ZTEFFE8% = Modem2, USB\VID_19D2&PID_FFE8&MI_00
%ZTEFFE7% = Modem2, USB\VID_19D2&PID_FFE7&MI_00
%ZTEFFE4% = Modem2, USB\VID_19D2&PID_FFE4&MI_00

[Models.NTia64]
%ZTEFFFF% = ModemRevA, USB\VID_19D2&PID_FFFF&MI_00
%ZTEFFFE% = Modem2, USB\VID_19D2&PID_FFFE&MI_00
%ZTEFFFD% = Modem2, USB\VID_19D2&PID_FFFD&MI_00
%ZTEFFFC% = Modem2, USB\VID_19D2&PID_FFFC&MI_00

%ZTEFFFB% = Modem2, USB\VID_19D2&PID_FFFB&MI_00
%ZTEFFFA% = Modem2, USB\VID_19D2&PID_FFFA&MI_00
%ZTEFFF9% = Modem2, USB\VID_19D2&PID_FFF9&MI_00
%ZTEFFF8% = Modem2, USB\VID_19D2&PID_FFF8&MI_00
%ZTEFFF7% = ModemRevA, USB\VID_19D2&PID_FFF7&MI_00
%ZTEFFF6% = ModemRevA, USB\VID_19D2&PID_FFF6&MI_01 ; MI_00 is Used for USB Disk
%ZTEFFF1% = ModemRevA, USB\VID_19D2&PID_FFF1&MI_00
%ZTEFFF0% = ModemRevA, USB\VID_19D2&PID_FFF0&MI_04
%ZTEFFEF% = Modem2, USB\VID_19D2&PID_FFEF&MI_00
%ZTEFFEE% = Modem2, USB\VID_19D2&PID_FFEE&MI_00
%ZTEFFEC% = Modem2, USB\VID_19D2&PID_FFEC&MI_03
%ZTEFFEA% = Modem2, USB\VID_19D2&PID_FFEA&MI_01
%ZTEFFE9% = Modem2, USB\VID_19D2&PID_FFE9&MI_00
%ZTEFFE8% = Modem2, USB\VID_19D2&PID_FFE8&MI_00
%ZTEFFE7% = Modem2, USB\VID_19D2&PID_FFE7&MI_00
%ZTEFFE4% = Modem2, USB\VID_19D2&PID_FFE4&MI_00

screenshot for error - The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering

Apparently the “hash” of “.inf” file was changed because I have edited it and was not in accordance with the Security Catalog file “.cat”. Then I tried to edit the “.inf” file again, this time I tried to give a sign “;” on the line Catalogfile so that the statement is no longer used because it is considered as a comment, and then I went back into device manager to try to update the driver again, and I encountered this error “The third-party INF does not contain digital signature information.”

[Version]
Signature="$WINDOWS NT$"
Class=Modem
Provider=%ZTEMT%
CLASSGUID={4D36E96D-E325-11CE-BFC1-08002BE10318}
DriverVer=05/13/2010,2.0.5.6
;Catalogfile = ztemtusbser.cat

screenshot for - The third-party INF does not contain digital signature information

In Windows 7, if you install a driver that does not have digital signature information, then Windows 7 will give us two options: “Do not install this driver software / Install this driver any way “. However, in windows 8 it did not appear that options. I had to restart the computer and press F8 on the dual boot menu. It would appear the “Startup settings” menu and then I selected the seventh option “Disable driver signature enforcement”.

windows 8 startup settings

Install this driver software any way - screenshot

When I tried to update the driver from device manager again, eventually a small window appeared with the two choices: “Do not install this driver software / Install this driver software any way”, and I certainly chose “Install this driver software any way” and successfully, the driver was installed perfectly. I hope my experience is useful for those of you who have driver compatibility issues in Windows 8.

  • Ted

    I’m confused, I’m just about to edit all of the .inf file, and when i located the driver’s location I found alot of .inf files, (ten to be exact). Am I supposed to edit all of them?

    • picohelp

      yes, it’s easy, use Notepad++ http://notepad-plus-plus.org/
      Search > Replace > Replace All

      • Ted

        I got it to work, thanks a lot for your help. :)

        • picohelp

          You’re welcome :)

  • Guest

    will it work for prolink h5200?

  • Bobbie

    good on you for your persistence. Will have to try this tonight

  • Simon

    Great, your explanation! I was just able to install the driver for the Trendnet TFM-561U USB-Modem. Thanks a lot.

  • GAGAN

    still not working with my CDMA MODEM :(

  • geminiman7

    Wow! I just purchased a Trendnet Wireless N adapter and ran into the “hash file” error message when trying to install it on my desktop running Windows 8. I was determined to find a way to fix the issue without going back to the store, and ran across your solution. Worked like a charm!
    Thank you!!!

  • Mike

    Thank you very much!!!! This worked perfectly for a 3G USB Modem..I was about to installa Windows 7 on the computer just for this but with your help I got it to work in Windows 8

  • Sambit

    It says the required line was not found in the inf

  • Dani

    Thank you very much!!! I have used it with my Wifi OvisLink EVO-W542PCI in Windows 8, and worked perfect.

    I simply would recommend an easy way to go to the startup settings:

    http://windows.microsoft.com/es-es/windows-8/windows-startup-settings-including-safe-mode

  • Neocsatornaja

    Dose’nt work with Winfast dv 2000 driver :(