Menu
▾
▴
libusb-win32-devel
|
From: Steinspecht <ste...@gm...> - 2014-02-19 08:43:21
|
Hello, I don't see any way to uninstall libusb-win32. It is not an option in the device manager nor in Programs and Features. I use Win 8.1. How should I proceed? Thanks for helping, steinspecht |
|
From: Xiaofan C. <xia...@gm...> - 2014-02-19 12:36:05
|
On Wed, Feb 19, 2014 at 4:43 PM, Steinspecht <ste...@gm...> wrote: > Hello, > I don't see any way to uninstall libusb-win32. It is not an option in the > device manager nor in Programs and Features. I use Win 8.1. > > How should I proceed? We need to know how you install libusb-win32 (and which version) before telling you how to uninstall libusb-win32. -- Xiaofan |
|
From: Steinspecht <ste...@gm...> - 2014-02-19 13:09:18
|
Hi Xiaofan, I have installed libusb-win32-bin-1.2.6.0 using the inf-wizard.exe and the corresponding .inf file. Thanks, Steinspecht sorry for the nuisance with erroneously sent message. > -----Ursprüngliche Nachricht----- > Von: Xiaofan Chen [mailto:xia...@gm...] > Gesendet: Mittwoch, 19. Februar 2014 13:36 > An: lib...@li... > Betreff: Re: [Libusb-win32-devel] uninstalling libusb-win32 > > On Wed, Feb 19, 2014 at 4:43 PM, Steinspecht <ste...@gm...> wrote: > > Hello, > > I don't see any way to uninstall libusb-win32. It is not an option in > > the device manager nor in Programs and Features. I use Win 8.1. > > > > How should I proceed? > > We need to know how you install libusb-win32 (and which > version) before telling you how to uninstall libusb-win32. > > > -- > Xiaofan > > ---------------------------------------------------------------------------- -- > Managing the Performance of Cloud-Based Applications Take advantage of > what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktr > k > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
|
From: Xiaofan C. <xia...@gm...> - 2014-02-19 23:01:48
|
On Wed, Feb 19, 2014 at 9:09 PM, Steinspecht <ste...@gm...> wrote: > Hi Xiaofan, > > I have installed libusb-win32-bin-1.2.6.0 using the inf-wizard.exe and the > corresponding .inf file. I see. Then there is nothing to uninstall. If your device is using the libusb-win32 driver and you are still using the device, then you will need the driver. If you no longer need to use the device, then you can leave the system as it is. Next time when you need the device again, you plug in the device, and then your device will work again. On the other hand, if you really need to remove the driver files from the system (from the driver store), then you can use tools like pnputils. Ref: http://technet.microsoft.com/en-us/library/cc730875.aspx A nice GUI program is here (Windows 7 and higher only). http://driverstoreexplorer.codeplex.com/ Travis has also written a command line which works from Windows Vista and up. https://code.google.com/p/picusb/downloads/detail?name=PnpFind.7z -- Xiaofan |
|
From: Steinspecht <ste...@gm...> - 2014-02-20 08:50:26
|
Thanks. I ran the driverstoreexplorer tool you recommended and deleted it. It is no longer listed in the driver store. The pnputil.exe -e tool doesn't list it either. However, after a cold reboot it still shows in the device manager as "libusb-win32 devices" and reacts to connecting/disconnecting the camera, so it is still there alive and kicking. Any suggestion? > -----Ursprüngliche Nachricht----- > Von: Xiaofan Chen [mailto:xia...@gm...] > Gesendet: Donnerstag, 20. Februar 2014 00:02 > An: lib...@li... > Betreff: Re: [Libusb-win32-devel] uninstalling libusb-win32 > > On Wed, Feb 19, 2014 at 9:09 PM, Steinspecht <ste...@gm...> wrote: > > Hi Xiaofan, > > > > I have installed libusb-win32-bin-1.2.6.0 using the inf-wizard.exe and > > the corresponding .inf file. > > I see. Then there is nothing to uninstall. If your device is using the libusb-win32 > driver and you are still using the device, then you will need the driver. > > If you no longer need to use the device, then you can leave the system as it is. > Next time when you need the device again, you plug in the device, and then your > device will work again. > > On the other hand, if you really need to remove the driver files from the system > (from the driver store), then you can use tools like pnputils. > > Ref: http://technet.microsoft.com/en-us/library/cc730875.aspx > > A nice GUI program is here (Windows 7 and higher only). > http://driverstoreexplorer.codeplex.com/ > > Travis has also written a command line which works from Windows Vista and up. > https://code.google.com/p/picusb/downloads/detail?name=PnpFind.7z > > > -- > Xiaofan > > ---------------------------------------------------------------------------- -- > Managing the Performance of Cloud-Based Applications Take advantage of > what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktr > k > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
|
From: Xiaofan C. <xia...@gm...> - 2014-02-20 08:54:39
|
On Thu, Feb 20, 2014 at 4:50 PM, Steinspecht <ste...@gm...> wrote: > Thanks. > > I ran the driverstoreexplorer tool you recommended and deleted it. It is no > longer listed in the driver store. The pnputil.exe -e tool doesn't list it > either. > > However, after a cold reboot it still shows in the device manager as > "libusb-win32 devices" and reacts to connecting/disconnecting the camera, so > it is still there alive and kicking. > > Any suggestion? That is strange. You may have some 3rd party software running which automatically install the driver. Please check if that is the case. -- Xiaofan |
|
From: Steinspecht <ste...@gm...> - 2014-02-20 09:02:13
|
None I'm aware of. Just checked autostart and running processes, both in user and admin accounts. What applications could automatically load this driver?? > -----Ursprüngliche Nachricht----- > Von: Xiaofan Chen [mailto:xia...@gm...] > Gesendet: Donnerstag, 20. Februar 2014 09:55 > An: lib...@li... > Betreff: Re: [Libusb-win32-devel] uninstalling libusb-win32 > > On Thu, Feb 20, 2014 at 4:50 PM, Steinspecht <ste...@gm...> wrote: > > Thanks. > > > > I ran the driverstoreexplorer tool you recommended and deleted it. It > > is no longer listed in the driver store. The pnputil.exe -e tool > > doesn't list it either. > > > > However, after a cold reboot it still shows in the device manager as > > "libusb-win32 devices" and reacts to connecting/disconnecting the > > camera, so it is still there alive and kicking. > > > > Any suggestion? > > That is strange. You may have some 3rd party software running which > automatically install the driver. Please check if that is the case. > > > > -- > Xiaofan > > ---------------------------------------------------------------------------- -- > Managing the Performance of Cloud-Based Applications Take advantage of > what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktr > k > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
|
From: Xiaofan C. <xia...@gm...> - 2014-02-20 09:46:58
|
On Thu, Feb 20, 2014 at 5:02 PM, Steinspecht <ste...@gm...> wrote: > None I'm aware of. Just checked autostart and running processes, both in > user and admin accounts. > What applications could automatically load this driver?? > I am not aware of any applications. Your system seems to be strange. Anyway I think you can try one experiment, use Zadig to replace your device driver from libusb0.sys to WinUSB. Then reboot to see if WinUSB driver is still there or not. After that, use driverstoreexplorer tool to remove the WinUSB driver and then reboot to see what happens. Zadig: http://zadig.akeo.ie/ http://zadig.akeo.ie/downloads/zadig_2.1.0.exe -- Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2014-02-20 09:50:25
|
On Thu, Feb 20, 2014 at 5:46 PM, Xiaofan Chen <xia...@gm...> wrote: > On Thu, Feb 20, 2014 at 5:02 PM, Steinspecht <ste...@gm...> wrote: >> None I'm aware of. Just checked autostart and running processes, both in >> user and admin accounts. >> What applications could automatically load this driver?? >> > > I am not aware of any applications. > > Your system seems to be strange. BTW, by default, libusb-win32-bin-1.2.6.0's inf-wizard.exe will not work under Windows 8 and Windows 8.1. As such, we have deprecated the inf-wizard.exe and suggest users to use Zadig or libusbK's inf-wizard GUI. What did you do to your system to get the driver installed? -- Xiaofan |
|
From: Steinspecht <ste...@gm...> - 2014-02-20 10:46:55
|
Well the wizard did work. At some point Windows complained about unsigned
drivers, but I recall I overrode that.
In the Zadig tool I can't see the libusb driver on the left side of the -->
arrow. It doesn't show on the dropdown list (Options /advanced mode /list
all / ignore hubs etc.).
Here are locations of libusb0*.*
Verzeichnis von C:\Windows\System32
30.10.2013 15:52 76.384 libusb0.dll
1 Datei(en), 76.384 Bytes
Verzeichnis von C:\Windows\System32\drivers
30.10.2013 15:52 52.832 libusb0.sys
1 Datei(en), 52.832 Bytes
Verzeichnis von C:\Windows\SysWOW64
30.10.2013 15:52 67.680 libusb0.dll
1 Datei(en), 67.680 Bytes
Anzahl der angezeigten Dateien:
3 Datei(en), 196.896 Bytes
0 Verzeichnis(se), 316.990.201.856 Bytes frei
> -----Ursprüngliche Nachricht-----
> Von: Xiaofan Chen [mailto:xia...@gm...]
> Gesendet: Donnerstag, 20. Februar 2014 10:50
> An: lib...@li...
> Betreff: Re: [Libusb-win32-devel] uninstalling libusb-win32
>
> On Thu, Feb 20, 2014 at 5:46 PM, Xiaofan Chen <xia...@gm...> wrote:
> > On Thu, Feb 20, 2014 at 5:02 PM, Steinspecht <ste...@gm...>
wrote:
> >> None I'm aware of. Just checked autostart and running processes, both
> >> in user and admin accounts.
> >> What applications could automatically load this driver??
> >>
> >
> > I am not aware of any applications.
> >
> > Your system seems to be strange.
>
> BTW, by default, libusb-win32-bin-1.2.6.0's inf-wizard.exe will not work
under
> Windows 8 and Windows 8.1. As such, we have deprecated the inf-wizard.exe
> and suggest users to use Zadig or libusbK's inf-wizard GUI.
>
> What did you do to your system to get the driver installed?
>
>
> --
> Xiaofan
>
>
----------------------------------------------------------------------------
--
> Managing the Performance of Cloud-Based Applications Take advantage of
> what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
>
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktr
> k
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
|
|
From: Xiaofan C. <xia...@gm...> - 2014-02-20 11:36:22
|
On Thu, Feb 20, 2014 at 6:46 PM, Steinspecht <ste...@gm...> wrote: > Well the wizard did work. At some point Windows complained about unsigned > drivers, but I recall I overrode that. I see. That is not good for your system. Anyway, please do not use libusb-win32 inf-wizard for Windows 8 and 8.1 in the future. > In the Zadig tool I can't see the libusb driver on the left side of the --> > arrow. It doesn't show on the dropdown list (Options /advanced mode /list > all / ignore hubs etc.). > Since your device is using libusb0.sys, then you can select WinUSB to replace your current driver. Is your device a USB composite device? In that case, you need to select the USB Composite Parent. -- Xiaofan |
|
From: Kustaa N. <Kus...@pl...> - 2014-02-20 11:41:27
|
On 20/02/2014 13:36, "Xiaofan Chen" <xia...@gm...> wrote: > >I see. That is not good for your system. Out of curiosity, why do you say that, what does it do to the system? br Kusti This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general. |
|
From: Xiaofan C. <xia...@gm...> - 2014-02-20 12:17:29
|
On Thu, Feb 20, 2014 at 7:41 PM, Kustaa Nyholm <Kus...@pl...> wrote: > On 20/02/2014 13:36, "Xiaofan Chen" <xia...@gm...> wrote: >> >>I see. That is not good for your system. > > Out of curiosity, why do you say that, what does it do to the system? > By overwriting the driver signature enforcement on the machine, the system can run unsigned drivers which may be malicious. Therefore it is more meant for developers/testers of Windows driver and not for normal users. -- Xiaofan |
|
From: Kustaa N. <Kus...@pl...> - 2014-02-20 13:09:57
|
On 20/02/2014 14:17, "Xiaofan Chen" <xia...@gm...> wrote: > >By overwriting the driver signature enforcement on the machine, >the system can run unsigned drivers which may be malicious. >Therefore it is more meant for developers/testers of Windows >driver and not for normal users. I see, thanks. Personally (if I were a Windows user) I could not care less, signing has never saved the day for me (knock on wood) but is always getting in the way of doing things. Going OT at the tangent but last week I ventured to Win7 and up on quitting an application I was running W7 said: "this application may required administrator rights, would you like to run it always with administrator rights?" or words to that effect...hmmm first they make a fuss how you never should (and I agree) run with admin rights and then they actively volunteer to do it for you...go figure. br Kusti This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general. |
|
From: Graeme G. <gr...@ar...> - 2014-02-21 00:58:53
|
Kustaa Nyholm wrote: > Personally (if I were a Windows user) I could not > care less, signing has never saved the day for me (knock > on wood) but is always getting in the way of doing things. Agreed. There is far too much faith put in the fact that something is signed, when this proves little directly about the origin of the software, and nothing about the trustworthiness of the company behind it or the software itself. The idea that some authority is somehow actively policing the software and revoking certificates is a quaint one. It may happen, but only in the most egregious of cases. The rest of the time we have to judge trustworthiness on evidence and reputation, whether the software is signed or not. Graeme Gill. |
|
From: Graeme G. <gr...@ar...> - 2014-02-21 00:50:50
|
Xiaofan Chen wrote: > By overwriting the driver signature enforcement on the machine, > the system can run unsigned drivers which may be malicious. It only runs the unsigned driver you installed while signature enforcement is off. When your reboot it returns to not installing unsigned drivers. Graeme Gill. |
|
From: Xiaofan C. <xia...@gm...> - 2014-02-21 11:58:12
|
On Fri, Feb 21, 2014 at 8:50 AM, Graeme Gill <gr...@ar...> wrote: > Xiaofan Chen wrote: > >> By overwriting the driver signature enforcement on the machine, >> the system can run unsigned drivers which may be malicious. > > It only runs the unsigned driver you installed while > signature enforcement is off. When your reboot it > returns to not installing unsigned drivers. That is not true. It depends on what you do. Eg: http://msdn.microsoft.com/en-us/library/windows/hardware/ff553484(v=vs.85).aspx -- Xiaofan |
|
From: Graeme G. <gr...@ar...> - 2014-02-22 06:37:10
|
Xiaofan Chen wrote: > That is not true. It depends on what you do. > > Eg: http://msdn.microsoft.com/en-us/library/windows/hardware/ff553484(v=vs.85).aspx I'm not referring to test boot signing - that's of very limited use with the latest versions of MSWin. I'm referring to the "Disable Driver Signature Enforcement" boot option. Graeme Gil. |
|
From: Steinspecht <ste...@gm...> - 2014-02-20 13:02:50
|
I'm afraid I'm a bit out of my depth here. > > Since your device is using libusb0.sys, then you can select WinUSB to replace > your current driver. > WinUSB is not shown by the Zadig tool. On the left-hand field there is this entry: HidUsb (v6.3.9600.16384 or USBSTOR (v6.3.9600.16475) depending on what's selected on the drop-down list above it. On the drop-down list there is no entry like WinUSB or libusbxxx. The listed entries are: USB2.0-CRW (Interface 1) Media Center Interface (Interface 0) My Passport 0730 [an external hard disk drive] EP1 Interrupt (Interface 0) Media Center Interface (Interface 1) EP2 Interrupt (Interface 1) Bulk-In, Bulk-Out, Interface (Interface 0) And that's it. The log says however: Zadig 2.1.0.658 Windows 8.1 64-bit ini file 'zadig.ini' not found - default parameters will be used default driver set to 'WinUSB' 0 devices found. 7 devices found. To answer your question: > Is your device a USB composite device? In that case, you need to select the USB > Composite Parent. My device is a Canon Powershot G10 camera. Composite? I don't know. Its original driver was installed automatically when I first connected it. Since the system doesn't see it properly due to libusb-win32, it cannot re-install the driver. I didn't do anything extravagant to my system (the unsigned driver override is long since reversed to normal security state). Conversely I must ask, why isn't it possible to remove the libusb-win32 driver in a standard way via the device manager? This is a moot point anyway. I appreciate your assistance very much, so please help me with removing it. Regards, Steinspecht |
|
From: Pete B. <pe...@ak...> - 2014-02-20 13:29:01
Attachments:
Image1.png
|
On 2014.02.20 13:02, Steinspecht wrote: > WinUSB is not shown by the Zadig tool. Are you sure? Please see the attached screenshot, and especially the part inside red ellipse. This is where you can select the target driver, and switch between WinUSB, libusb-win32 and libusbK. I'd be exceedingly surprised if your application doesn't show this... Regards, /Pete |
|
From: Xiaofan C. <xia...@gm...> - 2014-02-20 13:43:14
|
On Thu, Feb 20, 2014 at 9:02 PM, Steinspecht <ste...@gm...> wrote: > I didn't do anything extravagant to my system (the unsigned driver override > is long since reversed to normal security state). Conversely I must ask, why > isn't it possible to remove the libusb-win32 driver in a standard way via > the device manager? This is a moot point anyway. You should be able to. But there is something wrong with your system. BTW, removing the driver from the device manager does not remove the driver file, it just remove the association between the device and the driver. Usually driverstoreexplorer works. I do not know why it does not work for you. > I appreciate your assistance very much, so please help me > with removing it. Please try to use Zadig again. BTW, are you sure if your device is recognized by the system and is using libusb-win32 driver? Please post the screenshot of your device manager entry of your camera. -- Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2014-02-20 13:46:43
|
On Thu, Feb 20, 2014 at 9:02 PM, Steinspecht <ste...@gm...> wrote: > My device is a Canon Powershot G10 camera. Composite? I don't know. Its > original driver was installed automatically when I first connected it. Since > the system doesn't see it properly due to libusb-win32, it cannot re-install > the driver. > BTW, what do you mean by the system doesn't see it properly? Have you by any chance installed libusb-win32 filter as a class filter before? That could cause problems for the system. Ref: http://libusb.6.n5.nabble.com/BSOD-on-XP-td5712832.html -- Xiaofan |
|
From: Graeme G. <gr...@ar...> - 2014-02-21 00:59:25
|
Steinspecht wrote:
> I appreciate your assistance very much, so please help me with removing it.
If this is Vista or latter, while not just "remove completely"
using device manager ?
ie:
Plug in the device
Start -> Control Panel -> Hardware and Sound -> Device Manager
Locate the device in the device list.
Right click on instrument -> Uninstall -> click "Delete the driver software for this
device" -> OK
Graeme Gill.
|
|
From: Xiaofan C. <xia...@gm...> - 2014-02-20 11:38:01
|
On Thu, Feb 20, 2014 at 4:50 PM, Steinspecht <ste...@gm...> wrote: > Thanks. > > I ran the driverstoreexplorer tool you recommended and deleted it. It is no > longer listed in the driver store. The pnputil.exe -e tool doesn't list it > either. > > However, after a cold reboot it still shows in the device manager as > "libusb-win32 devices" and reacts to connecting/disconnecting the camera, so > it is still there alive and kicking. > BTW, what is the original driver for your camera? You can use Windows to roll back the driver to your original driver (either provided by the vendor or Windows). -- Xiaofan |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X