Metamation Developer Notes

  • Developer Notes
  • Resource Map
  • Tools
    • Code Formatting
    • Configuring Git
    • Assignments
    • Testing with Windows Sandbox
    • Single Binary Applications
    • Self-Updating Applications
  • Flux Workflow
    • Flux Workflow
    • Flux Development Style Guide
    • Release notes for Flux
    • SonarCloud analysis for Flux
    • Build a Flux SDK Program
    • Shipping Flux
    • Flux.Test
      • BasicBendAuto Test
      • LaserAuto.cs Detailed Documentation
      • Laserexample:Test1
  • Technical Notes
    • File formats
      • .FX File Format
      • Au(Gold) streams
      • .GEO File Format
      • .LST File Format
      • .LST file - technology
      • .BNC File Format
      • .WAD Files: Flux Resource Packages
      • .Curl Files: ASCII config information
    • Folders App
      • Data\Bendtools
      • Data\Machines
    • FluxCode
      • Welcome & Repo Map
      • Architecture & System Context
      • Subsystem *Bend* (Press Brake)
      • Subsystem *BCell* (Bend Cell Automation)
      • API Maps
      • Data Model Catalog
      • Design Patterns -- A Reader's Guide
      • Tests and Golden Paths
      • Guided Code Tours
      • CAM Glossary with Code Mapping
      • Assignments
      • Flux Onboarding Handbook
    • Data flow
      • Part
        • Part.Dwg
        • Part.Load
        • Part.Load to Part.Dwg
      • BendTech.cs
      • Bend Technology
      • Laser Cutting Technology
    • Machine ID Scheme
  • FluxTester
    • LaserTooling.cs Test Steps
    • Fluxtester Recipe Book
    • Nesting.cs Overview
    • Nesting.cs Recipe Book
    • Job.cs Overview
    • Job.cs Recipe Book
  • 3d party software
    • Python
  • Documentation
    • Bento tool
      • Structure
      • Attributes
    • Software
      • Software Requirement
      • Installation
      • Git Workflow
      • Environment Variable
      • Tools
    • Workflow
      • Roles
      • Analyze
      • Edit
      • Proofread
      • Pre-Publish
      • Publish
      • Release cycle
      • Information required for Documentation Team
      • Checklist for Documenters
    • Styleguide
    • Flavoring
    • Translation
      • General process
      • Anchor points
      • BT Diff Generation
      • BT Translate
      • BT Apply Changes
      • Order at Seprotec
    • Citations
Documentation
/
Software
/
Environment Variable

Environment Variable

User Variables vs System Variables in Windows

In Windows, environment variables are dynamic values that can affect the behavior of running processes. They are used to store information about the system environment and user preferences. There are two main types of environment variables:

  1. User Variables

  2. System Variables.

System Variables

System Variables are defined by the operating system and are available globally to all users on the system. These variables provide essential information required by the system and other applications to perform their tasks. For example, the PATH variable contains directories where executable files are located, allowing users to run programs from the command prompt without specifying their full paths

System variables are typically set by the system administrator and should not be modified by regular users. They are crucial for the proper functioning of the operating system and applications. Examples of system variables include %windir%, which points to the Windows installation directory, and %TEMP%, which points to the directory where temporary files are stored

User Variables

User Variables are specific to the currently logged-in user and can be customized by the user. These variables allow users to set their own preferences and configurations without affecting other users on the same system. For instance, a user can define their own PATH variable to include directories specific to their applications

User variables are stored in the user’s environment block and are only accessible to the user who created them. They can be used to define folders for temporary files, application-specific settings, and other user-specific information

Precedence

When both user and system variables have the same name, user variables take precedence over system variables. This means that if a user defines a variable with the same name as a system variable, the user-defined variable will be used instead of the system variable for that particular user

However, this precedence only applies to the user who defined the variable. Other users will still use the system variable by default.

An exception to this rule is the PATH variable. The user-defined PATH variable does not completely replace the system PATH variable. Instead, it is appended to the system PATH variable, resulting in a combined path that includes both system and user-specific directories

Managing Environment Variables

To manage environment variables in Windows, follow these steps:

  1. Right-click on This PC and select Properties.

  2. Click on Advanced system settings.

  3. Click on the Environment Variables button.

In the Environment Variables window, you can view, add, edit, and delete both user and system variables. It is important to be cautious when modifying system variables, as incorrect changes can affect the stability and functionality of the system

In summary, system variables are global and essential for the operating system, while user variables are specific to individual users and allow for customization. User variables take precedence over system variables, except for the PATH variable, which is combined with the system PATH.

Contents

  • User Variables vs System Variables in Windows
  • System Variables
  • User Variables
  • Precedence
  • Managing Environment Variables
Git Workflow Tools

      Copyright © 2025 TRUMPF Metamation. All rights reserved.

    Compiled by Bento