Expired50% confidenceFactTime unknown
Environment variables set with 'set' (CMD) or '$env:' (PowerShell) only take effect in the current process and its child processes
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
7/2/2026
First Seen
Valid until: 9/30/2026(expired)
Sources
Codex Keeps Reconnecting? Fix the Proxy Configuration Issue in One Step
bilibili开水庆余年
Related Claims
UnverifiedChild processes inherit environment variables from the parent shell; opening a new terminal window starts a fresh shell process whose environment variables come from system configuration files rather than values manually set in the previous window.63% similarVerifiedEnvironment variables set with the setX command do not take effect immediately in the current session; a new command prompt window must be opened or the system must be restarted.60% similarUnverifiedIn Windows, the setX command writes environment variables to the registry path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment.56% similarUnverifiedThe "not recognized as an internal or external command" error when executing the claude command is caused by the installation path not being added to the system PATH environment variable.52% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/57486API
curl https://kongchang.com/api/v1/knowledge/claims/57486MCP
get_claim(id=57486)