CivilGEOCivilGEO
GeoSTORMGeoHECRASGeoHECHMSCustomer StoriesKnowledge BaseProduct TutorialsEngineering Resources
Customer ReviewsCustomer StoriesCustomer VideosCase StudiesWall of LoveProductsKnowledge BaseProduct Tutorials
Training ClassesTraining WebinarsProduct TutorialsProductsKnowledge BaseAbout Us
Get SupportKnowledge BaseFeature RequestsEngineering ResourcesProductsCustomer StoriesAbout Us
About UsPrivacy CenterNewsBlogProductsCustomer StoriesKnowledge Base
Contact
Free Trial
CivilGEO Knowledge Base

Installation

Step-by-step procedures for installing CivilGEO products and configuring network deployments.

3 articles · Generated August 19, 2026

Contents

  1. Installation Procedures
  2. Installation “Error 1402”
  3. Assigning a Static IP Address
  4. Network Deployment
  5. Network Deployment Installation
Installation Procedures

Installation “Error 1402”

When installing or uninstalling Microsoft Windows component technologies on Windows, you may encounter a message box similar to "Error 1402. Could not open key: UNKNOWN Components 385C8F4C818DA64381F63245686473F0...”

Installation Error 1402


The long number listed is not an "address". It is a registry parent container key name (as a GUID) and its child name (as a GUID). The last "" character separates the two parent-child GUIDs.

This error is not related to our CivilGEO software, but rather to components which are provided by Microsoft. The following section describes how the error is generated and how to fix it.

How to fix 'Error 1402. Could not open key: UNKNOWN...'

This error is generally caused by insufficient or incorrect permissions on the named registry keys, or parent container of such registry keys. In relation with CivilGEO software, it may occur after upgrading the computer workstations from Windows 7 to 10, and then upgrading or reinstalling Microsoft products or components. The error can be easily fixed; follow these steps:

  1. Backup your computer or the registry. Microsoft's built-in backup program allows for the "system state" to be selectively backed up. Alternatively, ZIP up the windowssystem32config directory while running in a backup operating system (this is where the registry hive files are located).
  2. Log in as the 'administrator' (or an account with full administrator access) and disable the "UAC" (User Access Control). To disable the UAC, open the "User" control panel applet and select the Change User Account Control Settings. In Windows 10 the next dialog box will display a slider, simply set it to Never Notify.
  3. From the START menu, execute Run... (press WIN+R) and then type "regedit".
  4. Navigate to the following registry root:
    HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerUserDataS-1-5-18Components
    Note: The 'S-1-5-18' key may be different on your computer.
  5. Right-click on the Components registry key, and then choose Permissions...
    Registry Editor
  6. The Permissions for Components dialog box will be displayed.
    Permissions for Components dialog box
  7. Click the [Add...] button and add in the "Administrator", "Administrators" and "SYSTEM" accounts. You might also want to add a local account having administrator privileges.
    Adding permission for component
  8. On the first Permissions for Components dialog box, click on each account (in the top-list) and make sure each has the "Full Control = Allow" and "Read = Allow" permissions.
  9. Click the [Advanced] button to display the Advanced Security Settings for Components dialog box.
    Advanced permission settings
  10. On the Permissions tab, turn on the Replace all child object permission entries with inheritable permission entries from this object checkbox, and then click the [Apply] button.
    Advanced Security Settings for Components dialog box
  11. Repeat the above steps once more. There should not be any errors regarding not being able to update the permissions on the child keys.
  12. Exit the dialog boxes by clicking the [OK] button, and the main registry editor will become the active window.
  13. Re-run the CivilGEO installer or uninstaller by right-clicking on the respective icon and select "Run as administrator..." (if available) from the displayed context menu.
  14. If the "Could not open key" message is displayed, on the exact same keys, it means the above operations were not implemented correctly. Simply repeat the above steps for main registry root node.

If you have any issues regarding this, contact our technical support. They will be glad to assist you further.

Installation Procedures

Assigning a Static IP Address

Our software is licensed as a Node-Locked Workstation License, Floating Network License or Cloud License.

In order to get a Floating Network License to work within a local area network (LAN) environment, Network License Server software needs to be installed on a computer within the network. The computer that the Network License Server is installed on can be any kind of computer (i.e., workstation or server), but must have a static IP address for the software to find the Network License Server.

The video link below describes how to assign a static IP address.

unknown node
Network Deployment

Network Deployment Installation

A network deployment provides an efficient way to install and license CivilGEO software on multiple computers. Many commercial and open-source software utilities are available that can be used as deployment solutions across one or many computers (simultaneously) on the network.

Prerequisites

Before creating the deployment, make sure that the following items are available:

  • The software installer file.
  • Local administrator rights on each target computer.
  • A shared network location that all target computers can access.
  • The license information required for the deployment, such as the floating license server IP address and port, or the cloud license server ID.

Software Deployment Best Practices

Use the following best practices when creating a software deployment across multiple computers on the network:

  1. Create the deployment from a workstation rather than a server
    This helps to eliminate the need for the same computer to run the installation, read the media, and write the files. The combination of these tasks can greatly increase the amount of time necessary to complete the software deployment and can even cause corruption in the process. It is better to create the deployment on a shared network location from an administrative workstation.
  1. Do not create deployments over a WAN or VPN
    Network connections using a WAN or VPN are generally slow and can cause file I/O errors during the deployment creation. Running the deployment over a WAN or VPN can also result in missing or corrupt files.
  1. Temporarily disable antivirus software (optional)
    Running antivirus software while creating the software deployment may cause issues. If allowed by your organization’s IT/security policy, consider temporarily disabling antivirus software during deployment creation. Real-time scanning can slow the process and may block or modify required files, resulting in an incomplete or corrupted deployment. Re-enable antivirus protection after the deployment has been created. This step is optionaln.
  1. Use a shared directory
    Before creating the software deployment, create a shared directory on either the server or on a workstation. Keep the share name short and simple. Do not include spaces in the share name. Do not nest the shared directory too deeply on the drive.
  1. Use a separate folder for each deployment image
    Creating multiple software deployments within the same shared directory can cause corrupt installations and other problems.
  1. Create and store deployments on NTFS file systems only
    Other file systems, such as LINUX, UNIX, DFS, NFS, AIX, and others, can cause unforeseen issues with software deployments, including file systems used on network attached storage (NAS) devices.
  1. Users should have full read/write access
    Users creating the software deployments should have full read/write access to the network share where the software deployments are to be stored.
  1. Use UNC (Uniform Naming Convention) for network paths
    When specifying network paths, use a uniform naming convention (UNC) rather than mapped drive letters. For example, use \servernamesharefolder instead of S:folder. Not all networked computers share the same mapped drive letters, and the use of UNC network paths eliminates these types of problems.
  1. Avoid modifying a deployment once it has been created
    Instead of modifying the existing software deployment, it is better to create a new deployment for each modification that you make.
  1. Avoid moving deployments between servers
    It is not recommended to move software deployments between servers. If you must do this, you may need to modify the deployment to insert its current location into the deployment structure.

Creating a Silent Installation

Our software products use InstallShield software for installation. Using the installation software provided, you can easily create a silent install that allows deployment of the software to multiple computers on your network. This makes it much easier to install the software without having to babysit the installation for each computer.

To manually perform a silent installation, the following steps can be placed in a batch file or script file to automate the installation operation:

  1. Launch the Command Prompt using the Run as Administrator option.
  2. Change to the directory where the SETUP.EXE product installation program resides.
  3. Execute the below command to install the product in silent mode (on one line):

    SETUP.EXE -silent

Silent Install Example

Network-Deployment-Installation-Img-1.png


The installation program options shown above are detailed as follows:

unknown node

Automated Software Installation and License Deployment

When deploying software on an enterprise network that has a floating network license, manually installing the software and entering license server details on each workstation can be time-consuming. For each computer, CivilGEO software requires that the License Server IP Address and Port be manually specified.

Fortunately, the CivilGEO software and network licensing process can be deployed using a command line. This can save time and effort when using automation deployment software, such as PDQ Deploy.

Launch the Command Prompt with the Run as Administrator option in the directory where the SETUP.EXE product installation program resides.

Note: Cloud and Floating network license deployment does not apply to GeoSTORM because this software requires login authentication. To sign in to the GeoSTORM software, refer to this article in our knowledge base.

Floating Network License Deployment

Execute the below command to install the product in silent mode (on one line):

SETUP.EXE -silent FLOATING_SERVER_IP=[Server_IP] FLOATING_SERVER_PORT=[Server_Port]

Silent Install Example

Network-Deployment-Installation-Img-2.png


The installation program options shown above are detailed as follows:

unknown node

Cloud License Deployment

Execute the below command to install the product in silent mode (on one line):

SETUP.EXE -silent CLOUD_SERVER_ID=[Server_ID]

Silent Install Example

Network-Deployment-Installation-Img-3.png


The installation program options shown above are detailed as follows:

unknown node

Additional Installation Options

The following additional options control the display of the installation process:

unknown node

If you have difficulty getting the deployment command to work, contact CivilGEO Technical Support. They will be glad to assist you.

Products

  • Free Trial
  • GeoSTORM
  • GeoHECRAS
  • GeoHECHMS

Customers

  • Customer Portal Login
  • Customer Reviews
  • Customer Stories
  • Customer Videos
  • Case Studies
  • Wall of Love

Training

  • Training Classes
  • Training Webinars
  • Product Tutorials
  • Engineering Resources

Company

  • About Us
  • Contact
  • Privacy Center
  • Terms of Use
  • Brand Assets

Support

  • Knowledge Base
  • Contact Support
  • Feature Requests
  • General Feedback

Contact Us

  • info@civilgeo.com
  • +1 608-729-5100
CivilGEO United States
708 Heartland TrailSuite 3000Madison, WI 53717-2174Tel: 608-729-5100 or 800-488-4110
G2 Best Software 2026 — Top 50 CAD PLM ProductsAutodesk Authorized DeveloperFind us on Ariba Network
Copyright © 2026 CivilGEO, Inc. All rights reserved. The CivilGEO logo, “GeoSTORM”, “GeoHECHMS”, “GeoHECRAS”, and “Ready To Engineer” are registered trademarks of CivilGEO, Inc. All other brands, company names, product names or trademarks belong to their respective holders.