On the PC the keyboard is connected via USB. On the Surface Pro 3 it is the type cover which is connected via the standard port that the Surface uses for the touch cover. On the Surface the touch screen controls work as expected, this is only an issue with the keyboard. I am not experiencing keyboard issues with any other application or game on either the PC or the Surface.
As I mentioned I am only seeing this on the latest Insider builds. PC is on 1511 Build 14332.1001. I believe the build you are using 10586.218 is the standard released update. I realize there are some expectations that there may be issues with Windows 10 Insider Builds, but I wanted to bring this bug up since it is impacting multiple devices.
This issue seems like it may be related to MCPE-14055, the suggestion in that issue was build 14342 resolved the issue. Installing now and will report back. This build was just released to the fast ring in the last 24 hours.
Matt Gartman
MCPE-14382
rplatham,
On the PC the keyboard is connected via USB. On the Surface Pro 3 it is the type cover which is connected via the standard port that the Surface uses for the touch cover. On the Surface the touch screen controls work as expected, this is only an issue with the keyboard. I am not experiencing keyboard issues with any other application or game on either the PC or the Surface.
As I mentioned I am only seeing this on the latest Insider builds. PC is on 1511 Build 14332.1001. I believe the build you are using 10586.218 is the standard released update. I realize there are some expectations that there may be issues with Windows 10 Insider Builds, but I wanted to bring this bug up since it is impacting multiple devices.
This issue seems like it may be related to
MCPE-14055, the suggestion in that issue was build 14342 resolved the issue. Installing now and will report back. This build was just released to the fast ring in the last 24 hours.Just finished the upgraded to Win10 14342 which seems to have resolved this issue on the PC. Will try to upgrade the surface tomorrow and report back.
Just wanted to confirm that Win10 Build 14342 has resolved this issue (and
MCPE-14382) for me as well.