Deletes the specified items.
Remove-Item [-Path*] <String> [-Credential [<PSCredential>]] [-Exclude [<String>]] [-Filter [<String>]][-Force] [-Include [<String>]] [-Recurse] [-Stream [<System.String>]] [-Confirm] [-WhatIf] [-UseTransaction[<SwitchParameter>]] [<CommonParameters>]
Remove-Item [-Credential [<PSCredential>]] [-Exclude [<String>]] [-Filter [<String>]] [-Force] [-Include[<String>]] [-Recurse] [-Stream [<System.String>]] -LiteralPath* <String> [-Confirm] [-WhatIf][-UseTransaction [<SwitchParameter>]] [<CommonParameters>]
The Remove-Item cmdlet deletes one or more items. Because it is supported by many providers, it can delete many different types of items, including files, folders, registry keys, variables, aliases, and functions.
Specifies a user account that has permission to perform this action. The default is the current user.
Type a user name, such as User01 or Domain01User01, or enter a PSCredential object, such as one generated by the Get-Credential cmdlet. If you type a user name, this cmdlet prompts you for a password.
This parameter is not supported by any providers installed with Windows PowerShell.
Specifies items that this cmdlet omits. The value of this parameter qualifies the Path parameter. Enter a path element or pattern, such as *.txt. Wildcard characters are permitted.
Specifies a filter in the format or language of the provider. The value of this parameter qualifies the Path parameter. The syntax of the filter, including the use of wildcard characters, depends on the provider. Filters are more efficient than other parameters, because the provider applies them when it retrieves the objects, instead of having Windows PowerShell filter the objects after they are retrieved.
Forces the cmdlet to remove items that cannot otherwise be changed, such as hidden or read-only files or read-only aliases or variables. The cmdlet cannot remove constant aliases or variables. Implementation varies from provider to provider.
Specifies items to delete. The value of this parameter qualifies the Path parameter. Enter a path element or pattern, such as *.txt. Wildcard characters are permitted.
- This value is required
- Default value is None
- Accepts pipeline input ByPropertyName
Specifies a path of the items being removed. Unlike Path, the value of the LiteralPath parameter is used exactly as it is typed. No characters are interpreted as wildcard characters. If the path includes escape characters, enclose it in single quotation marks. Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences.
- This value is required
- Accepts pipeline input ByValue
Specifies a path of the items being removed. Wildcard characters are permitted.
Indicates that this cmdlet deletes the items in the specified locations and in all child items of the locations.
When it is used with the Include parameter, the Recurse parameter might not delete all subfolders or all child items. This is a known issue. As a workaround, try piping results of the Get-ChildItem -Recurse command to Remove-Item, as described in Example 4 in this topic.
Specifies an alternative data stream from a file that this cmdlet deletes. This cmdlet does not delete the file. Enter the stream name. Wildcard characters are supported.
This parameter is not valid on folders.
The Stream parameter is a dynamic parameter that the FileSystem provider adds to Remove-Item. This parameter works only in file system drives.
You can use Remove-Item to delete an alternative data stream. However, it is not the recommended way to eliminate security checks that block files that are downloaded from the Internet. If you verify that a downloaded file is safe, use the Unblock-File cmdlet.
This parameter was introduced in Windows PowerShell 3.0.
Prompts you for confirmation before running the cmdlet.Prompts you for confirmation before running the cmdlet.
Shows what would happen if the cmdlet runs. The cmdlet is not run.Shows what would happen if the cmdlet runs. The cmdlet is not run.
Includes the command in the active transaction. This parameter is valid only when a transaction is in progress.
This cmdlet supports the common parameters: Verbose, Debug,ErrorAction, ErrorVariable, WarningAction, WarningVariable,OutBuffer, PipelineVariable, and OutVariable.
You can pipe a string that contains a path, but not a literal path, to this cmdlet.
This cmdlet does not return any output.
- Delete files that have any file name extension:
PS C:> Remove-Item C:Test*.*
This command deletes all of the files that have names that include a dot (.) from the C:Test folder. Because the command specifies a dot, the command does not delete folders or files that have no file name extension.
- Delete some of the document files in a folder:
PS C:> Remove-Item * -Include *.doc -Exclude *1*
This command deletes from the current folder all files that have a .doc file name extension and a name that does not include 1. It uses the wildcard character (*) to specify the contents of the current folder. It uses the Include and Exclude parameters to specify the files to delete.
- Delete hidden, read-only files:
PS C:> Remove-Item -Path C:Testhidden-RO-file.txt -Force
This command deletes a file that is both hidden and read-only. It uses the Path parameter to specify the file. It uses the Force parameter to delete it. Without Force, you cannot delete read-only or hidden files.
- Delete files in subfolders recursively:
PS C:> Get-ChildItem * -Include *.csv -Recurse | Remove-Item
This command deletes all of the CSV files in the current folder and all subfolder recursively.
Because the Recurse parameter in Remove-Item has a known issue, the command in this example uses Get-ChildItem to get the desired files, and then uses the pipeline operator to pass them to Remove-Item.
In the Get-ChildItem command, Path has a value of *, which represents the contents of the current folder. It uses Include to specify the CSV file type, and it uses Recurse to make the retrieval recursive.
If you try to specify the file type the path, such as -Path *.csv, the cmdlet interprets the subject of the search to be a file that has no child items, and Recurse fails.
- Delete subkeys recursively:
PS C:> Remove-Item hklm:softwaremycompanyOldApp -Recurse
This command deletes the OldApp registry key and all its subkeys and values. It uses Remove-Item to remove the key. The path is specified, but the optional parameter name (Path) is omitted.
The Recurse parameter deletes all of the contents of the OldApp key recursively. If the key contains subkeys and you omit the Recurse parameter, you are prompted to confirm that you want to delete the contents of the key.
You can also refer to Remove-Item by any of its built-in aliases: del, erase, rmdir, rd, ri, or rm. For more
information, see about_Aliases.
Remove-Item cmdlet is designed to work with the data exposed by any provider. To list the providers available
in your session, type Get-PsProvider. For more information, see about_Providers.