How do I start the On Screen Keyboard in 64-bit Windows?

File System Redirection with Secure Desktop 10, 11 and 12

When a 32-bit application tries to launch osk.exe, Windows file system redirection automatically sends it to the 32-bit version in C:\Windows\SysWOW64\osk.exe.

However, the real/full-featured On-Screen Keyboard is the 64-bit version located in C:\Windows\System32\osk.exe.

Use this for the App Command Line

C:\Windows\Sysnative\cmd.exe /c start osk.exe

App Command Line break down:

• C:\Windows\Sysnative\cmd.exe
  Launches the 64-bit version of Command Prompt
• /c
  Tells cmd.exe to execute the following command then close itself immediately
• start
  Windows command that launches a program in a new process
• osk.exe
  The On-Screen Keyboard executable

Use this for the App Folder

C:\Windows\SysNative\

Secure Desktop 13

Secure Desktop 13 is a 64-bit application, so the App Command Line should be:

C:\Windows\System32\osk.exe

Should I purchase Secure Desktop 10, 11, 12 or 13?

If you wish to purchase Secure Desktop to

• Use with Windows XP, 7 or 8:
  • Secure Desktop 10 is the correct version.
• Use with Windows 10:
  • Secure Desktop 10, 11 or 12 is the correct version.
• Use with Windows 11:
  • Secure Desktop 11, 12 or 13 is the correct version.

If you wish to purchase Secure Desktop and

• Have configuration file compatibility with Secure Desktop 7, 8, 10 or 11:
  • Secure Desktop 10 or 11 is the correct version.
• Continue generating audit files in XML format:
  • Secure Desktop 10 or 11 is the correct version.
• Continue using a version of Secure Desktop that is feature frozen:
  • Secure Desktop 10, 11 or 12 is the correct version.

If you wish to purchase Secure Desktop with Windows 10 or 11 and

• Have the configuration stored in the registry:
  • Secure Desktop 12 is the correct version.
• Save audit data in CSV format or in the Windows Event Log:
  • Secure Desktop 12 is the correct version.

If you wish to purchase Secure Desktop with Windows 11 only and you are not already using Secure Desktop 12, then

• Secure Desktop 13 is the correct version.
• Secure Desktop 13.00 and 12.54 are 99% the same user interface and feature list.

If you have had configuration issues related to Secure Desktop 11 or 12 being a 32-bit application running in 64-bit Windows 11, then

• Secure Desktop 13 is the correct version.

Why move to Windows 10 or Windows 11?

• Windows 7 will become more susceptible to exploitation due to lack of security updates and the discovery of new vulnerabilities. Microsoft and other industry professionals strongly recommend upgrading computer systems to an actively supported operating system. Continuing to use any operating system within an enterprise beyond the end of life status may provide cyber criminals access into computer systems.
• Cyber actors continue to find entry points into legacy Windows operating systems and leverage Remote Desktop Protocol (RDP) exploits.
• Read the Joint Cybersecurity Advisory about the unauthorized access to a SCADA system at a drinking water treatment plant on February 5th, 2021.
• us-cert.cisa.gov

Problem with SnippingTool.exe (Secure Desktop 10, 11 or 12)

• sDesktop.exe (Secure Desktop Shell) is a 32bit application.
• 64-Bit Windows does what's called "File System Virtualization" for certain folders, including the System32 folder.
• The Virtualization swaps the contents of the
  • C:\windows\system32
  • and
  • C:\windows\syswow64
• folders depending on if the calling application is 32-bit or 64-bit.
• To launch the SnippingTool.exe from Secure Desktop, manually type the following string into the Command field for an icon:
  • C:\Windows\Sysnative\SnippingTool.exe
• If using Windows 11, consider upgrading to Secure Desktop 13 (64-bit).

Enable/Disable USB does not work.

• In Windows XP, 7 and 8 this Secure Desktop feature works by renaming 2 files in the Windows/Inf folder and a registry setting
• If the Windows folder or the Windows/Inf folder has the wrong folder ownership, this may not work correctly
• There is an alternate method in Windows 7, 8 and 10
  • To disable USB, open the Local Group Policy Editor (GPEdit.msc) and navigate to:
    • Local Computer Policy
    • Computer Configuration
    • Administrative Templates
    • System
    • Removable Storage Access
  • In the right pane, locate the following policies:
    • Removable Disks: Deny execute access
    • Removable Disks: Deny read access
    • Removable Disks: Deny write access
  • Set each of these policies to Enabled.
  • Restart the system for these policies to take effect.
  • Note: The Local Group Policy Editor is not available in Windows Home Edition.

The Supervisor password does not work.

• Check to see if Calculation Password is turned on for Supervisor
• Secure Desktop Tools | Administrator tab | Supervisor button | Calculation Passwords tab | Supervisor checkbox
• If the checkbox is not checked, the password should be straight up identical text
• If the checkbox is checked, the password is different than the password text
• Please read Secure Desktop documentation for more details

Is there a way to hide the universal time in the status bar of the Secure Desktop shell?

• If you are using Secure Desktop 8.xx, download a free upgrade to version 8.28
• https://visualautomation.com/download/sup828.exe
• If you are using Secure Desktop 10.xx, download a free upgrade to the latest version
• Secure Desktop Download
• Secure Desktop Tools | Secure Desktop tab | Option button | Icon tab | checkbox list | Hide Universal Time on Status Bar checkbox
• If you are not able to upgrade, you can hide the entire status bar
• Secure Desktop Tools | Secure Desktop tab | Option button | Icon tab | checkbox list | Hide Status Bar checkbox

Can there be a background image behind the Secure Desktop shell?

• Starting with version 8.10, Secure Desktop now has a wallpaper feature
• Secure Desktop Tools | Secure Desktop tab | Option button | Startup tab | Display Wallpaper when Secure Desktop is the Shell checkbox
• Secure Desktop Download

There is an error message: "Could not Set Attributes in C:\ProgramData\VisualAutomation\SecureDesktop\sdesktop.xml"

• sdesktop.xml is Secure Desktop's configuration file
• Secure Desktop sets the file attributes for this file to be read-only, hidden and system
• You may get this message when copying an sdesktop.xml file from one machine to another machine
• To resolve, simply clear all attributes for this file using File Explorer

Application XYZ works fine when Explorer is the shell, but not when Secure Desktop is the shell.

• Secure Desktop 11.60 and later has a new feature that may help with this issue:
  • Secure Desktop Tools | Secure Desktop tab | Option button | Autostart tab
• If using an older version than 11.60 of Secure Desktop, please keep reading
• Many software applications that are running in the background have a “stub” program that is started automatically by the Explorer shell
• Secure Desktop intentionally does not automatically start applications that the Explorer shell automatically starts
• Secure Desktop only starts applications automatically that are configured in the Secure Desktop Startup tab
• There are many registry locations where a “stub” application might be started by the Explorer shell
• The easiest way to find these locations and applications is to use a free utility from Microsoft named Autoruns:
• https://technet.microsoft.com/en-us/sysinternals/bb963902.aspx
• Once you have launched this utility, simply look for the “stub” application named similar to the name of XYZ application that you are using
• Once you have determined path and exe name of the application, simply configure Secure Desktop to start this application in the Startup tab
• Autoruns does not make any changes to your system, it simply reports which applications are configured to start automatically by the Explorer shell

Do you have a CD-ROM version of Secure Desktop that can be physically shipped?

• Visual Automation no longer ships physical CD-ROM disks
• Software delivery is an e-mail message for an order with software download information and serial numbers

Is there a free trial version of Secure Desktop?

• There is not a free trial version of Secure Desktop
• We do offer a 30 day evaluation period
• If our software does not meet your needs, you may ask for a refund within 30 days of the original purchase
• The easiest way to purchase Secure Desktop for evaluation is from our online Shopify store
• https://visual-automation.myshopify.com/
• Several different payment methods are available
• If Secure Desktop does not meet your needs, within 30 days, simply contact us and we will credit the payment method used

In 64-bit Windows, Windows Powershell is working correctly when Explorer is the shell, but not when Secure Desktop is the shell

• You might be running the 32-bit version of Powershell when Secure Desktop is the shell
• And the 64-bit version when Explorer is the shell
• The file paths to the 32-bit and 64-bit versions of Powershell are not intuitive
• 32-bit version: C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe
• 64-bit version: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

With Explorer as the shell, a file shortcut to a program works fine. But the same program in the Secure Desktop shell does not work

• With Explorer as the shell, open the properties of the file shortcut for the program
• Click on the Shortcut tab
• Look at the text for the "Target:" text field -- this same text should be in the "Command" field for a Secure Desktop icon
• Look at the text for the "Start In:" text field -- this same text should be in the "Directory" field for a Secure Desktop icon

Our online store, Shopify, offers convenient online ordering 24 hours a day, every day.

Secure Desktop 13 Data Sheet

Secure Desktop 13 Manual

Secure Utilities 13 Data Sheet

Secure Utilities 13 Manual

Secure Desktop 12 Data Sheet

Secure Desktop 12 Manual

Secure Utilities 12 Data Sheet

Secure Utilities 12 Manual

Secure Desktop 11 Data Sheet

Secure Desktop 11 Manual

Secure Utilities 11 Data Sheet

Secure Utilities 11 Manual

Secure Desktop 10 Manual

FAQ: Secure Desktop 10, 11, 12 or 13?