Home Dashboard Directory Help
Search

Twain driver in Windows Kits by Tom Mein


Status: 

Active


1
0
Sign in
to vote
Type: Bug
ID: 800947
Opened: 9/16/2013 6:54:05 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

The installation of the Windows kits Twain driver has made myCanon LiDE 25 scanner inoperable (cannot connect to twain driver)
Details
Sign in to post a comment.
Posted by Microsoft on 10/2/2013 at 12:50 PM
Thank you for submitting this bug. This site is focused on accepting bugs for Visual Studio and .NET Framework, however, this issue appears to be related to the Windows operating system so we have transferred it over to the Windows team for review. further support. Should more information be needed, someone from the Windows team will follow up with you. We’ve created some online forums where you can ask questions, post issues and get answers from other preview testers and Microsoft support professionals. We encourage active participation in these forums as the best way to provide feedback to Microsoft.

•Visit the Windows 8.1 Preview forum (http://aka.ms/WinPreviewForum)
•Visit the Internet Explorer 11 Preview forum (http://aka.ms/IEPreviewForum)
•Visit the developer forums for building apps (http://aka.ms/DevBuildApps)
•Visit the IT pro forums for Windows 8.1 business features (http://aka.ms/ITProForum)
Posted by Khuram Shahid on 9/17/2013 at 4:20 PM
Could you please elaborate on what exactly you mean by "Windows kits Twain driver", and also include exact repro steps?

From the current description, I suspect this issue is not related to Visual Studio, or the Windows Driver Kit.
Posted by Microsoft on 9/16/2013 at 7:17 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 9/16/2013 at 7:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.