Ignite Global Support Home Start a conversation Sign in
Start a conversation
  1. ObjectStore
  2. ObjectStore Articles
  3. Articles

ObjectStore 2025.2 on Windows Fails to Run After Setup (Registry Root Key Mismatch)

Contents

Overview

On Windows, the original ObjectStore 2025.2 package can fail to run after installation because the runtime looks for a different registry root key than the installer creates. This mismatch prevents the ObjectStore Server and ObjectStore Cache Manager Windows services from starting.

A permanent fix is available in a refreshed ObjectStore 2025.2 Windows package that restores the historical convention (registry key scoped to major version only). A temporary workaround is to start the services with the -r registry-location override pointing at the major-version key.

Solution

Applies to

  • Product: ObjectStore
  • Platform: Windows
  • Version: ObjectStore 2025.2 (original Windows package exhibiting registry root mismatch)

Symptoms

  • Installation completes, but ObjectStore 2025.2 does not run after setup.
  • Windows services for ObjectStore (Server / Cache Manager) do not start normally.
  • Registry root mismatch is visible:
    • Runtime expects:
      HKEY_LOCAL_MACHINE\SOFTWARE\ObjectStore Inc.\ObjectStore 2025.2
    • Installer creates:
      HKEY_LOCAL_MACHINE\SOFTWARE\ObjectStore Inc.\ObjectStore 2025

Root cause

The ObjectStore 2025.2 Windows runtime was coded to read a minor-version registry root (...\ObjectStore 2025.2) while the installer created the historically used major-version registry root (...\ObjectStore 2025). Because the runtime could not find the expected root, ObjectStore services failed to start.

Resolution options

Option A (Permanent fix): Install the refreshed ObjectStore 2025.2 Windows package

A refreshed 2025.2 build restores the major-version registry root convention by reverting OS_REG_OSTORE_NAME (in regnames.hh) back to “ObjectStore 2025”, aligning runtime behavior with the installer and prior release convention.

Steps

  1. Download the refreshed ObjectStore 2025.2 Windows package from your standard release/download portal (for example: release/download portal).
  2. Install/upgrade using your normal ObjectStore installation procedure.
  3. Start (or restart) the ObjectStore Windows services.

Expected result

  • Services start normally without needing any registry-location override.
  • Registry shows only:
    HKLM\SOFTWARE\ObjectStore Inc.\ObjectStore 2025

Option B (Workaround for the original 2025.2 package): Use the -r registry-location override

If you must run the original package before updating, configure the Windows services to point to the major-version registry root using the -r parameter.

Key requirement

  • The -r value is relative to HKLM\SOFTWARE. Do not include the HKLM\SOFTWARE\ prefix in the argument.

Example

-r "ObjectStore Inc.\ObjectStore 2025"

Steps

  1. Open the Windows Services management console (services.msc) or your service configuration tool.
  2. For each relevant ObjectStore service (Server and Cache Manager), update the service start parameters to include:
    • -r "ObjectStore Inc.\ObjectStore 2025"
  3. Restart the services.
  4. Re-test ObjectStore startup and operations.

If available in your environment, follow your standard documentation for “Changing the Registry Location for ObjectStore (Windows)” at <kb_article_url>.

How to Validate the Fix

After applying Option A (preferred) or Option B (workaround), confirm the following:

  1. Both Windows services start cleanly (ObjectStore Server and ObjectStore Cache Manager).
  2. Registry root present is correct for major version:
    • HKLM\SOFTWARE\ObjectStore Inc.\ObjectStore 2025
  3. Basic runtime checks succeed:
    • Configuration loads successfully
    • Checkpointing works
    • CRUD operations against a persistent database succeed

Verification note (refreshed package)

On a clean Windows Server installation with a fresh ObjectStore 2025.2 install (refreshed package), both services start cleanly, only HKLM\SOFTWARE\ObjectStore Inc.\ObjectStore 2025 exists, and configuration/checkpointing plus CRUD tests complete successfully.

Frequently Asked Questions

1. How can I tell if I’m affected by this specific issue?
You’re likely affected if ObjectStore 2025.2 on Windows won’t run after installation and you observe that the runtime is looking for HKLM\SOFTWARE\ObjectStore Inc.\ObjectStore 2025.2 while the installer created HKLM\SOFTWARE\ObjectStore Inc.\ObjectStore 2025.
2. What is the exact workaround if I can’t immediately install the refreshed package?
Configure the ObjectStore Windows services to include the registry-location override using a path relative to HKLM\SOFTWARE, for example: -r "ObjectStore Inc.\ObjectStore 2025", then restart the services.
3. Do I include HKLM\SOFTWARE\ in the -r parameter?
No. The -r value is specified relative to HKLM\SOFTWARE. Use -r "ObjectStore Inc.\ObjectStore 2025", not -r "HKLM\SOFTWARE\ObjectStore Inc.\ObjectStore 2025".
4. How do I verify the permanent fix is in place after upgrading?
Confirm both ObjectStore services start without the -r override and confirm the only registry root present is HKLM\SOFTWARE\ObjectStore Inc.\ObjectStore 2025. Then run basic operational checks (configuration load, checkpointing, and CRUD tests).
5. What should I do if services still don’t start after applying the refreshed 2025.2 package?
Re-check that the registry root exists at HKLM\SOFTWARE\ObjectStore Inc.\ObjectStore 2025, restart both services, and collect Windows service start logs/errors plus a screenshot or export of the relevant registry path(s) before contacting support.
Choose files or drag and drop files
ai_initiated
atlas_studio
kb_automation
Was this article helpful?
Yes
No

  1. Priyanka Bhotika

  2. Posted

Comments