Key Registry — Think Cell License

Run as Administrator:

REG ADD "HKLM\SOFTWARE\Think-Cell\License" /v Key /t REG_SZ /d "TC7F-1A2B-3C4D-5E6F-789G-H0IJ" /f

Cause: The registry permissions are corrupted, or the key was entered under the wrong user hive (e.g., HKEY_CURRENT_USER instead of HKEY_LOCAL_MACHINE).

Fix:

For new deployments, do not rely on end users entering keys. Pre-configure the HKLM\SOFTWARE\think-cell\License\LicenseKey value during your imaging process. It saves helpdesk tickets, ensures compliance, and makes license audits painless.

Have a tricky think-cell deployment scenario? Share it in the comments below, and I’ll show you the registry fix.

To manage think-cell license keys at scale, you can bypass the manual activation prompt by deploying the key directly through the Windows Registry. think-cell stores its license and core settings in a specific hive that differs slightly depending on whether the installation is per-user or per-machine. Primary Registry Path

The license key is stored as a string value in the following location: Software\Classes\Software\think-cell Value Name: Value Type: think-cell HKLM vs. HKCU

Depending on your deployment strategy, you should place the key in one of two hives: Per-Machine (All Users): HKEY_LOCAL_MACHINE\Software\Classes\Software\think-cell think cell license key registry

Use this for central deployments where all users on a device share the same key. Per-User (Current User): HKEY_CURRENT_USER\Software\Classes\Software\think-cell

Use this for individual installations where the user does not have administrator privileges. think-cell Automated Deployment Methods

For IT administrators, there are three primary ways to push this key: Group Policy (GPO): Group Policy registry preference items to push the value to either the Computer or User configuration. Intune / MDM: You can deploy the MSI with silent arguments ( ) and push the license key via imported ADMX templates or a PowerShell script using Set-ItemProperty Command Line / Scripting:

Run the following command from an elevated prompt for a machine-wide update:

REG ADD "HKLM\Software\Classes\Software\think-cell" /v license /t REG_SZ /d "YOUR-LICENSE-KEY" /f think-cell Troubleshooting License Prompts

If the license window still appears after you've applied the registry key, check the following: Permissions:

Ensure the user has "Read" access to the registry key. If the installation was per-user, check that they can modify files in %APPDATA%\think-cell Conflicts: If both HKLM and HKCU keys exist, the value typically takes precedence. XML Settings: think-cell also maintains a settings.xml %LOCALAPPDATA%\think-cell Cause: The registry permissions are corrupted, or the

. If you are seeing persistent issues, verify the configuration in this file. think-cell Are you looking to automate this across a specific number of seats , or are you troubleshooting a deployment failure on a single machine? KB0010: The think-cell license key window pops up

The think-cell license key and associated settings (such as automatic updates and quality assurance) are stored in the Windows Registry under the following path: Software\Classes\Software\think-cell Registry Details for Administration

For IT administrators deploying think-cell, the registry location depends on the installation type:

Per-Machine Installation: The key is typically found in HKEY_LOCAL_MACHINE.

Single-User Installation: The key is located in HKEY_CURRENT_USER.

64-bit Systems: Additional keys for integration with Office are created in Software\Wow6432Node\Microsoft\Office\PowerPoint\Addins\thinkcell.addin. Managing License Keys

Manual Entry: If the license key window appears upon starting PowerPoint or Excel, users can manually enter a valid key provided via email or the think-cell customer portal. Have a tricky think-cell deployment scenario

Automated Deployment: To prevent the license key dialog from appearing for users, administrators can provide the license key during the initial installation or through Windows Group Policies.

Troubleshooting: If entering a valid key does not work, users should check for hidden or hanging POWERPNT.EXE processes in the Task Manager or verify write permissions in the %APPDATA%\think-cell folder.

Updates and Maintenance: Organizations can manage license keys and updates centrally by hosting an XML file (e.g., update.xml) on a web server. How to order licenses - think-cell

❌ Using HKLM – Think-Cell does not read from HKLM. Don’t bother.

❌ Extra spaces – The license key must be contiguous. No line breaks.

❌ Per-machine install, per-user license – Even with MSI installed for all users, each user still needs their own registry key.

❌ Registry redirection (WOW64) – On 64-bit Windows, 32-bit Think-Cell reads from the 32-bit registry view under HKEY_CURRENT_USER\Software\Wow6432Node\Think-Cell\License. Wait – actually, no. Think-Cell correctly uses RegQueryValueEx without redirection flags. But if you’re injecting from a 64‑bit process, it still ends up in the same logical HKCU location. Test first.