Nest building has begun, March Skip to main content. Accessed 28 December If it works for you, please let me know? I was able to get mine functioning.
|Date Added:||27 June 2009|
|File Size:||16.50 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
For anyone who may be interested, my hardware ID was:.
Up to drivers not work!!! Tried these drivers and several others including the one that came with the hardware: Compare this with C: Choose the option to select the device from a list and click “Next. Thanks apyrexia, awesome work!
Suspicious Activity Detected
On Windows 10 Microsoft uses some compatibly drivers for this esycap dated from Someone knows how could I solve this problem? The older easycaps, when they were genuine, came with VideoStudio 8. Perhaps an older version of Windows 10 may work until Microsoft pushes it to update.
Driver details should be: I use this to capture the video signal for use in vMix. Muchas Gracias desde ya. VLC now captures audio and video. Unfortunately that usbtc007 most likely a bad fake! I didnt find any driver for it.
Non of them detecting this device. You may need to reboot if need be.
video capture – Easycap not working on windows 10 – Super User
Did you get this message? I thought it was the driver for a long time until it hit me try a quality usb cable.
Open the ZIP file and extract the drivers to a folder on your desktop. I’m about to give up and usbfv007 give my 8mm DV’s to a company who do this for money. However, I got the same yellow exclamation mark once I plugged the EasyCap. I have a 4ch usb dvr device.
I have windows 10 64bit and have install EasyCap W7 W10 x I have been trying for a long time. Visser, which one of the links goes to this copy? Notify me eeasycap new posts by email.
I do have to say a big Thank You! Did anyone have any ideas? The 1 channel version works though. INF file and not being able to migrate the driver.
ShieldSquare reCAPTCHA Page
At all may it a driver problem? It still works with Win10 64bit. This can be a device driver issue, such as failure to meet new signing requirements. I tried all the drivers on your website but nothing works. I was looking for a solution during a long time.