1. Steps to reproduce:

• Launch VS Code with the Qt Core extension (qt-core) installed.
• On startup, the extension scans for local Qt kits.
• It automatically writes an entry into settings.json under "qt-core.additionalQtPaths", with a name suffixed _from_PATH and using uppercase qtpaths.EXE, for example:
       

  "qt-core.additionalQtPaths": [
      {          
          "name": "Qt-6.8.3-win32-msvc_from_PATH",          
          "path": "D:\\Program_Files\\QT\\6.8.3\\msvc2022_64\\bin\\qtpaths.EXE" 
      }
  ]
      

2. Actual behavior:

• After this entry is written, an error appears:
  output log

       The specified additional Qt installation 'D:\Program_Files\QT\6.8.3\msvc2022_64\bin\qtpaths.EXE' does not point to qtpaths nor qmake.

3. Observed output log:

4. Root cause:

• The extension uses an uppercase .EXE extension (qtpaths.EXE) when writing the path, which fails the recognition check that expects lowercase filenames (qtpaths or qmake).
• Since this entry is automatically generated by the extension, such behavior should not occur.

5. Workaround:

• Manually editing settings.json to change "qtpaths.EXE" to "qtpaths.exe" (all lowercase) resolves the issue.
• While this does not block functionality, it is a bug that should be addressed.

6. Additional context:

• This is not a critical blocker, but is an unexpected behavior that should be corrected for better user experience.