SWFileFixer
Find and repair reference defects across whole SolidWorks file collections.
- Commits
- 4
- Stars
- 0
- Created
- July 31, 2026
A scanner and repair tool for SOLIDWORKS file corpora. It walks a directory of parts, assemblies and drawings looking for broken references, duplicate IDs, missing configurations, weldment profile problems and Toolbox defects, then reports what it found and repairs what it safely can.
The useful part is that scanning needs no SolidWorks install. It reads the files directly, so a defect sweep can run on a build server, on an archive drive, or on a machine that has never had a CAD licence. That matters when the corpus is thousands of files and opening each one by hand is not a plan.
What it does
Scans SOLIDWORKS file collections for:
- Broken file references (missing assemblies, missing parts)
- Duplicate ID conflicts within a file
- Missing or undefined configurations
- Weldment profile defects
- Toolbox component problems
Reports what it found, repairs what it safely can. Reports honestly when repair is not safe.
Small history, real tests
Four commits, launched 2026-07-31, narrow scope on purpose. This is a young tool still discovering which repair strategies hold and which edge cases trip them.
It is not an unexamined one: 13 test files and 278 test functions, measured on 2026-09-06 — the first time this repository was measured at all. Before that it appeared on the receipts page as not measured, which is a different thing from zero, and was never printed as zero.
Run it on a backup corpus first anyway. The conservative approach — repair only what is certain — means you do not lose data to an aggressive “fix”, and the tests do not change the advice.
Where this stands
Better at
- Scanning a corpus needs no SolidWorks install; runs on build servers, archive drives, or unlicensed machines.
- Batch scanning thousands of files for defects without manual intervention or per-file opening overhead.
- 13 test files and 278 test functions, measured for the first time on 2026-09-06. Four commits is a small history; it is not an untested one.
Worse at
- Four commits of history. The scope is narrow on purpose and the repair strategies are still being validated against real corpora.
- Conservative repair approach: only repairs defects that can be safely fixed; cannot handle all failure modes.
Pick something else when…
- SOLIDWORKS itself, on a licensed seatThe fix needs the modeler to resolve it, or you need vendor-supported behaviour you can escalate.
- A copy of the corpus, and patienceThe files are irreplaceable. Point any repair tool at a duplicate before you point it at the only copy you have.