gremetrix.blogg.se

In PowerShell, you can access it via the Shell.Application COM server: (New-Object -ComObject Shell.Application).NameSpace('shell:Downloads').Self.Pathįor a list of all supported ( shell:-prefixed) folder identifiers, see this article. Only the WinAPI's Known Folders API allows retrieval of the designated downloads folders in a robust fashion, without relying on fixed relationships with other known folders: GetFolderPath() method to ask for special known folders, the designated folder for downloads is - surprisingly - NOT among them. NET framework and can therefore use the System.Environment type's. While PowerShell has virtually unlimited access to the.

Adding such a feature has been proposed on GitHub, however.

PowerShell, as of PowerShell Core 7.0.0-preview.3, has no PowerShell-native way of asking the system for known folder locations. The only robust way to determine the downloads folder's location is to ask the system for it: More importantly, the downloads folder may have been explicitly configured to be in an arbitrary location, unrelated to the documents location That $HOME, which is equivalent to environment variable USERPROFILE ( $env:USERPROFILE), is the root directory for the user's documents isn't always true, namely not with roaming profiles - only "$" reliably reflects the documents folder. "$HOME\Downloads" assumes two things, which aren't necessarily true:

(New-Object -ComObject Shell.Application).NameSpace('shell:Downloads').Self.Path The naive answer, which typically but not always works:.