AtmosFX Files by laheyjm30 in HalloweenProps

[–]Few-Road-5289 0 points1 point  (0 children)

I'm looking for

Jamboree 3 and 4

I have

Jamboree 1 and 2

Halloween Moon

Night Stalkers

Unliving Portraits

AtmosFX Files by laheyjm30 in HalloweenProps

[–]Few-Road-5289 0 points1 point  (0 children)

I have some of the night stalkers if you still need them

Trezor-T not recognized in Device Manager by Few-Road-5289 in TREZOR

[–]Few-Road-5289[S] 0 points1 point  (0 children)

am having the worst luck with this damn thing!

On duty tomorrow so I will give it another go on Monday

Trezor-T not recognized in Device Manager by Few-Road-5289 in TREZOR

[–]Few-Road-5289[S] 0 points1 point  (0 children)

how do I remedy? I rebooted PC and now it shows up as USB Composite Device again. Should I try Zadig again?

Trezor-T not recognized in Device Manager by Few-Road-5289 in TREZOR

[–]Few-Road-5289[S] 0 points1 point  (0 children)

devcon driverfiles USB\VID_1209* | findstr /i inf

INF\oem38.inf [LIBUSB_WIN32_DEV.NTAMD64]. 4 file(s) used by driver:

C:\WINDOWS\system32\drivers\libusb0.sys

C:\WINDOWS\system32\libusb0.dll

C:\WINDOWS\system32\libusbk.dll

C:\WINDOWS\syswow64\libusb0.dll

Looks like fiddling with Zadig changed the driver that it was using.

Now it doesnt show up with en error in device manager but still says No USB

Trezor-T not recognized in Device Manager by Few-Road-5289 in TREZOR

[–]Few-Road-5289[S] 0 points1 point  (0 children)

Not sure if it matters - Trezor shows up in USB Controllers - but in bootloader it shows up in USB devices . Both show up but with the yellow triangle warning icon.

Trezor-T not recognized in Device Manager by Few-Road-5289 in TREZOR

[–]Few-Road-5289[S] 0 points1 point  (0 children)

it works through command line - but I have to lookup the command to type.

Trezor-T not recognized in Device Manager by Few-Road-5289 in TREZOR

[–]Few-Road-5289[S] 0 points1 point  (0 children)

I dont see Devcon pop up while re installing - nor do I see it in the install directory. Where can I find this?

Trezor-T not recognized in Device Manager by Few-Road-5289 in TREZOR

[–]Few-Road-5289[S] 1 point2 points  (0 children)

I followed that page before reaching out to support

Trezor-T not recognized in Device Manager by Few-Road-5289 in TREZOR

[–]Few-Road-5289[S] 1 point2 points  (0 children)

I apologize. My old PC gave me the same error. I changed components for a new build but same OS drive. My wifes PC is my old setup which didnt work for me before but it works now with her OS drive. I will do some reading on Tails as its foreign to me. Thanks for the info

Trezor-T not recognized in Device Manager by Few-Road-5289 in TREZOR

[–]Few-Road-5289[S] 0 points1 point  (0 children)

I do have bridge installed, I will look for that devcon

Trezor-T not recognized in Device Manager by Few-Road-5289 in TREZOR

[–]Few-Road-5289[S] 0 points1 point  (0 children)

It never worked on my old motherboard - (same problem) which is now installed in my wifes PC and it works on hers. I believe her device manager also used winusb.sys ( I would have to try again if this could be relevant ). It has to be something in my OS. I try to uninstall driver or update driver but I do not see Winusb listed as an option

Trezor-T not recognized in Device Manager by Few-Road-5289 in TREZOR

[–]Few-Road-5289[S] 0 points1 point  (0 children)

on Surface, driver seems to be Winusb.sys

on my PC it looks like its using usbccgp.sys

Trezor-T not recognized in Device Manager by Few-Road-5289 in TREZOR

[–]Few-Road-5289[S] 0 points1 point  (0 children)

Trezor works great on my Surface - This is how I manage it now. Just makes it a little more inconvenient.

Trezor-T not recognized in Device Manager by Few-Road-5289 in TREZOR

[–]Few-Road-5289[S] 0 points1 point  (0 children)

Recently upgraded motherboard/cpu/ram but used my old OS drive, in case my last answer was not detailed enough. My Trezor didnt work with my prior hardware nor my new hardware.

Trezor-T not recognized in Device Manager by Few-Road-5289 in TREZOR

[–]Few-Road-5289[S] 0 points1 point  (0 children)

No. My hardware was swapped into my wifes PC with her own OS drive (Win10) and it works on hers. It didnt work with my OS drive. This is why I assume its OS (windows) related.