屏幕键盘在自定义外壳程序，Windows 10 Pro 1709和1803中不起作用 [英] On Screen Keyboard not working in Custom Shell, Windows 10 Pro 1709 and 1803

问题描述

Hi,

我们正在使用屏幕键盘用于我们的自定义Shell应用程序的Windows 10 Pro。

We are using the On Screen Keyboard in Windows 10 Pro for our Custom Shell application.

从版本1607和1703开始注册表设置"EnableDesktopModeAutoInvoke"在"HKCU \ SOFTWARE \ Microsoft \ TabletTip \1.7"中设置为DWORD = 1为运行应用程序的用户提供了屏幕键盘，但由于
重新设置1709，因此不再起作用。我也尝试了最新的1803版本具有相同的否定结果。

Since release 1607 and for 1703 the registry setting "EnableDesktopModeAutoInvoke" in "HKCU\SOFTWARE\Microsoft\TabletTip\1.7" set to DWORD=1 has provided the On Screen Keyboard for the user running the application, but since relase 1709 this is not working anymore. I have also tried latest 1803 relase with the same negative result.

1709年有什么变化（并且1803）发布？

What have changed in the 1709 (and 1803) release?

这是"按设计"吗？或者是一个错误？

Is this "by design" or a mistake?

除了可以帮助我们的注册表设置之外，还有其他解决方案吗？ 1703支持将于2018年秋季结束。

Is there any other solution than the registry setting that can help us out here? The 1703 support is ending fall 2018.

谢谢。

推荐答案

您好，

我们遇到了同样的问题，并且发现在1709中运行除Explorer之外的任何shell会导致触摸屏键盘没有出现。 我们只是尝试使用IE运行简单的自助服务终端设置，并且自从将我们的SOE升级到Windows的最新功能
更新后，我不得不完全重新设计解决方案。 我一直希望另一轮Windows更新可以解决这个问题，但似乎March CU也没有产生任何影响。

We are having the same issue and have found that running any shell other than Explorer in 1709 causes the touchscreen keyboard to not appear.  We are just trying to run a simple kiosk setup using IE and since upgrading our SOE to the latest feature update of Windows, I'm having to re-engineer the solution entirely.  I've been hoping that another round of Windows updates may resolve the issue, but it seems that the March CU hasn't made a difference either.

我尝试过使用内置的ShellLauncher功能，但它也有同样的陷阱。 我现在正在考虑使用指定的访问功能和来自Windows应用商店的名为Kiosk SP浏览器的应用程序。 但是在开始时它看起来像是一个
更多的人工干预来设置，因为我想尽可能多地使用组策略和脚本在必要时进行标准化，所以这只是成像机器和放入正确的OU。

I've tried using the inbuilt ShellLauncher feature, but it suffers from the same pitfalls.  I'm now looking at toying with the assigned access feature and an app from the Windows Store called Kiosk SP browser.  But at the outset it looks like a bit more manual intervention to get set up as I'd like to have as much as I can standardized using Group Policy and scripting where necessary so it's just a matter of imaging a machine and dropping into the right OU.

有没有人对如何解决这个烦人的键盘问题有任何建议？ 我已经尝试了除了其他一些以外的所有各种注册表设置，但没有运气。 任何反馈或建议都会非常感激。  

Does anyone have any suggestions on how to get around this or found a solution to this annoying keyboard issue?  I've tried all of the various registry settings as above in addition to some others, but no luck.  Any feedback or suggestions would be much appreciated.  

谢谢

***更新***

已分配的访问方案已经过测试，但也无效！

The assigned access scenario has been tested and doesn't work either!

这篇关于屏幕键盘在自定义外壳程序，Windows 10 Pro 1709和1803中不起作用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！