Hi @Chandana_Ramesh,

The FileNotFoundError you are seeing means the analyzer.exe binary is not present on disk at the expected path:

C:\Users\chandana.r\.databricks\labs\lakebridge\state\venv\lib\site-packages\databricks\labs\bladespector\Analyzer\Windows\analyzer.exe

Since reinstalling Lakebridge via the Databricks CLI did not restore the file, the most likely cause is that Windows Defender (or another antivirus/endpoint protection tool) is quarantining or deleting the binary immediately after installation. This is a documented scenario in the Lakebridge project (GitHub issue #1811).

STEPS TO RESOLVE

1. Check Windows Defender quarantine history:
- Open Windows Security > Virus and threat protection > Protection history
- Look for any entries that show analyzer.exe being quarantined or removed
- If found, restore the file from quarantine

2. Add an exclusion for the Lakebridge directory:
- Open Windows Security > Virus and threat protection > Manage settings
- Scroll to Exclusions > Add or remove exclusions
- Add a folder exclusion for:
C:\Users\chandana.r\.databricks\labs\lakebridge\

3. If your organization uses a centralized endpoint protection solution (CrowdStrike, Carbon Black, Symantec, etc.), you may need to request your IT/security team to whitelist that directory or the analyzer.exe binary specifically.

4. After adding the exclusion, reinstall Lakebridge:

databricks labs install lakebridge

5. Verify the binary is now present:

dir "C:\Users\chandana.r\.databricks\labs\lakebridge\state\venv\lib\site-packages\databricks\labs\bladespector\Analyzer\Windows\analyzer.exe"

6. Run the analyze command again:

databricks labs lakebridge analyze --debug

ADDITIONAL NOTES

- The analyzer binary is bundled inside the bladespector Python package. When you install Lakebridge, pip downloads the package and extracts the binary. If antivirus scans the extraction in real-time, the file can be removed before the process completes, which is why reinstalling alone does not fix it.
- Make sure you are running Python 3.10.1 through 3.13.x, as required by Lakebridge.
- The Lakebridge documentation and latest releases are available at:
https://databrickslabs.github.io/lakebridge/
https://github.com/databrickslabs/lakebridge

If none of the above resolves the issue, consider opening a GitHub issue at https://github.com/databrickslabs/lakebridge/issues with the full --debug output so the maintainers can assist further.

* This reply used an agent system I built to research and draft this response based on the wide set of documentation I have available and previous memory. I personally review the draft for any obvious issues and for monitoring system reliability and update it when I detect any drift, but there is still a small chance that something is inaccurate, especially if you are experimenting with brand new features.

If this answer resolves your question, could you mark it as "Accept as Solution"? That helps other users quickly find the correct fix.