Auvisio VRC-1100 stopped working after Win 10 update 1607

Found a bug in EventGhost? Report it here.

Re: Auvisio VRC-1100 stopped working after Win 10 update 160

Postby kgschlosser » Wed Feb 08, 2017 6:54 pm

ok cool then i will know to look at the files on the eg server.. and i am also going to modify the WinUSB file to produce some really detailed logging so we can see what exactly is going wrong. instead of some mystery "install failed" statement
If you like the work I have been doing then feel free to Image
User avatar
kgschlosser
Site Admin
 
Posts: 2140
Joined: Fri Jun 05, 2015 5:43 am
Location: Rocky Mountains, Colorado USA

Re: Auvisio VRC-1100 stopped working after Win 10 update 160

Postby topix » Fri Feb 10, 2017 3:18 pm

topix
Experienced User
 
Posts: 299
Joined: Sat May 05, 2007 3:43 pm
Location: Germany

Re: Auvisio VRC-1100 stopped working after Win 10 update 160

Postby kgschlosser » Sat Feb 11, 2017 10:58 am

it very well could be... but i will tell you this.. the source files for the win usb wrapper between the 2 versions are identical. but the actual DLL's are 2 different sizes.

and the modified dates
EG 0.5 - Monday, ‎December ‎12, ‎2016, ‏‎2:34:08 PM
EG 0.4 - Monday, ‎February ‎15, ‎2016, ‏‎7:37:32 PM


So I have attached a copy if the WinUSBWrapper.dll from EG 0.4

I am not sure what versions of EG everyone is running. But the file is attached.. unzip it into the folder

YOUR_EG_INSTALL_DIR\lib27\site-packages

if you are running version 0.4 then it's not the dll file..
Attachments
WinUsbWrapper.zip
(1.82 KiB) Downloaded 30 times
If you like the work I have been doing then feel free to Image
User avatar
kgschlosser
Site Admin
 
Posts: 2140
Joined: Fri Jun 05, 2015 5:43 am
Location: Rocky Mountains, Colorado USA

Re: Auvisio VRC-1100 stopped working after Win 10 update 160

Postby mrceolla » Sun Feb 12, 2017 5:37 pm

I was running a 0.4 version :-(
mrceolla
 
Posts: 10
Joined: Wed Sep 07, 2011 11:51 pm

Re: Auvisio VRC-1100 stopped working after Win 10 update 160

Postby kgschlosser » Mon Feb 13, 2017 12:10 am

according to Microsoft if you upgraded to 1607 then the whole thing with them stopping unsigned drivers has not been turned on.. it is only if 1607 is a new install..

But Microsoft has been known to f*#$ things up quite a bit so... I am thinking from here i am going to have to modify the WinUsb.py file and add some aggressive debugging to see what is going on.
If you like the work I have been doing then feel free to Image
User avatar
kgschlosser
Site Admin
 
Posts: 2140
Joined: Fri Jun 05, 2015 5:43 am
Location: Rocky Mountains, Colorado USA

Previous

Return to Bug Reports

Who is online

Users browsing this forum: No registered users and 1 guest