Build 16170 and 16176 - USB scanners don't work

This may be an issue with the USB driver rather than your scanner. I have just received the latest build and now both my keyboard and mouse (both on USB) are not functioning. They power fine but after POST they both turn off. I cant log in or access the PC at all. 

Reboot tried already so next gonna try changing both to see if that helps. 

I am on b.16176 and I have an old Epson SX415 printer scanner and a USB wireless keyboard & mouse. The keyboard & mouse work fine. The printer drivers are kept/re-installed by each successive build but the scanner drivers I keep on a stick and I have to re-install them each time. This is probably because they are old Windows 7 drivers, but they work fine.

Have you tried looking for drivers at Epson & Fujitsu? Even old/older drivers sometimes work.

Davy.

One thought would be to try installing your device driver in Compatibility Mode. I've been doing this for quite some time for a couple of devices on my Windows 10 system of which one device is a USB scanner. The procedure for doing this is as follows:

1: Locate your device driver setup file on your system. Typically, that will be a setup.exe file included in your installation media.

2: Right click on the file to bring up Properties and select it.

3: Select the Compatibility tab.

4: Inside, you will find Compatibility Mode about half way down with a check box to "Run this program in compatibility mode for:"

5: Once you have checked the box, you can then use the drop down box and select which version of windows to run the program as.

6: Click on Apply.

7: Now you can run your device driver installation program by normal means.

Hello Peter, 

 can you scan using WIAacmgr (in windows/system32) ? that was a workaround for me.

Best regards,

- Guillaume

Thanks to all who replied. Compatibility mode didn't work. Neither did WIAacmgr, no scanner installed, but Windows Fax and Scan did, in a very primitive manner. I wouldn't like to have to do any amount of work with it.

I've had a lot of problems with these post-Creators builds, 16179 as well, not just with the scanners, quite unlike my experience with the insider program over more than two years, but I managed, at the second attempt, to get a spare drive onto Creators Edition and switched to the slow ring so everything is working as it should but not on an insiders build.

Thanks to all who replied. Compatibility mode didn't work. Neither did WIAacmgr, no scanner installed, but Windows Fax and Scan did, in a very primitive manner. I wouldn't like to have to do any amount of work with it.

I've had a lot of problems with these post-Creators builds, 16179 as well, not just with the scanners, quite unlike my experience with the insider program over more than two years, but I managed, at the second attempt, to get a spare drive onto Creators Edition and switched to the slow ring so everything is working as it should but not on an insiders build.

I am fighting with an Epson scanner on a Toshiba W10 public build.  It keeps losing the IP address.  It is on a friend's PC and I can play around with the IP address and I can hit it.  He has a HP laptop that hits it all the time.  I can go to the HP, get the current IP address and just insert this into the Toshiba and it lasts for a while.

The issue is likely that the Toshiba should be using a "Static" IP address and that is the route of the issue.  One of these days, I will go in and change the setting from the other type which is a floating IP, or whatever.

Here is what I do -

1   I search for Epson Scan Settings and look at the IP address

2  I delete the current IP address.   I add a new IP address that seems to range from, .010 to .015 on this IP.

3   This always works for a week or so but then it loses the IP.  I then repeat

This may not be your issue but the Epson seems to have this problem as a common problem.  The Epson seems to demand a Static IP address.  I will be trying this soon.

Mel