Zadig crash on launch on Windows XP,about pbatard/libwdi

Comments (32)

pbatard commented on July 17, 2024

I've been testing Zadig XP 2.1.0 on physical machines with Windows XP SP3 installed, and I have not observed any crash. Your report is also the only one I got about a crash on XP, and I have seen more than 1,000 downloads of the 2.1.0 XP version so far, without any similar report (so I have to assume that it worked for these other 999 XP users).

This means that, whatever it is, it is linked to your specific environment, and without access to it, it will be very difficult to troubleshoot...

I installed the Microsoft .net framework, because I saw a post that it was required.

Whoever posted that is wrong. Zadig does not need .NET or any kind of additional framework to run.

Since I can't replicate the crash, I'm afraid the only option I see would be for you to recompile Zadig from its source using Visual Studio 2012 or later, and run it in the Visual Studio debugger to see where it crashes.

Or you can try installing DebugView and see if there are any messages that can be of interest there (as the latest verstion of Zadig will try to send some output to DebugView), but since it seems to crash on startup, I'm not sure there will be much to help.

from libwdi.

Dot-Dash commented on July 17, 2024

I had no doubt that this was a rare issue. No one ships or recommends software that crashes immediately, and Zadig comes recommended. But, there's a first time for everything.

I tried it with DebugView and there were no messages. My system is a desktop Athlon 1.2 GHz with "only" 786 Mbytes of RAM. There's no chance Zadig needs some huge amount of RAM, is there? I watched in Task Manager, and at the point of the crash, Zadig has 10,688 K allocated.

As for Visual Studio, I'm pretty sure this machine doesn't meet the minimum system requirements.

from libwdi.

pbatard commented on July 17, 2024

OK, can you try this then?:

Download xusb.exe from here and save it to a directory.
Open a command prompt and navigate to this directory.
Run the command xusb -d 2>xusb.log
Send me the xusb.log or copy it here.

from libwdi.

Dot-Dash commented on July 17, 2024

Okay. Here is the xusb.log output:

[timestamp] [threadID] facility level [function call] <message>
--------------------------------------------------------------------------------
[ 0.030043] [00000f78] libusb: debug [libusb_get_device_list] 
[ 0.040058] [00000f78] libusb: debug [windows_get_device_list] allocating new device for session [2DC]
[ 0.040058] [00000f78] libusb: debug [windows_get_device_list] allocating new device for session [2DD]
[ 0.040058] [00000f78] libusb: debug [windows_get_device_list] allocating new device for session [1EB]
[ 0.040058] [00000f78] libusb: debug [windows_get_device_list] allocating new device for session [26E]
[ 0.040058] [00000f78] libusb: debug [windows_get_device_list] allocating new device for session [26F]
[ 0.050072] [00000f78] libusb: debug [get_api_type] driver(s): usbhub
[ 0.050072] [00000f78] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.050072] [00000f78] libusb: debug [windows_get_device_list] allocating new device for session [8A]
[ 0.160230] [00000f78] libusb: debug [get_api_type] driver(s): usbhub
[ 0.160230] [00000f78] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.160230] [00000f78] libusb: debug [windows_get_device_list] allocating new device for session [369]
[ 0.160230] [00000f78] libusb: debug [get_api_type] driver(s): usbhub
[ 0.160230] [00000f78] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.160230] [00000f78] libusb: debug [windows_get_device_list] allocating new device for session [73]
[ 0.270389] [00000f78] libusb: debug [get_api_type] driver(s): usbhub
[ 0.270389] [00000f78] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.270389] [00000f78] libusb: debug [windows_get_device_list] allocating new device for session [D0]
[ 0.270389] [00000f78] libusb: debug [get_api_type] driver(s): usbhub
[ 0.270389] [00000f78] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.270389] [00000f78] libusb: debug [windows_get_device_list] allocating new device for session [3B0]
[ 0.270389] [00000f78] libusb: debug [get_api_type] driver(s): usbhub
[ 0.270389] [00000f78] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.270389] [00000f78] libusb: debug [windows_get_device_list] allocating new device for session [3A6]
[ 0.280403] [00000f78] libusb: debug [windows_get_device_list] found existing device for session [8A] (0.0)
[ 0.280403] [00000f78] libusb: debug [init_device] (bus: 5, addr: 1, depth: 0, port: 0): '\\.\USB#ROOT_HUB#4&11F23577&0'
[ 0.280403] [00000f78] libusb: debug [windows_get_device_list] found existing device for session [369] (0.0)
[ 0.280403] [00000f78] libusb: debug [init_device] (bus: 1, addr: 1, depth: 0, port: 0): '\\.\USB#ROOT_HUB#4&1ADBC963&0'
[ 0.280403] [00000f78] libusb: debug [windows_get_device_list] found existing device for session [73] (0.0)
[ 0.280403] [00000f78] libusb: debug [init_device] (bus: 4, addr: 1, depth: 0, port: 0): '\\.\USB#ROOT_HUB#4&24ABE61C&0'
[ 0.280403] [00000f78] libusb: debug [windows_get_device_list] found existing device for session [D0] (0.0)
[ 0.280403] [00000f78] libusb: debug [init_device] (bus: 2, addr: 1, depth: 0, port: 0): '\\.\USB#ROOT_HUB#4&82218BE&0'
[ 0.280403] [00000f78] libusb: debug [windows_get_device_list] found existing device for session [3B0] (0.0)
[ 0.280403] [00000f78] libusb: debug [init_device] (bus: 3, addr: 1, depth: 0, port: 0): '\\.\USB#ROOT_HUB20#4&1991E997&0'
[ 0.300432] [00000f78] libusb: debug [windows_get_device_list] allocating new device for session [3E2]
[ 0.300432] [00000f78] libusb: debug [init_device] found 1 configurations (active conf: 1)
[ 0.310446] [00000f78] libusb: debug [cache_config_descriptors] cached config descriptor 0 (bConfigurationValue=1, 34 bytes)
[ 0.310446] [00000f78] libusb: debug [init_device] (bus: 4, addr: 2, depth: 1, port: 1): '\\.\USB#VID_046D&PID_C069#5&243B83A0&0&1'
[ 0.310446] [00000f78] libusb: debug [windows_get_device_list] allocating new device for session [2FF]
[ 0.320461] [00000f78] libusb: debug [init_device] found 1 configurations (active conf: 1)
[ 0.330475] [00000f78] libusb: debug [cache_config_descriptors] cached config descriptor 0 (bConfigurationValue=1, 59 bytes)
[ 0.330475] [00000f78] libusb: debug [init_device] (bus: 4, addr: 3, depth: 1, port: 2): '\\.\USB#VID_0566&PID_3107#5&243B83A0&0&2'
[ 0.330475] [00000f78] libusb: debug [windows_get_device_list] found existing device for session [3A6] (0.0)
[ 0.330475] [00000f78] libusb: debug [init_device] found 1 configurations (active conf: 1)
[ 0.340490] [00000f78] libusb: debug [cache_config_descriptors] cached config descriptor 0 (bConfigurationValue=1, 25 bytes)
[ 0.340490] [00000f78] libusb: debug [init_device] (bus: 5, addr: 3, depth: 1, port: 2): '\\.\USB#VID_058F&PID_9254#5&3A4D5D40&0&2'
[ 0.340490] [00000f78] libusb: info [windows_get_device_list] The following device has no driver: '\\.\USB#VID_0BDA&PID_2832#77771111153705700'
[ 0.340490] [00000f78] libusb: info [windows_get_device_list] libusb will not be able to access it.
[ 0.340490] [00000f78] libusb: debug [windows_get_device_list] allocating new device for session [250]
[ 0.340490] [00000f78] libusb: debug [init_device] found 1 configurations (active conf: 0)
[ 0.340490] [00000f78] libusb: debug [cache_config_descriptors] cached config descriptor 0 (bConfigurationValue=1, 25 bytes)
[ 0.340490] [00000f78] libusb: debug [init_device] (bus: 3, addr: 2, depth: 1, port: 5): '\\.\USB#VID_0BDA&PID_2832#77771111153705700'
[ 0.340490] [00000f78] libusb: debug [discovered_devs_append] need to increase capacity
[ 0.340490] [00000f78] libusb: debug [windows_get_device_list] allocating new device for session [36E]
[ 0.340490] [00000f78] libusb: debug [init_device] found 1 configurations (active conf: 1)
[ 0.340490] [00000f78] libusb: debug [cache_config_descriptors] cached config descriptor 0 (bConfigurationValue=1, 60 bytes)
[ 0.340490] [00000f78] libusb: debug [init_device] (bus: 5, addr: 2, depth: 1, port: 1): '\\.\USB#VID_0CF3&PID_9271#12345'
[ 0.350504] [00000f78] libusb: debug [get_api_type] driver(s): HidUsb
[ 0.350504] [00000f78] libusb: debug [get_api_type] matched driver name against HID API API
[ 0.350504] [00000f78] libusb: debug [windows_get_device_list] found existing device for session [3E2] (4.2)
[ 0.350504] [00000f78] libusb: debug [get_api_type] driver(s): usbccgp
[ 0.350504] [00000f78] libusb: debug [get_api_type] matched driver name against Composite API API
[ 0.350504] [00000f78] libusb: debug [windows_get_device_list] found existing device for session [2FF] (4.3)
[ 0.350504] [00000f78] libusb: debug [get_api_type] driver(s): AR9271
[ 0.350504] [00000f78] libusb: debug [windows_get_device_list] found existing device for session [36E] (5.2)
[ 0.350504] [00000f78] libusb: debug [windows_get_device_list] setting HID interface for [3E2]:
[ 0.350504] [00000f78] libusb: debug [set_hid_interface] interface[0] = \\.\HID#VID_046D&PID_C069#6&11C859A4&0&0000#{4D1E55B2-F16F-11CF-88CB-001111000030}
[ 0.350504] [00000f78] libusb: debug [windows_get_device_list] setting composite interface for [2FF]:
[ 0.350504] [00000f78] libusb: debug [set_composite_interface] interface[0] = \\.\HID#VID_0566&PID_3107&MI_00#7&2C064073&0&0000#{4D1E55B2-F16F-11CF-88CB-001111000030}
[ 0.350504] [00000f78] libusb: debug [windows_get_device_list] setting composite interface for [2FF]:
[ 0.350504] [00000f78] libusb: debug [set_composite_interface] interface[1] = \\.\HID#VID_0566&PID_3107&MI_01&COL01#7&1442B42E&0&0000#{4D1E55B2-F16F-11CF-88CB-001111000030}
[ 0.350504] [00000f78] libusb: debug [windows_get_device_list] setting composite interface for [2FF]:
[ 0.350504] [00000f78] libusb: debug [set_composite_interface] interface[1] already set - ignoring HID collection: \\.\HID#VID_0566&PID_3107&MI_01&COL02#7&1442B42E&0&0001
[ 0.350504] [00000f78] libusb: debug [libusb_get_device_descriptor] 
[ 0.350504] [00000f78] libusb: debug [libusb_get_device_descriptor] 
[ 0.350504] [00000f78] libusb: debug [libusb_get_device_descriptor] 
[ 0.350504] [00000f78] libusb: debug [libusb_get_device_descriptor] 
[ 0.350504] [00000f78] libusb: debug [libusb_get_device_descriptor] 
[ 0.350504] [00000f78] libusb: debug [libusb_get_device_descriptor] 
[ 0.350504] [00000f78] libusb: debug [libusb_get_device_descriptor] 
[ 0.350504] [00000f78] libusb: debug [libusb_get_device_descriptor] 
[ 0.350504] [00000f78] libusb: debug [libusb_get_device_descriptor] 
[ 0.350504] [00000f78] libusb: debug [libusb_get_device_descriptor] 
[ 0.350504] [00000f78] libusb: debug [libusb_unref_device] destroy device 1.1
[ 0.350504] [00000f78] libusb: debug [libusb_unref_device] destroy device 1.0
[ 0.350504] [00000f78] libusb: debug [libusb_unref_device] destroy device 2.1
[ 0.350504] [00000f78] libusb: debug [libusb_unref_device] destroy device 2.0
[ 0.350504] [00000f78] libusb: debug [libusb_unref_device] destroy device 4.2
[ 0.350504] [00000f78] libusb: debug [libusb_unref_device] destroy device 4.3
[ 0.350504] [00000f78] libusb: debug [libusb_unref_device] destroy device 4.1
[ 0.350504] [00000f78] libusb: debug [libusb_unref_device] destroy device 4.0
[ 0.350504] [00000f78] libusb: debug [libusb_unref_device] destroy device 5.3
[ 0.350504] [00000f78] libusb: debug [libusb_unref_device] destroy device 3.2
[ 0.350504] [00000f78] libusb: debug [libusb_unref_device] destroy device 3.1
[ 0.350504] [00000f78] libusb: debug [libusb_unref_device] destroy device 3.0
[ 0.350504] [00000f78] libusb: debug [libusb_unref_device] destroy device 5.2
[ 0.350504] [00000f78] libusb: debug [libusb_unref_device] destroy device 5.1
[ 0.350504] [00000f78] libusb: debug [libusb_unref_device] destroy device 5.0
  Failed.
[ 0.350504] [00000f78] libusb: debug [libusb_exit] 
[ 0.350504] [00000f78] libusb: debug [libusb_exit] destroying default context

from libwdi.

pbatard commented on July 17, 2024

Thanks. I'm not seeing much of anything suspicious with your devices.

Can you confirm that you have a Riched20.dll in your C:\Windows\System32\ directory? Also what does issuing echo %USERPROFILE% from a command prompt report?

from libwdi.

Dot-Dash commented on July 17, 2024

Yep. Riched20.dll is there.

C:\Documents and Settings\Operator>echo %USERPROFILE%
C:\Documents and Settings\Operator

C:\Documents and Settings\Operator>dir C:\Windows\System32\rich*
 Volume in drive C has no label.
 Volume Serial Number is 986F-D493

 Directory of C:\Windows\System32

04/13/2008  07:12 PM           433,664 riched20.dll
08/23/2001  07:00 AM             3,584 riched32.dll
05/22/2000  12:00 AM           203,976 RICHTX32.OCX
               3 File(s)        641,224 bytes
               0 Dir(s)  61,238,771,712 bytes free

from libwdi.

pbatard commented on July 17, 2024

It looks like you don't have the USERPROFILE environment variable defined.
Can you please define it (to something like "C:\Documents and Settings\Operator") and see if that works better?

from libwdi.

Dot-Dash commented on July 17, 2024

USERPROFILE is already set to "C:\Documents and Settings\Operator" (2nd line of previous post).

from libwdi.

pbatard commented on July 17, 2024

My bad. I thought that the value was empty and that the prompt was just repeated.

Well, I don't have any further ideas, so I'm afraid you'll have to debug Zadig on that specific machine to find out why it crashes...

from libwdi.

pbatard commented on July 17, 2024

One last thing you may want to try, to see if it helps, is download this sample zadig.ini and save it in the same directory as the one where you have Zadig. Then try to launch Zadig and see if it still crashes.

from libwdi.

Dot-Dash commented on July 17, 2024

Sorry. Thanks for the ideas, but it still crashes. I have been playing around, but nothing I have done has changed the situation yet.

from libwdi.

Dot-Dash commented on July 17, 2024

FYI, Booting Windows in Safe Mode made no difference in the problem. I tried a couple of other things with that xusb.exe Option "-i : print topology and speed info". Here is the output for my USB mouse:

C:\Documents and Settings\Operator\My Documents\Software Defined Radio\Drivers>x
usb.exe -i 046d:c069
Using libusb v1.0.18.10866

Opening device 046D:C069...
libusb: info [windows_get_device_list] The following device has no driver: '\\.\
USB#VID_0BDA&PID_2832#77771111153705700'
libusb: info [windows_get_device_list] libusb will not be able to access it.
libusb: warning [hid_open] could not open HID device in R/W mode (keyboard or mo
use?) - trying without

Device properties:
        bus number: 4
         port path: 1 (from root hub)
             speed: 1.5 Mbit/s (USB LowSpeed)

Reading device descriptor:
            length: 18
      device class: 0
               S/N: 0
           VID:PID: 046D:C069
         bcdDevice: 5601
   iMan:iProd:iSer: 1:2:0
          nb confs: 1

Reading BOS descriptor: libusb: error [libusb_get_bos_descriptor] failed to read
 BOS (-2)
no descriptor

Reading first configuration descriptor:
             nb interfaces: 1
              interface[0]: id = 0
interface[0].altsetting[0]: num endpoints = 1
   Class.SubClass.Protocol: 03.01.02
       endpoint[0].address: 81
           max packet size: 0006
          polling interval: 0A

Claiming interface 0...

Reading string descriptors:
   String (0x01): "Logitech"
   String (0x02): "USB Laser Mouse"

Releasing interface 0...
Closing device...
libusb: warning [libusb_exit] some libusb_devices were leaked

And here is the output for my TV/SDR Dongle:

C:\Documents and Settings\Operator\My Documents\Software Defined Radio\Drivers>x
usb.exe -i 0bda:2832
Using libusb v1.0.18.10866

Opening device 0BDA:2832...
libusb: info [windows_get_device_list] The following device has no driver: '\\.\
USB#VID_0BDA&PID_2832#77771111153705700'
libusb: info [windows_get_device_list] libusb will not be able to access it.
  Failed.

C:\Documents and Settings\Operator\My Documents\Software Defined Radio\Drivers>

The crash occurs whether or not the dongle is plugged in.

from libwdi.

luisgild commented on July 17, 2024

Same crash here, I cannot install Zadig (XP version). My system is an eBox 3310MX, running Windows XP SP3, processor is a Vortex86MX+. My plan is to use a SDR dongle as well, I'm using it flawlessly in other machines.

from libwdi.

luisgild commented on July 17, 2024

Tried same steps you proposed:

Dbgview shows no message at all.
This is my xusb.log

[timestamp] [threadID] facility level [function call] <message>
--------------------------------------------------------------------------------
[ 0.020028] [00000d68] libusb: debug [libusb_get_device_list] 
[ 0.030043] [00000d68] libusb: debug [windows_get_device_list] allocating new device for session [2BC]
[ 0.030043] [00000d68] libusb: debug [windows_get_device_list] allocating new device for session [2C4]
[ 0.030043] [00000d68] libusb: debug [windows_get_device_list] allocating new device for session [109]
[ 0.030043] [00000d68] libusb: debug [windows_get_device_list] allocating new device for session [111]
[ 0.040057] [00000d68] libusb: debug [get_api_type] driver(s): usbhub
[ 0.040057] [00000d68] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.040057] [00000d68] libusb: debug [windows_get_device_list] allocating new device for session [2C2]
[ 0.040057] [00000d68] libusb: debug [get_api_type] driver(s): usbhub
[ 0.040057] [00000d68] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.040057] [00000d68] libusb: debug [windows_get_device_list] allocating new device for session [7D]
[ 0.150216] [00000d68] libusb: debug [get_api_type] driver(s): usbhub
[ 0.150216] [00000d68] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.150216] [00000d68] libusb: debug [windows_get_device_list] allocating new device for session [272]
[ 0.150216] [00000d68] libusb: debug [get_api_type] driver(s): usbhub
[ 0.150216] [00000d68] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.150216] [00000d68] libusb: debug [windows_get_device_list] allocating new device for session [C4]
[ 0.160230] [00000d68] libusb: debug [get_api_type] driver(s): usbhub
[ 0.160230] [00000d68] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.160230] [00000d68] libusb: debug [windows_get_device_list] allocating new device for session [113]
[ 0.160230] [00000d68] libusb: debug [windows_get_device_list] found existing device for session [2C2] (0.0)
[ 0.160230] [00000d68] libusb: debug [init_device] (bus: 2, addr: 1, depth: 0, port: 0): '\\.\USB#ROOT_HUB#3&1BB80852&0'
[ 0.160230] [00000d68] libusb: debug [windows_get_device_list] found existing device for session [7D] (0.0)
[ 0.160230] [00000d68] libusb: debug [init_device] (bus: 1, addr: 1, depth: 0, port: 0): '\\.\USB#ROOT_HUB#3&2DFE8C8&0'
[ 0.170244] [00000d68] libusb: debug [windows_get_device_list] found existing device for session [272] (0.0)
[ 0.170244] [00000d68] libusb: debug [init_device] (bus: 4, addr: 1, depth: 0, port: 0): '\\.\USB#ROOT_HUB20#3&2726E719&0'
[ 0.170244] [00000d68] libusb: debug [windows_get_device_list] found existing device for session [C4] (0.0)
[ 0.170244] [00000d68] libusb: debug [init_device] (bus: 3, addr: 1, depth: 0, port: 0): '\\.\USB#ROOT_HUB20#3&770C9B8&0'
[ 0.170244] [00000d68] libusb: debug [windows_get_device_list] found existing device for session [113] (0.0)
[ 0.170244] [00000d68] libusb: debug [init_device] found 1 configurations (active conf: 1)
[ 0.170244] [00000d68] libusb: debug [cache_config_descriptors] cached config descriptor 0 (bConfigurationValue=1, 25 bytes)
[ 0.170244] [00000d68] libusb: debug [init_device] (bus: 1, addr: 2, depth: 1, port: 1): '\\.\USB#VID_058F&PID_9254#4&DE15B3&0&1'
[ 0.170244] [00000d68] libusb: debug [windows_get_device_list] allocating new device for session [27E]
[ 0.170244] [00000d68] libusb: debug [init_device] found 1 configurations (active conf: 1)
[ 0.170244] [00000d68] libusb: debug [cache_config_descriptors] cached config descriptor 0 (bConfigurationValue=1, 46 bytes)
[ 0.170244] [00000d68] libusb: debug [init_device] (bus: 3, addr: 2, depth: 1, port: 2): '\\.\USB#VID_07D1&PID_3303#00E04C000001'
[ 0.170244] [00000d68] libusb: info [windows_get_device_list] The following device has no driver: '\\.\USB#VID_0BDA&PID_2832#77771111153705700'
[ 0.170244] [00000d68] libusb: info [windows_get_device_list] libusb will not be able to access it.
[ 0.170244] [00000d68] libusb: debug [windows_get_device_list] allocating new device for session [250]
[ 0.170244] [00000d68] libusb: debug [init_device] found 1 configurations (active conf: 0)
[ 0.170244] [00000d68] libusb: debug [cache_config_descriptors] cached config descriptor 0 (bConfigurationValue=1, 25 bytes)
[ 0.170244] [00000d68] libusb: debug [init_device] (bus: 1, addr: 3, depth: 2, port: 4): '\\.\USB#VID_0BDA&PID_2832#77771111153705700'
[ 0.170244] [00000d68] libusb: debug [windows_get_device_list] allocating new device for session [20B]
[ 0.170244] [00000d68] libusb: debug [init_device] found 1 configurations (active conf: 1)
[ 0.180259] [00000d68] libusb: debug [cache_config_descriptors] cached config descriptor 0 (bConfigurationValue=1, 34 bytes)
[ 0.180259] [00000d68] libusb: debug [init_device] (bus: 2, addr: 2, depth: 1, port: 1): '\\.\USB#VID_15CA&PID_00C3#4&308D38F8&0&1'
[ 0.180259] [00000d68] libusb: debug [get_api_type] driver(s): RTL8192su
[ 0.180259] [00000d68] libusb: debug [windows_get_device_list] found existing device for session [27E] (3.2)
[ 0.180259] [00000d68] libusb: debug [get_api_type] driver(s): HidUsb
[ 0.180259] [00000d68] libusb: debug [get_api_type] matched driver name against HID API API
[ 0.180259] [00000d68] libusb: debug [windows_get_device_list] found existing device for session [20B] (2.2)
[ 0.190273] [00000d68] libusb: debug [windows_get_device_list] setting HID interface for [20B]:
[ 0.190273] [00000d68] libusb: debug [set_hid_interface] interface[0] = \\.\HID#VID_15CA&PID_00C3#5&24370EF2&0&0000#{4D1E55B2-F16F-11CF-88CB-001111000030}
[ 0.190273] [00000d68] libusb: debug [libusb_get_device_descriptor] 
[ 0.190273] [00000d68] libusb: debug [libusb_get_device_descriptor] 
[ 0.190273] [00000d68] libusb: debug [libusb_get_device_descriptor] 
[ 0.190273] [00000d68] libusb: debug [libusb_get_device_descriptor] 
[ 0.190273] [00000d68] libusb: debug [libusb_get_device_descriptor] 
[ 0.190273] [00000d68] libusb: debug [libusb_get_device_descriptor] 
[ 0.190273] [00000d68] libusb: debug [libusb_get_device_descriptor] 
[ 0.190273] [00000d68] libusb: debug [libusb_get_device_descriptor] 
[ 0.190273] [00000d68] libusb: debug [libusb_unref_device] destroy device 4.1
[ 0.190273] [00000d68] libusb: debug [libusb_unref_device] destroy device 4.0
[ 0.190273] [00000d68] libusb: debug [libusb_unref_device] destroy device 3.2
[ 0.190273] [00000d68] libusb: debug [libusb_unref_device] destroy device 3.1
[ 0.190273] [00000d68] libusb: debug [libusb_unref_device] destroy device 3.0
[ 0.190273] [00000d68] libusb: debug [libusb_unref_device] destroy device 1.3
[ 0.190273] [00000d68] libusb: debug [libusb_unref_device] destroy device 1.2
[ 0.190273] [00000d68] libusb: debug [libusb_unref_device] destroy device 1.1
[ 0.190273] [00000d68] libusb: debug [libusb_unref_device] destroy device 1.0
[ 0.190273] [00000d68] libusb: debug [libusb_unref_device] destroy device 2.2
[ 0.190273] [00000d68] libusb: debug [libusb_unref_device] destroy device 2.1
[ 0.190273] [00000d68] libusb: debug [libusb_unref_device] destroy device 2.0
  Failed.
[ 0.190273] [00000d68] libusb: debug [libusb_exit] 
[ 0.190273] [00000d68] libusb: debug [libusb_exit] destroying default context

from libwdi.

luisgild commented on July 17, 2024

Riched20.dll and riched32.dll are present on c:\windows\system32.

Microsoft Windows XP [Versión 5.1
(C) Copyright 1985-2001 Microsoft

C:\Documents and Settings\Luis>echo %USERPROFILE%
C:\Documents and Settings\Luis

C:\Documents and Settings\Luis>

from libwdi.

pbatard commented on July 17, 2024

I'm not seeing much of anything that looks wrong, and without being able to run a debugger on your machine, it will be very difficult to identify the cause of the crash.
Is there any way you can run Visual Studio on that system?
If not, I'll see if I can cook something with gdb, but that will probably take some time...

Also what happens if you go to the device manager and uninstall the RTL8192su driver for your RTL device. Do you still see the crash if the RTL device has no driver?

from libwdi.

luisgild commented on July 17, 2024

I have very little space left but tell me the minimum necessary to debug and I'll try.

Yes, same crash even with no dongle connected and driver removed. This is the exception thrown if it is of any help:

Exception Information
Code:  0xc000001d    Flags: 0x00000000
Record: 0x0000000000000000   Address: 0x000000000040131a

System Information
Windows NT 5.1 Build: 2600
CPU Vendor Code: 74726F56 - 36387865 - 436F5320
CPU Version: 00000586    CPU Feature Code: 00800111
CPU AMD Feature Code: 00D1E824

Module 1
zadig_xp_2.1.0.exe
Image Base: 0x00400000    Image Size: 0x00000000
Checksum: 0x0052eb91    Time Stamp: 0x52f04100
Version Information
 Signature:  feef04bd
 StrucVer:  00010000
 FileVer:  (2.1:0.658)
 ProdVer:  (2.1:0.658)
 FlagMask:  00000017
 Flags:  00000000
 OS:  00040004
 FileType:  00000001
 SubType:  00000000
 FileDate:  00000000:00000000

from libwdi.

luisgild commented on July 17, 2024

Which version of Visual Studio and .NET should I try to install to debug Zadig? Minimum possible please, as I don't have too much space left.

from libwdi.

pbatard commented on July 17, 2024

Visual Studio 2012 is what you should use, as this is the only version of VS for which I provide the solution files. Zadig is NOT a .NET application, so you don't need to bother about that.

To debug Zadig, you will need to recompile libwdi by following this guide.

I still haven't given up on trying to provide a debug version that works with gdb, but I've been busy with other things...

from libwdi.

luisgild commented on July 17, 2024

Thanks Pete. I see the minimum requirement for Visual Studio 12 is Windows 7, but this machine only runs Windows XP. Do I need to recompile in this same machine, or could it be done in another one running Windows XP as well?

from libwdi.

pbatard commented on July 17, 2024

Well, unless you got through a remote install of the debugger, you don't have to install VS on the same machine, and I remember using VS 2012 to remote debug an app on an XP machine in the past.
But using the remote debugger is a bit of a pain, and you'll have to figure out how to set it up.

from libwdi.

luisgild commented on July 17, 2024

Finally no way to install Visual Studio on that machine, there is very few space left. So I hope Pete can provide us a debug version or give up trying to use Zadig on that little box.

from libwdi.

stebo4u commented on July 17, 2024

I have the same issue while trying to use Zadig on an older PC with XP SP3 installed. Error code 0xc000001d at address 0x0040b9f9.

from libwdi.

pbatard commented on July 17, 2024

I'll see what I can do, but I'm afraid to say that, with Windows XP having reached its official end of life, investigating XP specific issues has become low priority for me...

from libwdi.

stebo4u commented on July 17, 2024

Figured out, that a Zadig Version 1.1 works fine, thus for me no need to dig any further in the XP issue.

from libwdi.

luisgild commented on July 17, 2024

I really understand your position, it sounds logical. Bt I'm sure that even when official Windows XP lifetime is over, it will still last for a while on lower end device such thinclients and so on.

Anyway, thanks a lot for your great piece of software working fine on other platforms.

from libwdi.

pbatard commented on July 17, 2024

I have just published a BETA version of Zadig that may fix some of the crash issues reported here.
Can anyone who had experienced a crash download zadig_xp_2.1.1_BETA.exe from here?

from libwdi.

luisgild commented on July 17, 2024

Oh nice !! I thought this was a lost cause :)
Please give me some time (a couple of days) and I'll try your new version. Thanks a lot Pete.

from libwdi.

pbatard commented on July 17, 2024

Note: Zadig 2.1.1 has now been released. Please let me know if it also fixes this issue on XP.

from libwdi.

luisgild commented on July 17, 2024

Hi Pete, sorry for the delay.

No good news, zadig_xp_2.1.1.exe still crashes, "program encountered a problem and need to be closed".

from libwdi.

Dot-Dash commented on July 17, 2024

Pete, I'm sorry for the delay also. I no longer have the machine or environment to reproduce my original crash report.

from libwdi.

pbatard commented on July 17, 2024

Since Windows XP is officially retired, and my time is too limited for that, I am not planning to spend any effort investigating XP specific issues. I will therefore close this issue.

I will however accept a fix, if anybody still using Windows XP wants to investigate and try to patch the problem. libwdi/Zadig is Free Software for precisely that reason.

from libwdi.

Zadig crash on launch on Windows XP about libwdi HOT 32 CLOSED

Comments (32)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent