# Calling Up the Windows On-Screen Keyboard from Perspective Session

**URL:** <https://forum.inductiveautomation.com/t/calling-up-the-windows-on-screen-keyboard-from-perspective-session/64959>\
**Category:** Ignition\
**Tags:** ignition81, scripting, perspective\
**Created:** [October 7, 2022, 5:20pm UTC](https://forum.inductiveautomation.com/t/calling-up-the-windows-on-screen-keyboard-from-perspective-session/64959 "2022-10-07T17:20:53Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Paul\_Holleger](https://avatars.discourse-cdn.com/v4/letter/p/eb9ed0/32.png) [@Paul\_Holleger](https://forum.inductiveautomation.com/u/Paul_Holleger)\
**Post date:** [October 7, 2022, 5:20pm UTC](https://forum.inductiveautomation.com/t/calling-up-the-windows-on-screen-keyboard-from-perspective-session/64959/1 "2022-10-07T17:20:53Z")

</div>

Hi all,

I'm working on user-logins for my current perspective project, and ran into a bit of a hurdle yesterday. I'm trying to allow users to login using an on-screen keyboard in kiosk mode, but perspective doesn't allow logins from anything other than their default login scheme. I made a login window like I would for vision, but there's no scripting options that work with perspective, so I need to use the default. However, I don't have access to the windows OSK unless I allow them access to the rest of windows, which is not acceptable.

So in talking with Ignition support, they recommended I create a bash file to call up the OSK with system.util.execute() . But I'm very unfamiliar with bash files.

So how would I go about calling up the windows OSK from perspective? It doesn't have to be with the method recommended, anything that works will do. Any ideas?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [October 7, 2022, 5:49pm UTC](https://forum.inductiveautomation.com/t/calling-up-the-windows-on-screen-keyboard-from-perspective-session/64959/2 "2022-10-07T17:49:11Z")

</div>

Support misled you. Perspective cannot run a bash file or any other local executable. (Except in the gateway itself.)

Vision can, because it runs locally.

(I'm not sure there's any solution at this time.)

---

<div class="post-metadata">

**Author:** ![Paul\_Holleger](https://avatars.discourse-cdn.com/v4/letter/p/eb9ed0/32.png) [@Paul\_Holleger](https://forum.inductiveautomation.com/u/Paul_Holleger)\
**Post date:** [October 7, 2022, 5:51pm UTC](https://forum.inductiveautomation.com/t/calling-up-the-windows-on-screen-keyboard-from-perspective-session/64959/3 "2022-10-07T17:51:32Z")

</div>

Oh dear. Then how am I supposed to login?!

---

<div class="post-metadata">

**Author:** ![bkarabinchak.psi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bkarabinchak.psi/32/83567_2.png) [@bkarabinchak.psi](https://forum.inductiveautomation.com/u/bkarabinchak.psi)\
**Post date:** [October 7, 2022, 5:51pm UTC](https://forum.inductiveautomation.com/t/calling-up-the-windows-on-screen-keyboard-from-perspective-session/64959/4 "2022-10-07T17:51:56Z")

</div>

Is the gateway on the same computer as the kiosk?

---

<div class="post-metadata">

**Author:** ![Paul\_Holleger](https://avatars.discourse-cdn.com/v4/letter/p/eb9ed0/32.png) [@Paul\_Holleger](https://forum.inductiveautomation.com/u/Paul_Holleger)\
**Post date:** [October 7, 2022, 5:52pm UTC](https://forum.inductiveautomation.com/t/calling-up-the-windows-on-screen-keyboard-from-perspective-session/64959/5 "2022-10-07T17:52:35Z")

</div>

It is not.

---

<div class="post-metadata">

**Author:** ![victordcq](https://avatars.discourse-cdn.com/v4/letter/v/f6c823/32.png) [@victordcq](https://forum.inductiveautomation.com/u/victordcq)\
**Post date:** [October 10, 2022, 7:09am UTC](https://forum.inductiveautomation.com/t/calling-up-the-windows-on-screen-keyboard-from-perspective-session/64959/6 "2022-10-10T07:09:39Z")

</div>

There should be ways to enable the osk even in kiosk mode... what windows is it?

---

<div class="post-metadata">

**Author:** ![Paul\_Holleger](https://avatars.discourse-cdn.com/v4/letter/p/eb9ed0/32.png) [@Paul\_Holleger](https://forum.inductiveautomation.com/u/Paul_Holleger)\
**Post date:** [October 10, 2022, 11:23am UTC](https://forum.inductiveautomation.com/t/calling-up-the-windows-on-screen-keyboard-from-perspective-session/64959/7 "2022-10-10T11:23:44Z")

</div>

It's Windows 10. What are the ways to enable it?

---

<div class="post-metadata">

**Author:** ![victordcq](https://avatars.discourse-cdn.com/v4/letter/v/f6c823/32.png) [@victordcq](https://forum.inductiveautomation.com/u/victordcq)\
**Post date:** [October 10, 2022, 11:40am UTC](https://forum.inductiveautomation.com/t/calling-up-the-windows-on-screen-keyboard-from-perspective-session/64959/8 "2022-10-10T11:40:19Z")

</div>

You need to add these reg entries

```auto
HKCU\Software\Microsoft\TabletTip\1.7\EnableDesktopModeAutoInvoke = 1
HKCU\Software\Microsoft\TabletTip\1.7\DisableNewKeyboardExperience = 1
HKCU\Software\Microsoft\windows\CurrentVersion\ImmersiveShell\TabletMode = 1

```

> **[On Screen Keyboard not working on Windows 10 Kiosk Mode(Assigned Access with...](https://learn.microsoft.com/en-us/answers/questions/119887/on-screen-keyboard-not-working-on-windows-10-kiosk.html)**
>
> Microsoft Q&A is the best place to get answers to all your technical questions on Microsoft products and services. Community. Forum.

> **[How to enable On-screen Keyboard in Kiosk mode in Windows 11/10](https://www.thewindowsclub.com/enable-on-screen-keyboard-in-kiosk-mode)**
>
> You can turn on or enable the On-screen Keyboard in Kiosk mode in Windows 11/10, by editing the Registry or during Setup. We show you how.

---

<div class="post-metadata">

**Author:** ![Paul\_Holleger](https://avatars.discourse-cdn.com/v4/letter/p/eb9ed0/32.png) [@Paul\_Holleger](https://forum.inductiveautomation.com/u/Paul_Holleger)\
**Post date:** [October 11, 2022, 5:45pm UTC](https://forum.inductiveautomation.com/t/calling-up-the-windows-on-screen-keyboard-from-perspective-session/64959/9 "2022-10-11T17:45:13Z")

</div>

OK, so that _kind of_ worked, but I had to use the second method (scheduling a task to write the registry entries on windows user login).

However, now I have a new problem. The keyboard is overzealous, and pops up whenever I click into ANY field. Numeric, dropdowns, text, it doesn't matter. It's really getting in the way. I'm not sure that this solution really works well for what I need. It's fine temporarily, but it can't be like this long-term.

---

<div class="post-metadata">

**Author:** ![victordcq](https://avatars.discourse-cdn.com/v4/letter/v/f6c823/32.png) [@victordcq](https://forum.inductiveautomation.com/u/victordcq)\
**Post date:** [October 12, 2022, 8:01am UTC](https://forum.inductiveautomation.com/t/calling-up-the-windows-on-screen-keyboard-from-perspective-session/64959/10 "2022-10-12T08:01:08Z")

</div>

> [@Paul\_Holleger](#):
>
> overzealous

Its not possible to not let it show up on "some" input fields...  
If you dont want those fields to be edited dont use input components

> [@Paul\_Holleger](#):
>
> dropdowns

For the dropdowns you probably have search enabled, disabling search should help i think
