In certain situations, you may find that you have two different versions of OnePager installed side-by-side in the same Windows user account. This is not supported, and typically happens when an old version of OnePager was originally installed in an administrator account for use by all users on the machine. Later, an end user without admin rights might have attempted to install a newer version of OnePager into their own account only, just for their own use.
This causes the end user’s account to have two different versions of OnePager simultaneously installed: the older installation from the administrator and the newer installation from the end user. Sometimes both versions are fully installed as shown below, and sometimes there is one full installation of an older version and another partial installation of a newer version that come into conflict with each other.
For clarity, it is acceptable to have different versions of OnePager installed in different Windows user accounts, as long as those versions are specific to one user, and not installed on a per-machine basis. Further, it is also acceptable to have different editions (e.g. OnePager Pro and OnePager Express) installed into the same user account, as these are different products. On the other hand, installing two versions of the same edition (e.g. OnePager Pro v6.1 and OnePager Pro v7.0) is not supported, and will cause issues, even if both installations appear to be successful.
In this article, we will walk you through different ways to remedy a side-by-side installation. You can try these steps sequentially, as the first set of steps may resolve the issue without needing to follow the subsequent steps. However, in some cases, all steps will need to be followed in sequence to completely resolve the issue.
Uninstall All Versions from All Windows Accounts
Go to your control panel and install all versions of OnePager, both old and new. If you have multiple Windows user accounts, you MUST go into each of those accounts and perform the same uninstallations. Simply removing OnePager from a single user account is not sufficient and will continue to cause issues. In many cases, there is an administrator account on the computer that has an outdated version of OnePager installed, and that administrator’s older installation is the source of the issue.
After removing all versions of OnePager from all Windows user accounts, you can try to reinstall the desired version into your own user account. If the new version works normally, then you have successfully cleaned up the mixed installations using the Windows control panel, and will not need to follow the remaining instructions. If you continue to experience issues, please uninstall the newly-installed version of OnePager again and proceed to follow all of the next steps in this article.
Finding Installation Remnants
If the issue persists after uninstalling all versions of OnePager from all Windows accounts, the next step is to delete the OnePager AppData folders from your own Windows user account. The following folders should be removed:
- C:\Users\yourname\AppData\Local\Chronicle Graphics
- C:\Users\ yourname\AppData\Roaming\Chronicle Graphics
Once these two folders are deleted, go to Windows File Explorer and search for all files ending with an *.t_d extension. Again, make sure you search the entire hard drive, often called Local Disk (C:), for these files, not just your individual Windows account:
If Windows File Explorer locates any remaining *.t_d files, this is an indication that OnePager is still installed somewhere on your computer and those remnants need to be removed. Again, it is best to do this through the Windows Control Panel, but if it is not listed there for the Windows account in question, you can navigate to the folder containing the *.t_d file and then navigate from there to delete the parent folder. To delete these folders manually, right-click on the *.t_d file that you found and choose Open File Location:
Once the file location is open, navigate from the data folder up to the Local folder in the same tree:
For example, here we start in:
C:\users\yourname\AppData\Local\Chronicle Graphics\OnePager Express\data\
We want to end up here instead:
Once in the Local folder, delete the Chronicle Graphics folder and all of its subfolders.
Next, for the same path, switch from the Local folder to the Roaming folder.
For example, if you are here:
Then you should switch to here:
From the Roaming folder, if there is another Chronicle Graphics subfolder, delete it as well.
Repeat these steps until all of the Chronicle Graphics folders in both Local and Roaming have been deleted for each result in your Windows Search.
To ensure that all of OnePager’s system files have been removed, return to Windows File Explorer and perform a second search on the C:\ drive. This time, instead of searching for *.t_d files, search for a file called CG_StandAlone.exe.
If you have successfully cleaned your computer of OnePager system files, there should be no instances of CG_StandAlone.exe remaining. If Windows finds remaining instances of CG_Standalone.exe, then you are not finished yet. You will need to repeat the above process, again using the Open File Location context menu option to browse to any folders containing these installation remnants, and again removing the Chronicle Graphics subfolders from both the Local and Roaming trees wherever these still exist.
Cleaning up the OnePager Registry
Next, open the registry editor (regedit) and navigate to the following location:
Delete the Chronicle Graphics registry key, which will remove OnePager registry entries from the current user’s account.
Now, search the registry for any other instances of the words Chronicle Graphics. There may be other instances of these under HKEY_LOCAL_MACHINE or HKEY_USERS that correspond to other users’ accounts on the same machine, or to machine-level installations of OnePager.
If a search of the registry did not come up with other Chronicle Graphics folder locations other than the first set, then you will need to load the hive for other users on the device. To do this:
Select HKEY_USERS in the registry
Go to File > Load Hive
Navigate to the folder for the other user and load the hive file. For example:
Give the loaded hive a name, typically the same as the user account.
Open the Software registry key, find the Chronicle Graphics sub-key, and delete it.
Repeat this process for all user hives on the computer, until the Chronicle Graphics sub-key has been deleted from all user hives on the device.
Cleaning up the Microsoft Registry
When OnePager is installed, it leaves breadcrumbs in Microsoft’s registry, either for Microsoft Project or Excel, depending on the edition of OnePager that is installed. These breadcrumbs tell Microsoft Project or Excel where to look when loading OnePager as an add-in.
The first breadcrumb tells Microsoft that OnePager is installed, and the second breadcrumb tells Microsoft how to launch OnePager as an add-in. To find the first breadcrumb:
Launch the registry editor
Open the HKEY_CURRENT_USER hive and navigate to the following location:
Expand the Office key, and either click on MS Project or Excel, depending on where you are trying to launch the add-in.
Determine which breadcrumb you should be looking for, based on the edition of OnePager you are running:
Now, expand the Addins key and find the breadcrumb that you need. Here is an example of the OnePager Pro breadcrumb for Microsoft Project:
Make sure that the key has values and data similar to the screenshot above. Assuming so, then the first breadcrumb is set up correctly.
You will need to double-check the second breadcrumb to ensure that Microsoft can successfully find the DLL is that is required to launch OnePager as an add-in. This second breadcrumb is more likely to have issues if you have remnants of a previous OnePager installation. To find the second breadcrumb:
Launch the registry editor.
In the HKEY_CURRENT_USER hive, go to Edit > Find…
Speed up your search by restricting it to only look at Keys:
Search for the key based on where you are trying to launch OnePager:
Once you have located the key, expand it, and open the InprocServer32 sub-key:
There should be one and only one DLL path shown for each edition of OnePager that you have installed. For example, if you have OnePager Pro and OnePager Bundle installed side-by-side, you can expect to see two DLL paths, but if you only have OnePager Pro installed, you should only have one. If you only have one edition of OnePager and there are multiple DLL paths, remove the duplicates so that only the latest version remains. If there is no DLL path or it’s empty, then you should be able to recreate it by reinstalling OnePager. Either way, your sole DLL path should always reflect the version of OnePager that you intend to use.
In this example, the path for the OnePager Pro or OnePager Bundle DLL that Microsoft Project will load is:
C:\Users\yourname\AppData\Roaming\Chronicle Graphics\OnePager [Edition]\x.y.z\CG_MSP_COMShim.dll
If you are using OnePager Express or OnePager Bundle with Excel, the path will be slightly different:
C:\Users\yourname\AppData\Roaming\Chronicle Graphics\OnePager [Edition]\x.y.z\CG_XL_COMShim.dll
With all of the remnants removed from the Windows Control Panel, the file system, and the registry, it should now be safe to do a clean installation of the newer version of OnePager. After reinstalling, double-check the two Microsoft registry breadcrumbs again to ensure that the DLL path for OnePager is correct. If it is empty, you can recreate it by hand, and Project or Excel should be able to enable the add-in the next time it is launched.
Last Updated: December 30, 2022