Troubleshooting CCW v23 Controller Selection Crashes

CCW v23 can reach controller selection and open Global Variables without closing once the failing dependency or engineering component is identified and corrected. Repeated reinstallations are not a useful endpoint: this failure occurred in a new project with no user logic, and the specified Visual C++ replacement-and-repair sequence did not resolve it.

Failure boundary

The first task is to separate a project-logic fault from an engineering-environment fault. In the reported sequence, CCW v23 created a new project, accepted a controller selection, and then crashed when Global Variables was opened. No application logic had been entered. Controller selection causes CCW to load controller-specific editors, definitions, and supporting software components; opening the variable editor exercises more of that component chain.

Check 1: Create a new empty project, select the same controller, and open Global Variables. Expect either a repeatable crash at the same transition or a normally displayed variable editor. A repeat at the same point establishes an environment or controller-component failure before any logic is added.

Diagnostic record

Capture the crash report before changing installed packages again. A report generated from the displayed prompt can identify the module that stopped, while the CCW debug log records events leading to the failure. The reported default log location is C:\ProgramData\Rockwell\CCW.

1. Reproduce the failure once using the shortest known sequence: new project, controller selection, then Global Variables.
2. Generate the report offered by the crash dialog.
3. Open C:\ProgramData\Rockwell\CCW and identify the log updated at the reproduction time.
4. Record the CCW version as v23, the selected controller, the last successful screen, and the first failing action.
5. Preserve the report and log before uninstalling, repairing, or replacing runtimes.

Read from the end of the log backward and locate the first failure preceding shutdown. Record the named module, exception information, or component-loading failure exactly as displayed. Do not infer a package name from the crash location alone.

Check 2: Compare the log timestamp with the reproduction time. Expect a newly updated CCW log and a report tied to the same run. If neither artifact updates, verify that the crash prompt's report-generation action completed before proceeding.

Visual C++ runtime alignment

The term runtime alignment here means installing the x86 Visual C++ redistributable requested by the affected CCW component. An installed package can exist while the component still fails to load because architecture, package generation, or registration does not match what it requests.

One proposed compatibility sequence was to remove Microsoft Visual C++ 2015-2019 and run the Visual C++ 2017 x86 installer at ...\13.00.00-CCW-INT-Std-DVD\Redist\VCRedist_2017\vc_redist.x86.exe. That path identifies a particular installation-media layout; use it only when that file is present on the installation media. Preserve the crash artifacts first because package removal changes shared Windows runtime state.

1. Record the installed Visual C++ packages before changing them.
2. Uninstall Microsoft Visual C++ 2015-2019.
3. Run vc_redist.x86.exe from the stated VCRedist_2017 directory.
4. Restart Windows if the installer requests it.
5. Reproduce the empty-project test without adding logic.

This sequence did not resolve the reported installation. Treat it as one bounded compatibility test, not a reason to repeat runtime removal indefinitely.

Check 3: Return to the installed-programs list and expect the x86 runtime installation to appear without a failed installer status. Then select the controller and open Global Variables; expect the editor to remain open. If the crash repeats, retain the new log and advance to CCW repair.

CCW repair sequence

A CCW repair re-registers installed application components after the runtime change. Repair must follow runtime installation in this sequence; repairing first and then replacing a dependency can leave the repaired component pointing at a changed runtime environment.

1. Close CCW.
2. Open the Windows Add or remove programs settings page.
3. Select the installed CCW entry and start its repair operation.
4. Allow the repair to finish without opening the project concurrently.
5. Start CCW v23 and repeat the new-project controller-selection test.

A complete uninstall and reinstall had already been attempted several times without clearing this failure. Another identical reinstall adds little diagnostic value unless the log identifies a missing or damaged CCW file that repair cannot restore.

Check 4: Expect CCW v23 to start, accept the controller selection, and display Global Variables without the crash prompt. If it still closes, compare the pre-repair and post-repair logs. An unchanged first failure points away from simple installation-file damage.

Project and operating-system isolation

Use controlled substitutions to determine whether the failing boundary is the project, the selected controller component, or the Windows environment. Change one variable per test and preserve a separate log for each result.

1. Open a new empty project and repeat the original controller selection.
2. Open a known project in which a controller is already selected, then navigate directly to Global Variables.
3. If suitable test hardware definitions are available in CCW, repeat with another controller selection and record whether the editor opens.
4. Run the same CCW v23 workflow in a Windows 10 virtual machine only as an environment-isolation test.

A Windows 10 virtual machine bypassed some CCW v23 controller issues in another case, but that result does not identify the cause of this specific crash. If the same project and controller work in the virtual machine, compare installed runtimes, CCW components, and the failing module named in the host log. If both environments fail identically, focus on the project or controller-specific component rather than repeatedly rebuilding the host.

Check 5: Expect a test matrix with one result per project, controller selection, and operating system. The decisive reading is a single changed condition that changes the outcome from crash to an open Global Variables editor.

End-to-end commissioning verification

Passing one editor-opening test is not enough. Verify the complete offline engineering path that originally failed before connecting equipment or writing application logic.

1. Create a new project in CCW v23.
2. Select the required controller and confirm that CCW remains open.
3. Open Global Variables and expect the editor to display normally.
4. Create a test variable using valid project conventions, save the project, close CCW, and reopen it.
5. Confirm that the selected controller and saved variable remain present.
6. Repeat the controller-selection and variable-editor sequence once more while monitoring C:\ProgramData\Rockwell\CCW.

Check 6: Expect two consecutive runs with no crash prompt, a persistent controller selection, a persistent test variable, and no new fatal entry at the end of the CCW log. This is the final verification step.

FAQ