KYP Connect App Diagnostics

Updated
  • Updated on Sep 10, 2025
  • Published on Sep 10, 2025
  • 5 minute(s) read
Prev Next

Sometimes the KYP Connect App may not function as expected. For example, there might be a connection issue that causes data to be collected offline or, in some cases, not collected at all.

This guide will walk you through the steps to diagnose issues with the Connect App.

🔍 Step 1: Check the KYP Connect App Icon

The first step in troubleshooting should always be reviewing the KYP Connect App status icon.

  • ✅ Green – Collecting data
    Everything is working as expected.

  • ⚠️ Other statuses
    Data collection may be impacted. Please review the KYP Connect App Status Guide for a complete list of possible statuses and their meaning.

  • ❌ No icon displayed
    This indicates that the KYP Connect App did not start. In this case, review the logs:

    • Begin with the Supervisor log, which usually contains information on why the app failed to start.

    • If no clear cause is found, check the Updater log next to confirm whether the application components were installed or updated correctly.

🕒 Step 2: Check Task Scheduler

🔍 Open:
Start → Type task → Open Task Scheduler

📁 Under Task Scheduler Library, look for 3 main KYP-related tasks:

  • KypAdmin

  • KypPerfGuard

  • KypClient_[username]

  • ❌ Disabled? → Enable and run

  • ⏳ Ready? → Run the task manually

  • ✅ Running? → All good. Those tasks should be running at all times

🗂️ Step 3: Check KYP Files in Installation Directories

Verify all files are present in these directories:

  • C:\Program Files\kyp-client

  • C:\Users\Public\KypCache

  • C:\Users\[username]\AppData\Roaming\KypClient

If any of these folders are missing, KYP might not have been fully installed. In that case, continue with this guide to verify what is missing, or reinstall the application and check again afterward.

🛡️ Step 4: Ensure KYP is added to antivirus/firewall exceptions

Sometimes, certain KYP components may be blocked by antivirus or firewall software. It is very important to whitelist crucial components. Make sure the following processes are not blocked:

  • supervisor

  • javaw

  • KypClient

For the complete list of KYP components, please refer to the Antivirus Exceptions article.

📄 Step 5: Review Application Logs

When diagnosing issues with data collection or the Connect App itself, the application logs provide the most insight.

📌 Always check for ERR (error) or WARN (warning) entries in the log files. These typically indicate the root cause of the problem and should be reviewed first.

Logs can be found in the following locations:

  • User space logs (AppData):
    C:\Users\Your_username\AppData\Roaming\KypClient\logs

  • Admin space logs (Public folder):
    C:\Users\Public\KypCache\logs

The default log level is ERROR, which provides information only about errors in the application logs. Please change it if the logs dont include any entries that might help you identify your issue. To learn about the log levels, please visit this article.

🗂️ Logs Overview

👤 User Space Components (AppData)

These components are responsible for collecting and processing data.

  • 🟢 Supervisor (supervisor.log)
    Supervises other user space components. Logs include health-check calls from them. If no data is being collected, check here to identify which component may have failed. Usually any errors here are important.

  • 🟠 Recorder (recorder.log)
    Captures user actions and screenshots. If data gaps appear and no functions are created in the Message to Function Mapper log, review this log to confirm whether the actions were recorded.

  • 🔵 Processor (processor.log)
    Processes the data collected by the recorder. If recorder logs show captured data but no functions appear in the mapper log, check here. It also records cases where insufficient disk space on the user’s machine causes data collection to stop.

  • 🟣 Message to Function Mapper (message-to-function-mapper.log)
    Converts recorder messages into functions. If there are gaps in the data, review this log during the missing period to see whether functions were generated.

  • 🟡 Function Publisher (function-publisher.log)
    Sends functions to the database. When the app is in offline mode (yellow icon), check this log to see why data is not being transmitted. A successful transmission should show a 200 response code: “Successfully sent 9c673a93-38df-4dc5-ad4d-4717fe33333b to server and received 200 “

🛠️ Admin Space Components (Public Folder)

These components manage the application, updates, and system-level monitoring.

  • ⬆️ Updater (updater.log)
    Installs user space components and updates the KYP Connect App. Check this log if user space components are missing or the application is not being updated.

  • 📂 Shell (shell.log)
    Main component that handles scheduled tasks and configuration updates. Review this log if KYP Connect tasks are not visible on the user system, or if other logs mention configuration issues.

  • 📊 Perfguard (perfguard.log)
    Monitors CPU usage by Connect App components. Check this log to verify whether the machine was running at a given time or if excessive CPU usage occurred.

  • 🧩 Extension Host (extension_host_mfjhecbpfpgaamljbngeepkpalfddabc.log)
    Stores information about the KYP browser extension. Review this log if there are issues with the extension.

  • 🚀 Bootstraper (bootstraper.log)
    Launches other admin components: Monitor, Updater, Activator. Check this log if any of those components fail to start correctly.

  • 🖥️ Monitor (monitor.log)
    Collects hardware metrics and system specifications. Check this log if there are issues with HM (hardware metrics) data collection.

  • 🌐 Activator (activator.log)
    Ensures proper configuration of the Chrome web browser. While generally not critical for investigations, this log can confirm whether browser-related issues exist

📋 Step 6: Check Windows Event Logs

📍 Navigate to:
Event Viewer → Applications and Services Logs → Microsoft → Windows → TaskScheduler → Operational

  • 🔍 Look for errors related to KypAdmin

  • ⚠️ Common error codes:

    • 2147943726 → Indicates a user permissions or policy issue

🔧 Examples

Here are some common scenarios to help guide log investigation:

  • Symptom: The KYP Connect App icon is missing.

    • Check: Supervisor log → Updater log. Look for any errors

    • Likely cause: The app failed to start or components were not installed correctly.

  • Symptom: Data gap in the data. Verify if you see the proper functions created during the missing data period.

    • Check: Message to Function mapper log  → Recorder log → Processor log

    • Likely cause: Recorder failed to capture actions, or Processor could not process due to low disk space.

  • Symptom: The app icon is yellow (offline mode).

    • Check: Function Publisher log. Check if the functions are receiving code 200.

    • Likely cause: Functions are being generated but not sent to the server (network issue, or database connection failure).

  • Symptom: KYP Connect App is not updated.

    • Check: Updater log. Check for any entries indicating version mismatch and update failures.

    • Likely cause: The update has failed, or the auto update was disabled for this user.

🔌 KYP Extension Diagnostics

If you are experiencing issues with the KYP Extension, please refer to the KYP Extension Diagnostics guide. It will help you gather the necessary information to identify the cause and work toward resolving the problem.

✅ Summary

  • Start diagnostics by checking the KYP Connect App status icon and the Task Scheduler.

  • Review user space logs (data collection and processing) and admin space logs (application management, updates, hardware monitoring).

  • Use the component-specific logs to narrow down the source of data gaps, offline collection, or update issues.