René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`Get-Process`: Add a switch that limits retrieval to the current user's own processes","articleBody":"### Summary of the new feature / enhancement\r\n\r\nWhen retrieving processes - either with or without a `-Name` filter - it would be helpful to allow limiting the set of candidate processes to the current user's _own_ processes, say with a newly introduced `-CurrentUser` (or `-User`) switch\r\n\r\n```powershell\r\n# WISHFUL THINKING\r\n\r\n# Only retrieve processes started with the current user identity.\r\nGet-Process -CurrentUser\r\n\r\n# Only retrieve `cmd` processes started with the current user identity.\r\nGet-Process -CurrentUser -Name cmd\r\n```\r\n\r\nIt is often only one's own processes that are of interest, especially when running _non-elevated_.\r\n\r\nIn non-elevated sessions, there's currently no easy way to determine which processes are one's own.\r\n_Update_: One's own means: all processes running with the current user identity, irrespective of how they were started - see discussion in the next two comments.\r\n\r\nEven in elevated sessions the solution is cumbersome:\r\n`Get-Process -IncludeUserName  | Where UserName -eq $env:USERDOMAIN\\$env:USERNAME`\r\n\r\n\r\n### Proposed technical implementation details (optional)\r\n\r\nAdd the new switch only to the `Name` parameter set.\r\n\r\nIt would be the (possibly `-Name`-filtered) equivalent of the following, which on Windows can currently only be run with elevation:\r\n\r\n```powershell\r\n#requires -RunAsAdministrator\r\nGet-Process -IncludeUserName  | \r\n  Where UserName -eq ($IsWindows ? \"$env:USERDOMAIN\\$env:USERNAME\" : $env:USER)\r\n```\r\n\r\n\r\n","author":{"url":"https://github.com/mklement0","@type":"Person","name":"mklement0"},"datePublished":"2024-03-04T18:04:39.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/21301/PowerShell/issues/21301"}