InvestigAItor

Troubleshooting

Common issues and solutions when deploying or using the InvestigAItor extension.

Extension not appearing after GPO update

Run gpresult /ron the target machine to verify the GPO is applied. Look for your GPO name under “Applied Group Policy Objects.” If it's missing, check that the GPO is linked to the correct OU and that the machine's computer account is within that OU. After confirming, restart Chrome completely.

Extension installed but not enrolled

The extension is installed but shows the enrollment form instead of monitoring. This means the managed config with the enrollment key is not being applied.

  • Open chrome://policy and check that setupToken has a value under the extension's managed storage
  • Verify the setup token matches what is shown in Settings → General in the admin dashboard
  • If using GPO, check that registry values exist under HKLM\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\<extension-id>\policy
  • Restart Chrome completely after setting registry values (close all Chrome processes)

Registry values not appearing in chrome://policy

Registry value names are case-sensitive. They must match the exact camelCase names from the extension's managed schema:

  • setupToken (not setuptoken or SetupToken)
  • deviceName (not devicename or DeviceName)
  • userName (not username or UserName)

If the names don't match exactly, Chrome silently ignores the values and they won't appear on chrome://policy.

userName not working via GPO

%USERNAME% does not expand in HKLM registry values set via GPO Computer Configuration because they run in SYSTEM context. Use a GPO logon scriptinstead:

reg add "HKLM\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\ncibbcpcjhieaffkncaeemcfihlhkcdg\policy" /v userName /t REG_SZ /d %USERNAME% /f

Deploy this as a logon script via User Configuration → Policies → Windows Settings → Scripts → Logon. The logon script runs as the logged-in user, so %USERNAME% expands correctly.

CRX_REQUIRED_PROOF_MISSING

This error means Chrome is rejecting the self-hosted CRX file. It only occurs on unmanaged devices (not domain-joined or MDM-managed). Self-hosted CRX deployment requires the device to be managed via GPO, Intune, JAMF, or Google Workspace.

For unmanaged devices, use the Chrome Web Store or Edge Add-ons store listing instead, or install manually via developer mode for testing.

Device not appearing in dashboard

  • Verify the machine has internet access to api.investigaitor.org
  • Check that the enrollment key is correct and the subscription is active
  • Open the extension popup and look for error messages
  • Check chrome://extensions for any extension errors

Extension disabled by Chrome

Chrome periodically disables sideloaded extensions on unmanaged devices and shows a “Developer mode extensions” warning. This is expected behavior for manually installed extensions.

For production deployment, use GPO, Intune, or JAMF force-install. Extensions installed via enterprise policy cannot be disabled by users or by Chrome.

AI events not appearing

  • Visit a monitored AI platform (e.g. chatgpt.com, claude.ai) and wait a few seconds
  • Check the Activity page in the admin dashboard with no filters applied
  • Verify the platform is enabled in Governance and AI Catalog
  • Check that the device status shows “Online” on the Devices page

PII detection not working

  • PII detection only runs on monitored AI platform pages, not all websites
  • Type or paste test data (e.g. a fake credit card number like 4111 1111 1111 1111) into an AI prompt field
  • Check that custom patterns are enabled in Governance and PII & Detection
  • Detection runs on-device. The extension must be enrolled and have received its policy config

Training banner not showing

  • The extension checks for training assignments every 60 minutes
  • Admin-triggered reminders (Send Reminder button) appear on the user's active tab on the next poll
  • The banner only shows once per reminder. If dismissed, it won't reappear until a new reminder is sent or the cadence timer fires again

Policies not updating on devices

The extension syncs policies every 5 minutes. If you made a change in the dashboard and it hasn't taken effect:

  • Wait 5 minutes for the next sync cycle
  • Or close and reopen Chrome to trigger an immediate sync
  • Check chrome://extensions to ensure the extension is active (not errored)

Managed config not applying via Intune

  • In Intune, go to the device record and check Device configuration status
  • Ensure the profile targets the correct device group
  • On the device, run chrome://policy to verify the policies are applied
  • Intune policy delivery can take up to 8 hours. Force a sync from the Intune portal or from the device's Company Portal app

JAMF profile not applying

  • Run sudo jamf recon on the Mac to force a check-in
  • In JAMF Pro, check the device record under Management and Configuration Profiles
  • Verify the preference domain is com.google.Chrome (or com.microsoft.Edge for Edge)
  • Restart Chrome after the profile is applied

Still need help?

Contact us at [email protected] with your organization name and a description of the issue. Include screenshots of chrome://policy and chrome://extensions if relevant.