With compiler path set properly still get error upon opening first .cr file

Describe the bug When I start VS Code and load in the Crystal file it give this error: " Crystal compiler not found. Some features can through errors" but I have Crystal in the Env. Variables so I cannot figure this out. Maybe this is why (1) does not work too. The syntax highlighting does work.

To Reproduce Steps to reproduce the behavior: I have crystal compiler installed and environmental path set for system and home. I have path in extension set properly. I have it blank for crystal since it is set in Env. Var. for system and home. If I put in the work crystal or the absolute path then I get three errors and nothing works....that is another bug I believe.

Expected behavior Not to get the subject warning.

Piece of Code N/A

Screenshots . THIS IS THE POP UP ERROR/WARNING . THIS IS MY EXTENSION SETTING PART 1 OF 2 , THIS IS MY EXTENSION SETTING PART 2 OF 2

Desktop (please complete the following information): OS: Windows 11 Pro, fully up to date Crystal version: Crystal 1.9.2 [1908c81] (2023-07-19); LLVM: 16.0.3; Default target: x86_64-pc-windows-msvc I have a native Crystal install, NOT WSL 1 or 2 running This plugin version: 0.8.4

Additional context Not sure but may be related this Issue/Bug report I just submitted before this one: https://github.com/crystal-lang-tools/vscode-crystal-lang/issues/176

crystal-lang-tools / vscode-crystal-lang

With compiler path set properly still get error upon opening first .cr file #177