> Source: [sk138252](https://support.checkpoint.com/results/sk/sk138252)

# sk138252 - Unable to see users in MUH agent when Secure Boot is enabled on Windows 10 or Windows Server 2016

| Property | Value |
|----------|-------|
| Solution ID | sk138252 |
| Date Created | 2018-11-01 |
| Last Modified | 2023-05-14 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Windows |
| Platform | Intel/PC |

## Symptoms

- * Unable to see users in MUH agent when Secure Boot is enabled on Windows 10 or Windows Server 2016.   

  **SECURE BOOT - ON (not working)**
  ![](https://sc1.checkpoint.com/sc//SolutionsStatics/NEW_SK_NOID1539689753311/11810160446.JPG)   

  **SECURE BOOT - OFF (working)**
  ![](https://sc1.checkpoint.com/sc//SolutionsStatics/sk138252/21810160448edited1811040727.jpg)
* The **%TEMP%\ia_client.log** file shows these errors:   

  \[ ...\]@Host\[DATE TIME\] \[UIPConf (NAC::IS::TD::Important)\] UIP::ConfigurationSet::ConfigurationSet: Configuration: UserTimeOutInterval: 600 MaximumNumberOfPortsPerUser: 900 TCPExcludedPorts: 1-9999 UDPExcludedPorts: 1-9999   
  \[ ...\]@Host\[DATE TIME\] \[UserManager (NAC::IS::TD::Events)\] NAC::CLIENT::MANAGER::UserManager::UserManager: Ct'or  
  \[ ...\]@Host\[DATE TIME\] \[UIPLib (NAC::IS::TD::Surprise)\] UIP::UserIdentificationByPort::startDriver: StartService failed **error code = 0x241**   
  \[ ...\]@Host\[DATE TIME\] \[UserManager (NAC::IS::TD::Surprise)\] NAC::CLIENT::MANAGER::UserManager::UserManager: driver wasn't started correctly   
  \[ ...\]@Host\[DATE TIME\] \[NAC_Manager (TD::Events)\] NAC::CLIENT::MANAGER::Manager::authenticateFinished: schedule first update used ports callback for 2 minutes

## Cause

Windows SecureBoot feature requires new capabilities such as device guard support for the drivers. Adding those is considered as an enhancement.

## Solution

This problem was fixed. The fix is included in:

* [**Check Point R80.40**](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk160736)

Check Point recommends to always [upgrade to the most recent version](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=overview&product=436).  

The issue is resolved by using Terminal Server Agent v2 (MUH2). For more information, see the [Identity Awareness Clients Administration Guide](https://sc1.checkpoint.com/documents/Identity_Awareness_Clients_Admin_Guide/Default.htm) \> section "Identity Agent for a Terminal Server".

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content