FireDaemon ZeroInput 0.0.0.7
Warning and Disclaimer
By downloading and installing FireDaemon ZeroInput you fully acknowledge that this software modifies your Windows operating system in order to restore functionality that Microsoft has intentionally removed. As such, you now assume all risks and FireDaemon Technologies Limited will not be liable for any losses or damages as a result. If you have any doubt whatsoever in regard to the usefulness or fitness for purpose of this driver then please, do not use it. Additionally, FireDaemon Technologies Limited provides no warranty that ZeroInput will continue to work correctly with any future update to Microsoft Windows 10, Windows 11, Server 2016, Server 2019, Server 2022, or any future Microsoft operating system.
TABLE OF CONTENTS
- Warning and Disclaimer
- What Is ZeroInput?
- What Does ZeroInput Cost?
- Operating System Compatibility
- Limitation #1: VBS HVCI Breaks ZeroInput
- Limitation #2: Access to Session 0 via RDP Doesn't Work Reliably
- Limitation #3: VMware Virtual Machine SVGA Driver Bug
- Limitation #4: Disable Secure Boot Before Installing ZeroInput
- Limitation #5: Disable Hyper-V Hypervisor Before Installing ZeroInput
- Limitation #6: ZeroInput does not work on ARM CPUs
- Step 1 - Install Windows and / or Patch and Backup
- Step 2 - Connect to the Administrative Console of your computer
- Step 3 - Download ZeroInput
- Step 4 - Install FireDaemon ZeroInput
- Step 5 - Install FireDaemon Zero
- Step 6 - Install / Re-install Virtualisation Tools
- Step 7 - Reboot and Confirm Installation is Successful
- Uninstalling FireDaemon ZeroInput
- Upgrading Windows (a.k.a. In Place Upgrade)
- Manual UI0Detect Service Installation
- Bugs? Issues? Feature Requests?
What Is ZeroInput?
With the release of Windows 10 and Server 2016, Microsoft decided to block keyboard and mouse input on Session 0. So if you have an interactive Windows service running on Session 0, your keyboard and mouse will not work and you will not be able to interact with your application. For more information please refer to our comprehensive discussion on the matter. Additionally, with the release of Windows 10 1803 and Server 2019, Microsoft decided to remove the Interactive Services Detection Service entirely from the operating system.
So, behold, we created FireDaemon ZeroInput. This is a digitally signed kernel-mode driver that restores the keyboard and mouse functionality on Session 0 on Windows 10, Windows 11, Server 2016, Server 2019, and Server 2022. The driver also removes the "blacked out" Session 0 desktop. FireDaemon Zero works with FireDaemon ZeroInput and detects that the driver is present and gives you the ability to remain on Session 0 indefinitely (normally you would be kicked out after 30 seconds).
What Does ZeroInput Cost?
It's free. Use at your own risk. Please read the Warning and Disclaimer above.
Operating System Compatibility
ZeroInput works on Windows 10, Windows 11, Server 2016, Server 2019, and Server 2022 only. It's not required to be deployed on any other version of Windows. Please see the Deployment Matrix which summarises when and where you should deploy FireDaemon Zero and ZeroInput.
Limitation #1: VBS HVCI Breaks ZeroInput
ZeroInput will not work if you enable VBS (Virtualization Based Security) HVCI (Hypervisor Enforced Code Integrity) on your machine. There's no workaround. This article describes how to disable VBS / HVCI.
Limitation #2: Access to Session 0 via RDP Doesn't Work Reliably
There are numerous limitations regarding remote access to Session 0 via RDP. Please ensure you carefully review the FireDaemon Zero release notes prior to deploying ZeroInput. Also review the Deployment Matrix.
Limitation #3: VMware Virtual Machine SVGA Driver Bug
If you are using Windows in a VMware virtual machine, then there is a bug in the VMware SVGA Helper Service that will cause your Windows desktop to fail when you switch to / from Session 0. Please see this article to resolve the problem.
Limitation #4: Disable Secure Boot Before Installing ZeroInput
If you have Secure Boot enabled, you will need to disable it prior to installing ZeroInput otherwise the driver will not load. To resolve, disable Secure Boot, reboot, install ZeroInput, enable Secure Boot and reboot one more time.
Limitation #5: Disable Hyper-V Hypervisor Before Installing ZeroInput
If you have the Hyper-V Hypervisor enabled (Control Panel -> Turn Windows features on or off -> Hyper-V Platform -> Hyper-V Hypervisor) you will need to turn it off. ZeroInput will not work if the host operating system is itself virtualised via Hyper-V. ZeroInput does work in guest virtual machines (i.e. those that have been virtualised with VMware ESXi, VMware Workstation, Oracle VirtualBox, Hyper-V Server, Azure, AWS, etc.).
Limitation #6: ZeroInput does not work on ARM CPUs
ZeroInput is designed to work with Windows Operating Systems deployed on Intel or AMD CPUs only.
Step 1 - Install Windows and / or Patch and Backup
- Install Windows 10, Windows 11, Server 2016, Server 2019, Server 2022
- Apply ALL Windows updates - everything
- Install your latest hypervisor support tools
- Ensure your operating system is fully backed up so that you can completely restore it.
Step 2 - Connect to the Administrative Console of your computer
FireDaemon ZeroInput is a kernel-mode driver. Windows requires you to install kernel-mode drivers on an "administrative console". Hence, you need to login to an "administrative console" prior to installation. The administrative console is defined as:
- The physical desktop computer, desktop, laptop, etc. to which a physical mouse and keyboard are connected
- The console session is available via a computer management gateway such as Dell iDRAC, HP ILO, or equivalent
- The virtual machine console session (i.e. the screen displayed when accessing the machine via VMware vSphere Client or equivalent)
- The Administrative RDP session. To connect to this session type at an elevated command prompt:
mstsc /v:<hostname> /admin
Step 3 - Download ZeroInput
|FireDaemon ZeroInput 0.0.0.4 + 0.0.0.5 + 0.0.0.7|
For Intel and AMD CPUs only
April 2023 - Free
The ZIP file contains:
ZeroInput 0.0.0.4 for
Windows 10 1809 or earlier (32-bit and 64-bit)
Server 2016 and 2019 (64-bit only)
ZeroInput 0.0.0.5 for
Windows 10 1903 or later (32-bit and 64-bit)
Server 2022 (64-bit only)
ZeroInput 0.0.0.7 for
Windows 11 (64-bit only)
Server 2022 (64-bit only)
Step 4 - Install FireDaemon ZeroInput
Please do the following:
- Review the Deployment Matrix
- Ensure you are logged in as a local or domain administrator
- Ensure you are connected to an administrative console per Step 2 above
- Unpack the downloaded ZIP file to a location of your choice
- Locate the architecture-specific ZIP files (i.e. x86 or x64) for your operating system and unpack the one you need
- Locate the file FDUI0Input.inf, right-click on it and select Install
- Confirm the various UAC confirmation prompts
- The driver will be installed and the corresponding FDUI0Input service will be created automatically
- You can install the 0.0.0.4 driver via an elevated command prompt on Server 2016 and Server 2019 as follows (n.b. you must specify the <PathToDriver>):
rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 132 <PathToDriver>\FDUI0Input.inf
- You can install the 0.0.0.5 and 0.0.0.7 drivers via an elevated command prompt on Windows 10 1903 or later as follows:
pnputil /add-driver FDUI0Input.inf /install
Step 5 - Install FireDaemon Zero
If you have Windows 10 1803 or later, Windows 11, Server 2019, or Server 2022 installed, the Interactive Services Detection Service (UI0Detect) binaries have been removed from the operating system. Hence, you must install FireDaemon Zero to allow you to switch your desktop to Session 0. This step is optional on Server 2016 - however, managing Session 0 without FireDaemon Zero is painful. FireDaemon Zero enables interactive services system-wide, updates the UI0Detect service to work with the Zero task tray applet plus gives you an easy way to switch back and forth between your logged-in user session and Session 0.
Step 6 - Install / Re-install Virtualisation Tools
If your operating system is virtualised, please install or completely uninstall and re-install the corresponding helper tools (e.g., VMware Tools, Virtualbox Guest Additions, etc.).
Step 7 - Reboot and Confirm Installation is Successful
Now reboot your computer. FireDaemon Zero is ZeroInput aware. You can query the running state of the ZeroInput driver by typing the following at an elevated command prompt after your computer has rebooted:
For FireDaemon Zero 2:
cd /d "C:\Program Files\FireDaemon Zero"
FDUI0Control query --fdui0input-state
For FireDaemon Zero 3:
cd /d "C:\Program Files\FireDaemon Zero"
FDUI0CLI query --fdui0input-state
You should see the following output similar to the following:
Input Driver Details
Driver state: running
Status: Desktop switched
You should now be able to switch your desktop to Session 0 and see your interactive FireDaemon Pro services running.
Uninstalling FireDaemon ZeroInput
Complete the following steps:
- Login as a local or domain administrator
- Open an elevated command prompt.
- At the command prompt type:
sc delete FDUI0Input
Then reboot your machine. This will ensure ZeroInput has been unloaded from memory. Note this does not delete the driver from the disk drive.
Upgrading Windows (a.k.a. In Place Upgrade)
Upgrading Windows from one version to the next is hazardous. We recommend you do not do this as the machine can be left in an unknown state and may be unreliable. We recommend that you install Windows from scratch, apply all Windows updates, and then deploy the latest version of FireDaemon software products. If you absolutely have to upgrade Windows (e.g. from Windows 10 to Windows 11) and have ZeroInput 0.0.0.5 or earlier installed, you will need to:
- Remove ZeroInput per the step above
- Upgrade your operating system
- Install the version of ZeroInput qualified for your new operating system version (e.g. ZeroInput 0.0.0.7 for Windows 11) per the instruction above from Step 1 through Step 7.
Manual UI0Detect Service Installation
Should you ever want to install the Interactive Services Detection Service (UI0Detect) manually follow these instructions. First, check to see if the UI0Detect service is present via the following command at an elevated command prompt. If the service does not exist you will get an "OpenService FAILED 1060" error.
sc query UI0Detect
To set up the Interactive Services Detection Service manually, do the following:
- Login in as a local or domain administrator
- Open an elevated command prompt.
- At the elevated command prompt type the following three commands to re-create the UI0Detect service.
sc create UI0Detect start= auto type= own type= interact error= severe binpath= "C:\Windows\System32\winver.exe"
sc sidtype UI0Detect unrestricted
sc privs UI0Detect SeTcbPrivilege/SeAssignPrimaryTokenPrivilege/SeIncreaseQuotaPrivilege/SeDebugPrivilege
Note: In the sc create command - we have used winver.exe in the binpath. This is a "stub". sc.exe won't create the service if you supply an invalid binpath. When you install FireDaemon Zero the binpath is updated. Alternately, and if you are feeling really brave, copy over the UI0Detect.exe binary from an earlier version of Windows 10 or Server 2016 to C:\Windows\System32. Then adjust the binpath to read "C:\Windows\System32\UI0Detect.exe". If you do this you will be able to start the UI0Detect service and you should be able to switch desktop to Session 0 via the legacy Interactive Services popup.
Bugs? Issues? Feature Requests?
Tell us what you think! All feedback is gratefully received!