# A JoSIM®-Pro netlist cannot find an included file

Check the .include reference and preserve the files used by the project. The installed AND example requires base_cells.cir alongside the main example.

## Compatibility

2.9.0 release target; current-source Windows candidate evidence

Published guidance with release-applicability limits. Confirm package applicability before following this guide.

## Check the missing file

1. Read the exact file or .include diagnostic and inspect the reference as written in the netlist.
2. Confirm that the included file exists at the intended location. Preserve nearby files when copying a project; use stable explicit relative references where appropriate.
3. In the GUI, use File > Open Folder... for a project that depends on nearby include files.
4. For AND_Example.cir, keep the installed base_cells.cir in the same example directory. Save a writable working copy and rerun after correcting the missing dependency.

## If the file can be found but the error remains

Distinguish a missing include from a subcircuit problem. Check matching .subckt/.ends boundaries, subcircuit names, the number of connection nodes and cyclic include/subcircuit relationships. Use the specific diagnostic rather than assuming all these errors have the same cause.

## A smaller starting point

Use JTL_Example.cir for the first simulation if you are still checking installation and licensing. The manual identifies it as self-contained.

## Checked command-line recovery

On a disposable working copy, omitting base_cells.cir caused an exit with a missing-file diagnostic and no CSV. Restoring the unchanged library recovered the run: 2,001 finite samples, four traces, 0–250 ps.

```text
josim-pro-cli -o recovered.csv AND_Example.cir
```

## Checked native GUI recovery

On a disposable AND example, the normal licensed GUI Run action rejected the missing base_cells.cir with a specific include diagnostic. Restoring the unchanged library beside AND_Example.cir and rerunning produced 2,001 finite samples across four traces over 0–250 ps. The source and library hashes were preserved.

This verifies the recorded production run/recovery actions on the Windows candidate. File > Open Folder picker interaction and the final package remain unchecked. The diagnostic screenshot was withheld because it contained a personal workspace path; useful path-free recovery imagery is still needed.

## Sources and verification details

Recorded inputs/builds only. Complete walkthrough and final-package acceptance remain separate.

- VAL-011: JoSIM-Pro 2.9.0 Windows review CLI, built 3 November 2026. Packaged AND/base_cells CLI run, missing-include rejection/restoration, main/include output-collision rejection and absolute-input resolution from another working directory CLI recovery and input/output integrity only. GUI recovery, numerical accuracy/convergence and final-package checks remain pending.
- VAL-016: JoSIM-Pro 2.9 current-source Windows candidate with matching freshly built runtime; not the final distributed package. Production GUI controls, normal licensed JTL and AND runs, missing-include restoration, exact input/output collision rejection and operator-assisted CSV/All traces export. Explicitly reopening saved JTL and rerunning also passed Automatic session restoration failed (KB-GUI-007). File opening was supplied at the production OpenFile boundary; folder-picker input, cancellation, retry, other export formats, physical accuracy and final-package acceptance remain unverified. CSV/CLI differences were at most one ULP in this example, not an accuracy or regression tolerance. The Clang-built runtime does not close the separate MSVC/OpenMP finding KB-BUILD-001. External Computer Use capture remains unqualified.


- josim-pro:docs/manual_source/sections/troubleshooting.tex: Input files, .include paths, and subcircuit boundaries
- josim-pro:docs/manual_source/sections/gui_quick_start.tex: Before starting
- owner:technical-review-20261102: JoSIM-Pro 2.9 chosen as the public starting path; release availability must be checked before publication
- validation:windows-workflows-20261103: VAL-011/VAL-012; exact route, runtime and evidence limits
- validation:josim-native-windows-20261103: VAL-016; exact native actions, independent output checks, operator Save and failed automatic-restoration boundary

- The earlier baseline timeout and later successful CLI recovery remain separately recorded; the original wait has no established cause.
- VAL-016 verifies scoped native missing-include rejection and restoration. Complete illustrated GUI guidance and final distributed-package checks remain pending.

## Related guides

- [Run the installed JTL example in JoSIM®-Pro](/knowledge-base/josim-first-jtl)
- [JoSIM®-Pro reports a licensing problem or degraded mode](/knowledge-base/josim-licensing-unavailable)
- [Find declarations, references and source locations](/knowledge-base/josim-editor-navigation)
- [Use completion, linked snippets and live diagnostics](/knowledge-base/josim-editor-completion)
- [Hand off an already fitted line model from external network data](/knowledge-base/sparameter-model-handoff)