Microsoft Surface Book Keyboard issues with Revit 2017

[Anonymous]

I have a Microsoft Surface Book with the performance package. I don't have lag issues or any performance issues with running Revit, but occasionally my keyboard will stop responding. The keyboard will respond periodically, but never go back to normal response times once it starts glitching. I have changed the resolution around like the other posts have suggested to deal with visual glitching, but still run into Keyboard issues. I noticed one other person saying the same thing as a piggyback on another post, but it didn't receive any input. 

[chris_hagan]

I am having this issue.  I just came across this issue page.  Is a fix available?

I am running a surface book i7, 16gb ram, with nvidia video card.

This occurs when using Revit 2018.3.2.7.

[Anonymous]

I started using Revit 2018 and recently switched to Revit 2019. I haven't
had an issue with either of the new versions.

[Anonymous]

Using Surface book with performance base - i7 - 16gb ram - 512gb ssd. After spending hours and hours trouble shooting and clean install of windows I finally found this thread. Thought it was a computer issue not a revit software issue.

Currently using revit 2019.2 and the keyboard will become unresponsive. Didn't have the issue in revit 2018... 

Anybody also having issues in 2019?

[Viveka_CD]

Hi @Anonymous 

Here are some steps to try:

1. Please see: Troubleshoot your Surface Type Cover or keyboard

2. Download the Surface Diagnostic Toolkit for Windows 10 Home or Windows 10 Pro and check if this resolves the issue

If none of the above help, please send me the diagnostic data for further investigation.

Please see the article for more information:

Revit - Collecting and sending diagnostic data to Autodesk Technical Support

Regards,

[ryangriffin.arch]

Are there any other threads that have answers to this issue?!?!?!?!?! It's been years I've been working with this issue. Same things happens with AutoCAD.

[csds360]

I had my Surface replaced by my company on an unrelated issue and no longer have this issue with the new one. However, the solution I found with my previous Surface was to buy a small USB wired number pad and plug that in when portable working. That seemed to keep this issue at bay.