diff --git a/user-guide/Reference/DataMiner_Tools/SLNetClientTest_tool/SLNetClientTest_tool_diagnostic_procedures.md b/user-guide/Reference/DataMiner_Tools/SLNetClientTest_tool/SLNetClientTest_tool_diagnostic_procedures.md
index 9d0a0f6df5..0784efd1dc 100644
--- a/user-guide/Reference/DataMiner_Tools/SLNetClientTest_tool/SLNetClientTest_tool_diagnostic_procedures.md
+++ b/user-guide/Reference/DataMiner_Tools/SLNetClientTest_tool/SLNetClientTest_tool_diagnostic_procedures.md
@@ -23,6 +23,7 @@ The procedures below can be used to retrieve data from a DataMiner System. Howev
 - [Inspecting the parameter notification queue](xref:SLNetClientTest_Inspecting_the_parameter_notification_queue)
 - [Inspecting the SLNet event subscriptions](xref:SLNetClientTest_viewing_connection_details)
 - [Inspecting the stack sizes in SLNet](xref:SLNetClientTest_Inspecting_the_stack_sizes_in_SLNet)
+- [Querying the assembly resolution hint paths](xref:SLNetClientTest_query_hint_paths)
 - [Requesting a list of active merge actions for a protocol](xref:SLNetClientTest_active_merge_actions_protocols)
 - [Requesting an estimate of the number of rows for a storage type in the database](xref:SLNetClientTest_estimate_number_rows_for_storage_type)
 - [Requesting information about pending incoming events](xref:SLNetClientTest_info_pending_incoming_events)
diff --git a/user-guide/Reference/DataMiner_Tools/SLNetClientTest_tool/SLNetClientTest_tool_diagnostic_procedures/SLNetClientTest_query_hint_paths.md b/user-guide/Reference/DataMiner_Tools/SLNetClientTest_tool/SLNetClientTest_tool_diagnostic_procedures/SLNetClientTest_query_hint_paths.md
new file mode 100644
index 0000000000..ed013eb121
--- /dev/null
+++ b/user-guide/Reference/DataMiner_Tools/SLNetClientTest_tool/SLNetClientTest_tool_diagnostic_procedures/SLNetClientTest_query_hint_paths.md
@@ -0,0 +1,18 @@
+---
+uid: SLNetClientTest_query_hint_paths
+---
+
+# Querying the assembly resolution hint paths
+
+To troubleshoot assembly resolution issues, from DataMiner 10.4.12/10.5.0 onwards, you can use the SLNetClientTest tool to query the hint paths used to look up QAction dependencies:
+
+1. [Connect to the DMA using the SLNetClientTest tool](xref:Connecting_to_a_DMA_with_the_SLNetClientTest_tool).
+
+1. In the *Diagnostics* menu, select *DMA* > *SLScripting AssemblyResolve HintPaths*.
+
+1. Go to the *Output* tab to view the current list of hint paths used by the DataMiner AssemblyResolveHelper.
+
+   If [multiple SLScripting processes are configured](xref:Configuration_of_DataMiner_processes), the output will show the hint paths for each process per process ID.
+
+> [!NOTE]
+> To help with the troubleshooting of assembly resolution issues, from DataMiner 10.4.12/10.5.0 onwards, an entry is also added in the *SLManagedScripting.txt* log file each time DataMiner has loaded or failed to load an assembly. This log entry will include both the requested version and the actual version of the assembly.
diff --git a/user-guide/Reference/toc.yml b/user-guide/Reference/toc.yml
index 13f214ab51..0b52230979 100644
--- a/user-guide/Reference/toc.yml
+++ b/user-guide/Reference/toc.yml
@@ -262,6 +262,8 @@ items:
                 topicUid: SLNetClientTest_viewing_connection_details
               - name: Inspecting the stack sizes in SLNet
                 topicUid: SLNetClientTest_Inspecting_the_stack_sizes_in_SLNet
+              - name: Querying the assembly resolution hint paths
+                topicUid: SLNetClientTest_query_hint_paths
               - name: Requesting a list of active merge actions for a protocol
                 topicUid: SLNetClientTest_active_merge_actions_protocols
               - name: Requesting an estimate of the number of rows for a storage type in the database