wootility "Device Init Failed" | Wooting | Page 1

outer glen May 7, 2023, 9:44 AM

#

Change the input of other USB socket , wont work

#

📎 message.txt

#

📎 message.txt

paper arrow May 8, 2023, 9:48 PM

#

Please run this command and proivide the generated file "USB devices.txt" here: pnputil /enum-devices /class USB > USB devices.txt

outer glen May 9, 2023, 3:52 AM

#

@paper arrow

📎 USDdevices.txt

paper arrow May 9, 2023, 4:25 PM

#

You have a Razer Viper V2 Pro, do you also have the dongle?

outer glen May 9, 2023, 5:24 PM

#

yes

paper arrow May 9, 2023, 5:33 PM

#

Can you tell me the device ID of the dongle from the device manager.

outer glen May 9, 2023, 7:40 PM

#

Device HID\VID_1532&PID_00A6&MI_00\7&4e813a5&0&0000 was configured.

Driver Name: oem19.inf
Class Guid: {4d36e96f-e325-11ce-bfc1-08002be10318}
Driver Date: 02/23/2022
Driver Version: 10.0.15063.0
Driver Provider: Razer Inc
Driver Section: RzDev_Device.NT
Driver Rank: 0xFF0001
Matching Device Id: HID\VID_1532&PID_00A6&MI_00
Outranked Drivers: msmouse.inf:HID_DEVICE_SYSTEM_MOUSE:00FF1003 input.inf:HID_DEVICE:00FF1005
Device Updated: true
Parent Device: USB\VID_1532&PID_00A6&MI_00\6&77cae1e&0&0000

paper arrow May 9, 2023, 7:44 PM

#

That should be the virtual part of the mouse. I would assume the dongle is different.

outer glen May 9, 2023, 7:51 PM

#

hmm where should i find athatd

paper arrow May 9, 2023, 7:54 PM

#

I would assume it's somewhere shown in device manager.

outer glen May 10, 2023, 11:48 AM

#

Any other solution

#

As no idea how to locate them as they just look the same

#

Plus it been few month no issue with razer all this while

paper arrow May 10, 2023, 1:04 PM

#

I arranged that I can get the mouse and the dongle for testing. So I can check it out by my own.

To address the reconnection issue there is only a workaround so far. I don't have much data of this but so far it seems that the issue is gone after a clean install of Win from the fresh. Please consider that and report back how it went for you in the case you do it.

outer glen May 10, 2023, 2:35 PM

#

Device HID\VID_1532&PID_00A6&MI_01&Col02\7&2d52c16e&0&0001 was configured.

Driver Name: oem20.inf
Class Guid: {4d36e96f-e325-11ce-bfc1-08002be10318}
Driver Date: 02/23/2022
Driver Version: 10.0.15063.0
Driver Provider: Razer Inc
Driver Section: RzDev_Device.NT
Driver Rank: 0xFF0001
Matching Device Id: HID\VID_1532&PID_00A6&MI_01&Col02
Outranked Drivers: msmouse.inf:HID_DEVICE_SYSTEM_MOUSE:00FF1003 input.inf:HID_DEVICE:00FF1005
Device Updated: true
Parent Device: USB\VID_1532&PID_00A6&MI_01\6&77cae1e&0&0001

outer glen May 10, 2023, 5:29 PM

#

found it

paper arrow May 10, 2023, 7:30 PM

#

outer glen found it

From the data I know this looks more to me as the virtual device for the macro support of the product.

outer glen May 11, 2023, 3:46 AM

#

As when I unplug and plug in again this is the device would be reappeared other than the mice it self

paper arrow May 11, 2023, 4:49 PM

#

Ok, thx... As far as I know the virtual device is enabled only when the physical device is present. But it doesn't matter, I can inspect it myself when I get the device.

paper arrow May 11, 2023, 6:39 PM

#

It seem that there is a workaround by reinstalling Win from the fresh of a clean source. Please consider that and report back how it went if you do it.

#wootility "Device Init Failed"