Windows 7 PATH system32 should be System32

Kidd

New Member
Joined
Nov 2, 2009
Messages
6
Just a message for the MS support staff.

This is either something that has come up hundreds of times (and I can't find it) or I'm just plain wrong. (I think that this same problem existed in Vista, so this may be really old and I'm making a fool out of myself.)

In Control Panel=>System=>Advanced System Settings=>Advanced=>Environmental Variables the PATH variable has the directory %SystemRoot%\system32 instead of %SystemRoot%\System32. Check out the directories under c:\Windows.

So why is this little detail important given that the MS Windows OS is not case sensitive? Some OS independent apps are case sensitive and load the path.

My system: Win 7 Ultimate 64 N (sorry, I can't find the build version)
 
Solution
In Windows environments, path variables are not case-sensitive, as you correctly noted. However, there are some components or applications that are case-sensitive and might not recognize paths correctly if the case does not match what they expect. Regarding the discrepancy you observed in the path variable %SystemRoot%\system32 instead of %SystemRoot%\System32, this is indeed an interesting detail. While Windows itself is case-insensitive, specific applications or utilities might have case-sensitive behavior and could potentially be impacted by this variation in case. To address your concern, it's worth considering a few points: 1. Compatibility: Some third-party applications or scripts might rely on the correct case...
In Windows environments, path variables are not case-sensitive, as you correctly noted. However, there are some components or applications that are case-sensitive and might not recognize paths correctly if the case does not match what they expect. Regarding the discrepancy you observed in the path variable %SystemRoot%\system32 instead of %SystemRoot%\System32, this is indeed an interesting detail. While Windows itself is case-insensitive, specific applications or utilities might have case-sensitive behavior and could potentially be impacted by this variation in case. To address your concern, it's worth considering a few points: 1. Compatibility: Some third-party applications or scripts might rely on the correct case in paths. If they expect System32 but encounter system32, they might fail to find the necessary components. 2. Consistency: While Windows is case-insensitive, maintaining consistency in path variables helps prevent potential issues with applications that do treat case differently. 3. Best Practices: Following best practices for maintaining paths, even in a case-insensitive environment, can help ensure smoother interoperability with various tools and software. Given your observation, it might be beneficial to correct the case of the %SystemRoot%\system32 variable to %SystemRoot%\System32 for completeness and to align with common expectations. This adjustment could help ensure better compatibility and prevent any unforeseen issues that sensitive applications might encounter. If you encounter any specific applications or scenarios where this case discrepancy causes issues, addressing it by correcting the variable might help mitigate such problems. Additionally, ensuring consistency in path variables can contribute to a more robust and reliable system configuration.
 
Solution