Scenario 1:
The registry entry for the DLP fcnm.exe process is missing, so fcnm.exe doesn't start on the endpoint that tracks the URL on Chromium-based browsers.

NOTE: Make sure that you back up the registry before you perform the following steps. 

1. Look for the following registry entry in the affected system:
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Google\Chrome\NativeMessagingHosts\com.mcafee.dlp_native_messaging_host  
   
   If the registry isn’t present, create a key com.mcafee.dlp_native_messaging_host under Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Google\Chrome\NativeMessagingHosts
    
2. Right-click the registry com.mcafee.dlp_native_messaging_host, and click New, String value. Name the string as (Default) and the value data as C:\Program Files\McAfee\DLP\Agent\native_messaging_manifest.json
   
   Verify if the C:\Program Files\McAfee\DLP\Agent\native_messaging_manifest.json file is present on the system. The native_messaging_manifest.json file must be present in the DLP installed folder.
    
3. Right-click the registry com.mcafee.dlp_native_messaging_host, click New, String value. Name the string as last and the value data as cealeengjcdcgnmdhongkljamkkhbigl.
   
   After the registry is created, it must be displayed as shown in the screenshot below:
   

Scenario 2:
Execution of fcnm.exe is blocked using the group policies for the browser.

1. Look for the following registry entry on the affected system:

2. If there’s a registry in GPO for NativeMessagingBlocklist, then allow the DLP by adding an entry in NativeMessagingAllowlist for DLP plugin in GPO.