Record the release
Note the year, installer language, Windows version and previous installations. Distinguish a single-release failure from a general one.
Check Windows records
Capture installed-app entries before changing them. A missing folder does not imply a removed product record.
Preserve resources
Back up custom families, templates and the add-in list. Prepare a model copy for testing.
Follow the log
Investigate the specific product or shared installer identified by the log. Create a test project after setup.
What to prepare for support
A clear description helps select the next check before connecting. Send the product year, Windows version and full error screenshot with personal details hidden. For a file issue, say whether other projects behave the same way.
- What happened immediately before the fault?
- Does it affect one project or the whole application?
- Which steps have you already tried, and what changed?
We agree the scope and cost before an AnyDesk or RuDesktop session. You keep control of the connection and enter account credentials yourself.
Describe the problem ↗Technical reference
Product requirements and repair procedures vary by release. This guide explains initial checks; use the vendor instructions for your exact environment.
