Downgrade err msg about resolving AHK v2 interpreter

changelog.md

@@ -2,8 +2,12 @@
 
 ## 6.4.1 - unreleased 🛠️
 
--   Fix go to definition in AHK v1 files ([#559](https://github.com/mark-wiemer-org/ahkpp/issues/559))
 -   Add [troubleshooting guide](docs/Troubleshooting.md)
+-   Fix go to definition in AHK v1 files ([#559](https://github.com/mark-wiemer-org/ahkpp/issues/559))
+-   Remove unnecessary error message "Couldn't resolve AHK v2 interpreter" ([#493](https://github.com/mark-wiemer-org/ahkpp/issues/493))
+    -   This has been moved to a console log visible in the AHK++ (v2) output channel
+    -   A similar error message will still appear when attempting to debug with an unrecognized interpreter path
+    -   See the new [troubleshooting guide](docs/Troubleshooting.md) for details
 
 ## 6.4.0 - 2024-11-02 🗳️
 

docs/Troubleshooting.md

@@ -2,6 +2,20 @@
 
 If AHK++ isn't behaving as you expect, here are some things you can try.
 
+## AHK v2: Validate your interpreter
+
+For AHK v2, the language server may not behave correctly if it fails to identify a valid path to an interpreter like `AutoHotkey.exe`. The status bar at the bottom left of your IDE should show the current interpreter or an option to "Select AHK v2 Interpreter".
+
+Currently, AHK++ does not support the Windows Store edition of AHK v2, but there are plans to support it by the end of 2024, ref [#496](https://github.com/mark-wiemer-org/ahkpp/issues/496).
+
+Interpreter found:
+
+![AHK v2 interpreter version and path](../image/ahkV2InterpreterAndPath.png)
+
+Interpreter not found:
+
+![Select AHK v2 Interpreter in status bar](../image/selectAHKV2Interpreter.png)
+
 ## Restart extensions
 
 Some settings changes only take effect after restart. Other issues may arise that are mitigated with a restart.