I've been chipping in on a forum post about finding if a given file exists in any folder within the system environmental %PATH% variable using Windows PowerShell. There are several ways you might approach this. But the best way in my opinion is to leverage the PowerShell pipeline. Perhaps you don't really need the solution but I think it is a valuable learning opportunity.<\/p>\n
First off, you can access Windows environmental variables with the Environment PSProvider. All environmental variables can be in the ENV: psdrive.<\/p>\n
[cc lang=\"PowerShell\"]
\nPS S:\\> dir env:
\n[\/cc]<\/p>\n
The easy way to reference a specific variable is like this:<\/p>\n
[cc lang=\"PowerShell\"]
\nPS S:\\> $env:PSModulePath
\nC:\\Users\\Jeff\\Documents\\WindowsPowerShell\\Modules;C:\\Windows\\system32\\WindowsPowerShell\\v1.0\\Modules\\;C:\\Program Files\\Intel Corporation\\PowerShell\\Modules
\n[\/cc]<\/p>\n
So to get the %PATH% variable we would use $env:Path. Because the path is stored as a semi-colon delimted entries we can split it.<\/p>\n
[cc lang=\"PowerShell\"]
\nPS S:\\> $env:path.split(\";\")
\n%SystemRoot%\\system32\\WindowsPowerShell\\v1.0\\
\nC:\\Program Files\\Common Files\\Microsoft Shared\\Microsoft Online Services
\nC:\\Program Files (x86)\\Common Files\\Microsoft Shared\\Microsoft Online Services
\nC:\\Program Files (x86)\\VMware\\VMware vSphere CLI\\Perl\\site\\bin
\nC:\\Program Files (x86)\\VMware\\VMware vSphere CLI\\Perl\\bin
\nC:\\Program Files (x86)\\NVIDIA Corporation\\PhysX\\Common
\nC:\\Windows\\system32
\nC:\\Windows
\nC:\\Windows\\System32\\Wbem
\nC:\\Windows\\System32\\WindowsPowerShell\\v1.0\\
\nc:\\Program Files (x86)\\Microsoft SQL Server\\100\\Tools\\Binn\\
\nc:\\Program Files\\Microsoft SQL Server\\100\\Tools\\Binn\\
\nc:\\Program Files\\Microsoft SQL Server\\100\\DTS\\Binn\\
\nc:\\Program Files (x86)\\Microsoft SQL Server\\100\\Tools\\Binn\\VSShell\\Common7\\IDE\\
\nc:\\Program Files (x86)\\Microsoft SQL Server\\100\\DTS\\Binn\\
\nC:\\Windows\\System32\\Windows System Resource Manager\\bin
\nC:\\Program Files\\Windows Imaging\\
\nC:\\Windows\\System32\\Windows System Resource Manager\\bin
\n[\/cc]<\/p>\n
Each path is written to the pipeline. Because the goal is to filter paths that only contain the file, we can take advantage of Where-Object.<\/p>\n
[cc lang=\"PowerShell\"]
\nPS S:\\> $env:path.split(\";\") | Where {test-path -path \"$_\\notepad.exe\"}
\nC:\\Windows\\system32
\nC:\\Windows
\n[\/cc]<\/p>\n
The $_ is the current object in the pipeline, or each path element that comes from splitting the path. If Test-Path is True, then the path element is passed to the end of the pipeline. An alternative might be to pipe to Join-Path which uses the piped in value for its -Path parameter.<\/p>\n
[cc lang=\"PowerShell\"]
\nPS S:\\> $env:path.split(\";\") | Join-path -child \"notepad.exe\" | Where {test-path $_}
\nC:\\Windows\\system32\\notepad.exe
\nC:\\Windows\\notepad.exe
\n[\/cc]<\/p>\n
If we wanted to get the file details we can take this a step further and pipe to Get-Item. Again, the value will be used for the -Path parameter.<\/p>\n
[cc lang=\"PowerShell\"]
\nPS S:\\> $env:path.split(\";\") | Join-path -child \"notepad.exe\" | Where {test-path $_} | get-item<\/p>\n
Directory: C:\\Windows\\system32<\/p>\n
Mode LastWriteTime Length Name
\n---- ------------- ------ ----
\n-a--- 7\/13\/2009 9:39 PM 193536 notepad.exe<\/p>\n
Directory: C:\\Windows<\/p>\n
Mode LastWriteTime Length Name
\n---- ------------- ------ ----
\n-a--- 7\/13\/2009 9:39 PM 193536 notepad.exe
\n[\/cc]<\/p>\n
For this particular exercise there is one limitation: any path element that uses a environmental variable like %Windir%, won't work. I'll work on that separately. The main takeaway is to look at cmdlet parameters and see where you can leverage the pipeline. Let PowerShell do the work for you.<\/p>\n","protected":false},"excerpt":{"rendered":"
I’ve been chipping in on a forum post about finding if a given file exists in any folder within the system environmental %PATH% variable using Windows PowerShell. There are several ways you might approach this. But the best way in my opinion is to leverage the PowerShell pipeline. Perhaps you don’t really need the solution…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[8],"tags":[309,251,98,534,128],"class_list":["post-1801","post","type-post","status-publish","format-standard","hentry","category-scripting","tag-filtering","tag-join-path","tag-pipeline","tag-powershell","tag-test-path"],"yoast_head":"\n