Windows CPB Not Showing Updated Settings or Software?
Use this article when a Windows Computer Panic Button (CPB) workstation still shows an old hotkey, incident button, location assignment or software version after a change was expected.
Applies to Windows computers only. The Mac version of CPB works differently, so the update and troubleshooting steps may differ. If you use a Mac, contact 911Cellular Support for instructions specific to your version.
Settings changes versus software updates
Settings changes affect how CPB operates—for example, its activation shortcut, incident buttons, assigned location or panic enablement.
Software updates change the installed CPB application version. A settings change does not necessarily require a software update, and receiving new settings does not confirm that a new software version has installed.
How settings changes are applied
When Windows CPB starts, it connects to the configured server and retrieves organization settings. The client also supports remote updates for certain settings:
- Activation shortcut: Organization hotkey changes can be pushed remotely. If no panic is active, the client relaunches to register the new shortcut.
- Incident buttons and workstation assignments: The client can receive real-time updates when these settings change.
- Panic enablement: Remote changes update the Windows tray tooltip and whether the client allows panic submission.
The Windows fallback shortcut is Alt+Backspace when no valid organization-specific shortcut is returned. Your organization may use a different shortcut.
How software updates are applied
Windows CPB supports remote software-update scheduling. Your IT administrator or 911Cellular Support should confirm the expected software version and the installation steps for your deployment.
Do not assume that restarting CPB or receiving updated settings confirms that a software update has completed.
Troubleshoot a missing update
1. Identify what has not changed
Record the expected change and what the workstation currently shows.
Examples include:
- The previous activation shortcut still applies.
- An incident button is missing or still displays its previous configuration.
- The workstation shows an unexpected location.
- The installed software version does not match the expected version.
Include when the change was made and whether it affects one workstation or several.
2. Ask your administrator to verify the configuration
Your administrator should confirm that:
- The change was saved for the correct organization or workstation.
- The workstation is registered under the correct organization.
- CPB is enabled where expected.
- The workstation has the intended security zone assignment.
- Any location-lock setting matches the intended workstation location.
- The expected software version applies to that workstation’s deployment.
3. Contact IT or 911Cellular Support if the issue continues
Provide:
- The affected computer name.
- The installed CPB version and Windows version.
- The expected setting or software version.
- When the change was made.
- Whether one or multiple workstations are affected.
- Any error messages or relevant screenshots.
The Windows client supports remote log-upload requests. Support can determine whether logs are needed and provide collection instructions.
Only delete local CPB application data, uninstall or reinstall the application when directed by your IT administrator or 911Cellular Support.
4. Verify the result
After the change is applied, confirm the specific issue is resolved:
- Settings change: The workstation reflects the intended shortcut, incident buttons, location or enablement.
- Software update: The installed CPB version matches the version confirmed by IT or Support.
Coordinate any panic activation test with your organization’s designated administrator or safety team before triggering CPB.
If the issue remains unresolved
Reply to the existing support ticket with the current result, any new error messages and the steps already completed. Include whether the issue is unchanged or behaves differently after troubleshooting.