The tables below summarise Microsoft Windows, FireDaemon Zero, and FireDaemon ZeroInput operating system kernel compatibility and supported deployment combinations and limitations. Not all Windows operating system versions are supported. Please also review:
- FireDaemon Zero Compatibility and Support Matrix
- FireDaemon ZeroInput Compatibility and Support Matrix
- FireDaemon Zero Release Notes
- FireDaemon ZeroInput Release Notes
ZeroInput and Windows Kernel Compatibility
Kernel updates to Microsoft Windows may cause the ZeroInput driver to be unable to do its job, which means you will not be able to see the contents of the Session 0 desktop when switching to Session 0 via FireDaemon Zero.
| ZeroInput Version | Windows Kernel Version | Status | Last Tested |
|---|---|---|---|
| 0.0.0.5 | Windows 10 22H2 19045.5247 | Compatible | 17 December 2024 |
| 0.0.0.7 | Windows 11 23H2 22631.4460 | Compatible | 17 December 2024 |
| 0.0.0.7 | Windows 11 23H2 22631.4602 | Incompatible (1) | 17 December 2024 |
| 0.0.0.7 | Windows 11 24H2 26100.2605 | Incompatible (2) | 17 December 2024 |
| 0.0.0.4 | Windows Server 2016 1607 14393.7606 | Compatible | 17 December 2024 |
| 0.0.0.4 | Windows Server 2019 1809 17763.6659 | Compatible | 17 December 2024 |
| 0.0.0.7 | Windows Server 2022 21H2 20348.2966 | Compatible | 17 December 2024 |
| 0.0.0.7 | Windows Server 2025 24H2 26100.2605 | Incompatible (2) | 17 December 2024 |
- Session 0 functionality is limited. Due to Windows Update KB5048685, the keyboard and (possibly) mouse do not appear to work on Session 0. Remove the update to restore keyboard and mouse functionality.
- Viewing the Session 0 desktop is not possible. The ZeroInput driver cannot patch win32kfull.sys due to removed or relocated win32kfull.sys entry points.
Zero and ZeroInput Deployment Matrix
| Windows Operating System Version | Is FireDaemon Zero compatible? | Is the UI0Detect Service present? | Should I deploy FireDaemon Zero? | Do I need to create the UI0Detect Service? | Should I deploy FireDaemon ZeroInput? | Are Interactive FireDaemon Pro Services visible on Session 0? | Are Interactive Windows Services visible on Session 0? | Is Access to Session 0 via RDP Permitted? |
|---|---|---|---|---|---|---|---|---|
| Windows Vista | No | Yes | No | No | No | Yes | Yes | Yes |
| Server 2008 | No | Yes | No | No | No | Yes | Yes | Yes |
| Windows 7 | Yes | Yes | Yes | No | No | Yes | Yes | Yes |
| Server 2008 R2 | Yes | Yes | Yes | No | No | Yes | Yes | Yes |
| Windows 8 | Yes | Yes | Yes | No | No | Yes | Yes | Yes |
| Server 2012 | Yes | Yes | Yes | No | No | Yes | Yes | Yes |
| Windows 8.1 | Yes | Yes | Yes | No | No | Yes | Yes | Yes |
| Server 2012 R2 | Yes | Yes | Yes | No | No | Yes | Yes | Yes |
| Windows 10 < 1803 (1) | Yes | Yes | Yes | No | Yes (4) | Yes | Yes | Yes |
| Windows 10 >= 1803 (1,2) | Yes | No | Yes | No (3) | Yes (4,5) | Yes | No | No (7) |
| Windows 11 <= 23H2 (2)(10) | Yes | No | Yes | No (3) | Yes (6)(10) | Yes | No | No (7) |
| Windows 11 24H2 (2) | No | No | No | No | No | No | No | No |
| Server 2016 | Yes | Yes | Yes | No | Yes (4) | Yes | Yes | Yes |
| Server 2019 (2) | Yes | No | Yes | No (3) | Yes (4) | Yes | No | Yes (8) |
| Server 2022 (2) | Yes | No | Yes | No (3) | Yes (5,6) | Yes (9) | No | No (7) |
| Server 2025 (2) | No | No | No | No | No | No | No | No |
| All Other Server Versions | No | No | No | No | No | No | No | No |
- The Interactive Services Detection Service (UI0Detect) is preserved if FireDaemon Zero was deployed on Windows 10 1709 or earlier, which is then upgraded to Windows 10 1803 or later
- The Interactive Services Detection Service (UI0Detect) has been removed from Windows 10 1803 or later, Windows 11, Server 2019, Server 2022, and Server 2025
- The FireDaemon Zero installer will create the UI0Detect service for you
- Deploy FireDaemon ZeroInput 0.0.0.4 (For <= Windows 10 1809, Server 2016, Server 2019)
- Deploy FireDaemon ZeroInput 0.0.0.5 (For >= Windows 10 1903, Server 2022)
- Deploy FireDaemon ZeroInput 0.0.0.7 (For <= Windows 11 23H2, Server 2022)
- Access to Session 0 via RDP is prohibited and does not work. Your RDP session will freeze. You must use another third-party remote control software, such as TeamViewer or TSPlus, that provides direct access to the Windows console session to gain remote access to Session 0. Alternatively, you can gain access to Session 0 via the physical or virtual machine console (e.g. via VMware Remote Console - VMRC)
- You can switch to Session 0 without restriction. However, when you switch back from Session 0, you will be returned to the Windows logon screen rather than your user desktop.
- Enable Legacy Console Mode to see console-based programs running on Session 0 when using TeamViewer for remote control.
- KB5048685 blocks keyboard and mouse input on Session 0 on Windows 11 23H2. To continue using your keyboard and mouse on Session 0, you will need to uninstall this security update.