How can I package the libusbK driver on Windows 10 for redistribution?











up vote
1
down vote

favorite
1












I'm working with a GPS sports logger for which Windows 10 default installs the usbser.sys driver. This standard driver does not support the WebUSB API. For that reason, on my local Windows 10 machine, I successfully use Zadig (v2.4) to install the libusbK driver.



Because I've open sourced the WebUsb-mtk code specific to this GPS sports logger (and other loggers with the MTK 3329 GPS module), I'd like to also distribute this signed driver to other Windows 10 users of similar hardware.



What are the steps to generate an installation package that correctly disables (?) the existing driver and installs the libusbK driver for my hardware? (LibUSBK is already signed, so I think the signature is not relevant.)





p.s. With Mac OS X, WebUSB for this hardware works out of the box.










share|improve this question







New contributor




philshem is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













This question has an open bounty worth +100
reputation from philshem ending in 2 days.


This question has not received enough attention.




















    up vote
    1
    down vote

    favorite
    1












    I'm working with a GPS sports logger for which Windows 10 default installs the usbser.sys driver. This standard driver does not support the WebUSB API. For that reason, on my local Windows 10 machine, I successfully use Zadig (v2.4) to install the libusbK driver.



    Because I've open sourced the WebUsb-mtk code specific to this GPS sports logger (and other loggers with the MTK 3329 GPS module), I'd like to also distribute this signed driver to other Windows 10 users of similar hardware.



    What are the steps to generate an installation package that correctly disables (?) the existing driver and installs the libusbK driver for my hardware? (LibUSBK is already signed, so I think the signature is not relevant.)





    p.s. With Mac OS X, WebUSB for this hardware works out of the box.










    share|improve this question







    New contributor




    philshem is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.













    This question has an open bounty worth +100
    reputation from philshem ending in 2 days.


    This question has not received enough attention.


















      up vote
      1
      down vote

      favorite
      1









      up vote
      1
      down vote

      favorite
      1






      1





      I'm working with a GPS sports logger for which Windows 10 default installs the usbser.sys driver. This standard driver does not support the WebUSB API. For that reason, on my local Windows 10 machine, I successfully use Zadig (v2.4) to install the libusbK driver.



      Because I've open sourced the WebUsb-mtk code specific to this GPS sports logger (and other loggers with the MTK 3329 GPS module), I'd like to also distribute this signed driver to other Windows 10 users of similar hardware.



      What are the steps to generate an installation package that correctly disables (?) the existing driver and installs the libusbK driver for my hardware? (LibUSBK is already signed, so I think the signature is not relevant.)





      p.s. With Mac OS X, WebUSB for this hardware works out of the box.










      share|improve this question







      New contributor




      philshem is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      I'm working with a GPS sports logger for which Windows 10 default installs the usbser.sys driver. This standard driver does not support the WebUSB API. For that reason, on my local Windows 10 machine, I successfully use Zadig (v2.4) to install the libusbK driver.



      Because I've open sourced the WebUsb-mtk code specific to this GPS sports logger (and other loggers with the MTK 3329 GPS module), I'd like to also distribute this signed driver to other Windows 10 users of similar hardware.



      What are the steps to generate an installation package that correctly disables (?) the existing driver and installs the libusbK driver for my hardware? (LibUSBK is already signed, so I think the signature is not relevant.)





      p.s. With Mac OS X, WebUSB for this hardware works out of the box.







      windows-10 drivers distribution






      share|improve this question







      New contributor




      philshem is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question







      New contributor




      philshem is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question






      New contributor




      philshem is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked Nov 13 at 10:36









      philshem

      65




      65




      New contributor




      philshem is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      philshem is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      philshem is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      This question has an open bounty worth +100
      reputation from philshem ending in 2 days.


      This question has not received enough attention.








      This question has an open bounty worth +100
      reputation from philshem ending in 2 days.


      This question has not received enough attention.
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote













          According to
          libusbK - Creating Client Installers With InfWizard,
          the installer does basically all its operations by using the
          Driver Package Installer (DPInst),
          which is a standard feature in Windows.



          According to
          Using DPInst to Uninstall Driver Packages,
          the syntax to uninstall a driver is:



          DPInst.exe /u path-to-inf-file


          The driver for usbser.sys I found in the folder
          C:WindowsWinSxSamd64_dual_usbser.inf_31bf3856ad364e35_10.0.17134.1_none_8281fb62ec80df7e,
          so uninstalling it could be by using a command such as:



          DPInst.exe /u C:WindowsWinSxSamd64_dual_usbser.inf_31bf3856ad364e35_10.0.17134.1_none_8281fb62ec80df7e


          It would of course be better if your installer could verify first that this
          file exists, and if not then search for it.



          The next step would be to install libusbK using the command:



          DPInst.exe libusbK.inf


          Since you have installed libusbK, you should have the .sys and the .inf
          files that belong to it.
          You need to have them both in one folder, then invoke DPInst on the .inf
          file.



          (As I don't have these files, this answer is mostly theory.)






          share|improve this answer























          • thanks! so the installer is actually just a dos script? Can I uninstall usbser.sys for just this device, and not for potentially all devices?
            – philshem
            Nov 15 at 15:18










          • It was probably done in the installer via a program, rather than a script, but might be possible from a script. From usbser.inf I gather that this is a generic driver that is associated with USB devices in general and doesn't specify device-ids. I don't have the files for libusbK so can't examine them.
            – harrymc
            Nov 15 at 15:31










          • I read a bit more. It seems one way is to use Visual Studio to create a driver package docs.microsoft.com/en-us/windows-hardware/drivers/develop/… Also it seems DPInst is now DIFX
            – philshem
            Nov 15 at 18:21










          • Also it seems that Zadig.exe can create the files necessary to share as a driver install package. I'll keep trying, but many thanks for a push in the right direction.
            – philshem
            Nov 15 at 18:24










          • DPInst is still there and is used by the libusbK installers, so it still works as well as ever. If made available libusbK.inf/sys I'll compare with usbser.inf.
            – harrymc
            Nov 15 at 20:18











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });






          philshem is a new contributor. Be nice, and check out our Code of Conduct.










           

          draft saved


          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1374992%2fhow-can-i-package-the-libusbk-driver-on-windows-10-for-redistribution%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          1
          down vote













          According to
          libusbK - Creating Client Installers With InfWizard,
          the installer does basically all its operations by using the
          Driver Package Installer (DPInst),
          which is a standard feature in Windows.



          According to
          Using DPInst to Uninstall Driver Packages,
          the syntax to uninstall a driver is:



          DPInst.exe /u path-to-inf-file


          The driver for usbser.sys I found in the folder
          C:WindowsWinSxSamd64_dual_usbser.inf_31bf3856ad364e35_10.0.17134.1_none_8281fb62ec80df7e,
          so uninstalling it could be by using a command such as:



          DPInst.exe /u C:WindowsWinSxSamd64_dual_usbser.inf_31bf3856ad364e35_10.0.17134.1_none_8281fb62ec80df7e


          It would of course be better if your installer could verify first that this
          file exists, and if not then search for it.



          The next step would be to install libusbK using the command:



          DPInst.exe libusbK.inf


          Since you have installed libusbK, you should have the .sys and the .inf
          files that belong to it.
          You need to have them both in one folder, then invoke DPInst on the .inf
          file.



          (As I don't have these files, this answer is mostly theory.)






          share|improve this answer























          • thanks! so the installer is actually just a dos script? Can I uninstall usbser.sys for just this device, and not for potentially all devices?
            – philshem
            Nov 15 at 15:18










          • It was probably done in the installer via a program, rather than a script, but might be possible from a script. From usbser.inf I gather that this is a generic driver that is associated with USB devices in general and doesn't specify device-ids. I don't have the files for libusbK so can't examine them.
            – harrymc
            Nov 15 at 15:31










          • I read a bit more. It seems one way is to use Visual Studio to create a driver package docs.microsoft.com/en-us/windows-hardware/drivers/develop/… Also it seems DPInst is now DIFX
            – philshem
            Nov 15 at 18:21










          • Also it seems that Zadig.exe can create the files necessary to share as a driver install package. I'll keep trying, but many thanks for a push in the right direction.
            – philshem
            Nov 15 at 18:24










          • DPInst is still there and is used by the libusbK installers, so it still works as well as ever. If made available libusbK.inf/sys I'll compare with usbser.inf.
            – harrymc
            Nov 15 at 20:18















          up vote
          1
          down vote













          According to
          libusbK - Creating Client Installers With InfWizard,
          the installer does basically all its operations by using the
          Driver Package Installer (DPInst),
          which is a standard feature in Windows.



          According to
          Using DPInst to Uninstall Driver Packages,
          the syntax to uninstall a driver is:



          DPInst.exe /u path-to-inf-file


          The driver for usbser.sys I found in the folder
          C:WindowsWinSxSamd64_dual_usbser.inf_31bf3856ad364e35_10.0.17134.1_none_8281fb62ec80df7e,
          so uninstalling it could be by using a command such as:



          DPInst.exe /u C:WindowsWinSxSamd64_dual_usbser.inf_31bf3856ad364e35_10.0.17134.1_none_8281fb62ec80df7e


          It would of course be better if your installer could verify first that this
          file exists, and if not then search for it.



          The next step would be to install libusbK using the command:



          DPInst.exe libusbK.inf


          Since you have installed libusbK, you should have the .sys and the .inf
          files that belong to it.
          You need to have them both in one folder, then invoke DPInst on the .inf
          file.



          (As I don't have these files, this answer is mostly theory.)






          share|improve this answer























          • thanks! so the installer is actually just a dos script? Can I uninstall usbser.sys for just this device, and not for potentially all devices?
            – philshem
            Nov 15 at 15:18










          • It was probably done in the installer via a program, rather than a script, but might be possible from a script. From usbser.inf I gather that this is a generic driver that is associated with USB devices in general and doesn't specify device-ids. I don't have the files for libusbK so can't examine them.
            – harrymc
            Nov 15 at 15:31










          • I read a bit more. It seems one way is to use Visual Studio to create a driver package docs.microsoft.com/en-us/windows-hardware/drivers/develop/… Also it seems DPInst is now DIFX
            – philshem
            Nov 15 at 18:21










          • Also it seems that Zadig.exe can create the files necessary to share as a driver install package. I'll keep trying, but many thanks for a push in the right direction.
            – philshem
            Nov 15 at 18:24










          • DPInst is still there and is used by the libusbK installers, so it still works as well as ever. If made available libusbK.inf/sys I'll compare with usbser.inf.
            – harrymc
            Nov 15 at 20:18













          up vote
          1
          down vote










          up vote
          1
          down vote









          According to
          libusbK - Creating Client Installers With InfWizard,
          the installer does basically all its operations by using the
          Driver Package Installer (DPInst),
          which is a standard feature in Windows.



          According to
          Using DPInst to Uninstall Driver Packages,
          the syntax to uninstall a driver is:



          DPInst.exe /u path-to-inf-file


          The driver for usbser.sys I found in the folder
          C:WindowsWinSxSamd64_dual_usbser.inf_31bf3856ad364e35_10.0.17134.1_none_8281fb62ec80df7e,
          so uninstalling it could be by using a command such as:



          DPInst.exe /u C:WindowsWinSxSamd64_dual_usbser.inf_31bf3856ad364e35_10.0.17134.1_none_8281fb62ec80df7e


          It would of course be better if your installer could verify first that this
          file exists, and if not then search for it.



          The next step would be to install libusbK using the command:



          DPInst.exe libusbK.inf


          Since you have installed libusbK, you should have the .sys and the .inf
          files that belong to it.
          You need to have them both in one folder, then invoke DPInst on the .inf
          file.



          (As I don't have these files, this answer is mostly theory.)






          share|improve this answer














          According to
          libusbK - Creating Client Installers With InfWizard,
          the installer does basically all its operations by using the
          Driver Package Installer (DPInst),
          which is a standard feature in Windows.



          According to
          Using DPInst to Uninstall Driver Packages,
          the syntax to uninstall a driver is:



          DPInst.exe /u path-to-inf-file


          The driver for usbser.sys I found in the folder
          C:WindowsWinSxSamd64_dual_usbser.inf_31bf3856ad364e35_10.0.17134.1_none_8281fb62ec80df7e,
          so uninstalling it could be by using a command such as:



          DPInst.exe /u C:WindowsWinSxSamd64_dual_usbser.inf_31bf3856ad364e35_10.0.17134.1_none_8281fb62ec80df7e


          It would of course be better if your installer could verify first that this
          file exists, and if not then search for it.



          The next step would be to install libusbK using the command:



          DPInst.exe libusbK.inf


          Since you have installed libusbK, you should have the .sys and the .inf
          files that belong to it.
          You need to have them both in one folder, then invoke DPInst on the .inf
          file.



          (As I don't have these files, this answer is mostly theory.)







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 15 at 15:14

























          answered Nov 15 at 15:05









          harrymc

          247k10256542




          247k10256542












          • thanks! so the installer is actually just a dos script? Can I uninstall usbser.sys for just this device, and not for potentially all devices?
            – philshem
            Nov 15 at 15:18










          • It was probably done in the installer via a program, rather than a script, but might be possible from a script. From usbser.inf I gather that this is a generic driver that is associated with USB devices in general and doesn't specify device-ids. I don't have the files for libusbK so can't examine them.
            – harrymc
            Nov 15 at 15:31










          • I read a bit more. It seems one way is to use Visual Studio to create a driver package docs.microsoft.com/en-us/windows-hardware/drivers/develop/… Also it seems DPInst is now DIFX
            – philshem
            Nov 15 at 18:21










          • Also it seems that Zadig.exe can create the files necessary to share as a driver install package. I'll keep trying, but many thanks for a push in the right direction.
            – philshem
            Nov 15 at 18:24










          • DPInst is still there and is used by the libusbK installers, so it still works as well as ever. If made available libusbK.inf/sys I'll compare with usbser.inf.
            – harrymc
            Nov 15 at 20:18


















          • thanks! so the installer is actually just a dos script? Can I uninstall usbser.sys for just this device, and not for potentially all devices?
            – philshem
            Nov 15 at 15:18










          • It was probably done in the installer via a program, rather than a script, but might be possible from a script. From usbser.inf I gather that this is a generic driver that is associated with USB devices in general and doesn't specify device-ids. I don't have the files for libusbK so can't examine them.
            – harrymc
            Nov 15 at 15:31










          • I read a bit more. It seems one way is to use Visual Studio to create a driver package docs.microsoft.com/en-us/windows-hardware/drivers/develop/… Also it seems DPInst is now DIFX
            – philshem
            Nov 15 at 18:21










          • Also it seems that Zadig.exe can create the files necessary to share as a driver install package. I'll keep trying, but many thanks for a push in the right direction.
            – philshem
            Nov 15 at 18:24










          • DPInst is still there and is used by the libusbK installers, so it still works as well as ever. If made available libusbK.inf/sys I'll compare with usbser.inf.
            – harrymc
            Nov 15 at 20:18
















          thanks! so the installer is actually just a dos script? Can I uninstall usbser.sys for just this device, and not for potentially all devices?
          – philshem
          Nov 15 at 15:18




          thanks! so the installer is actually just a dos script? Can I uninstall usbser.sys for just this device, and not for potentially all devices?
          – philshem
          Nov 15 at 15:18












          It was probably done in the installer via a program, rather than a script, but might be possible from a script. From usbser.inf I gather that this is a generic driver that is associated with USB devices in general and doesn't specify device-ids. I don't have the files for libusbK so can't examine them.
          – harrymc
          Nov 15 at 15:31




          It was probably done in the installer via a program, rather than a script, but might be possible from a script. From usbser.inf I gather that this is a generic driver that is associated with USB devices in general and doesn't specify device-ids. I don't have the files for libusbK so can't examine them.
          – harrymc
          Nov 15 at 15:31












          I read a bit more. It seems one way is to use Visual Studio to create a driver package docs.microsoft.com/en-us/windows-hardware/drivers/develop/… Also it seems DPInst is now DIFX
          – philshem
          Nov 15 at 18:21




          I read a bit more. It seems one way is to use Visual Studio to create a driver package docs.microsoft.com/en-us/windows-hardware/drivers/develop/… Also it seems DPInst is now DIFX
          – philshem
          Nov 15 at 18:21












          Also it seems that Zadig.exe can create the files necessary to share as a driver install package. I'll keep trying, but many thanks for a push in the right direction.
          – philshem
          Nov 15 at 18:24




          Also it seems that Zadig.exe can create the files necessary to share as a driver install package. I'll keep trying, but many thanks for a push in the right direction.
          – philshem
          Nov 15 at 18:24












          DPInst is still there and is used by the libusbK installers, so it still works as well as ever. If made available libusbK.inf/sys I'll compare with usbser.inf.
          – harrymc
          Nov 15 at 20:18




          DPInst is still there and is used by the libusbK installers, so it still works as well as ever. If made available libusbK.inf/sys I'll compare with usbser.inf.
          – harrymc
          Nov 15 at 20:18










          philshem is a new contributor. Be nice, and check out our Code of Conduct.










           

          draft saved


          draft discarded


















          philshem is a new contributor. Be nice, and check out our Code of Conduct.













          philshem is a new contributor. Be nice, and check out our Code of Conduct.












          philshem is a new contributor. Be nice, and check out our Code of Conduct.















           


          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1374992%2fhow-can-i-package-the-libusbk-driver-on-windows-10-for-redistribution%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          AnyDesk - Fatal Program Failure

          How to calibrate 16:9 built-in touch-screen to a 4:3 resolution?

          QoS: MAC-Priority for clients behind a repeater