使用Remove-Item命令时，即使使用-r和-Force参数，有时也会返回以下错误消息:
Remove-Item : Cannot remove item C:\Test Folder\Test Folder\Target: The directory is not empty.
特别是在Windows资源管理器中打开要删除的目录时，会发生这种情况。
现在，虽然可以通过关闭Windows资源管理器或不浏览该位置来避免这种情况，但我在多用户环境中工作脚本(在这种环境下，人们有时会忘记关闭Windows资源管理器窗口，但我对删除的解决方案感兴趣)整个文件夹和目录，即使它们已在Windows资源管理器中打开。
我可以设置比
-Force更强大的选项来实现此目的吗？为了可靠地重现此代码，请创建文件夹
C:\Test Folder\Origin并在其中填充一些文件和子文件夹(重要)，然后采用以下脚本或类似脚本并执行一次。现在打开C:\Test Folder\Target的子文件夹之一(在我的例子中，我使用了包含C:\Test Folder\Target\Another Subfolder的A third file.txt)，然后尝试再次运行该脚本。您现在将得到错误。如果您第三次运行该脚本，则不会再次出现该错误(但是，根据我尚未确定的情况，该错误有时会第二次发生，然后再也不会发生，有时又每第二次发生一次)。$SourcePath = "C:\Test Folder\Origin"
$TargetPath = "C:\Test Folder\Target"
if (Test-Path $TargetPath) {
Remove-Item -r $TargetPath -Force
}
New-Item -ItemType directory -Path $TargetPath
Copy-Item $SourcePath -Destination $TargetPath -Force -Recurse -Container
最佳答案
更新:从(至少为[1])Windows 10版本20H2 (我不知道Windows Server的版本和与之相对应的版本；运行winver.exe来检查您的版本和内部版本)，现在显示DeleteFile Windows API函数同步行为隐式解决了PowerShell的Remove-Item和.NET的System.IO.File.Delete/System.IO.Directory.Delete的问题(但奇怪的是，不是cmd.exe的rd /s)。
这是，最终仅是一个计时问题:尝试删除父目录时，子目录的最后一个句柄可能尚未关闭-这是的基本问题，不限于具有文件资源管理器 window 打开:
令人难以置信的是，Windows文件和目录删除API的是异步的:即，在函数调用返回时，不能保证删除已完成。
遗憾的是， Remove-Item无法解释该-且cmd.exe的rd /s和.NET的[System.IO.Directory]::Delete()都没有-有关详细信息，请参见this answer。
这会导致间歇性，不可预测的故障。
解决方法由this YouTube video提供(从7:35开始)，其PowerShell实现如下:
同步目录删除功能Remove-FileSystemItem :
重要提示:
Remove-Item的要求。在Windows上，自定义实现:cmd.exe会锁定-参见下文)。FILE_SHARE_DELETE/[System.IO.FileShare]::Delete(很少见)打开的文件也不会阻止删除，尽管它们确实以父目录中的临时名称存在，直到关闭它们的最后一个句柄为止。不同于PowerShell，
cmd.exe(命令提示符)确实锁定了当前目录，因此，如果打开了cmd.exe窗口，其当前目录是目标目录或其子目录之一，则删除将失败。FILE_SHARE_DELETE/[System.IO.FileShare]::Delete(很少使用此模式)下未打开的目标目录的子树中保持文件打开，则删除将失败。请注意，这仅适用于在处理文件内容时保持打开状态的应用程序。 (例如Microsoft Office应用程序)，而文本编辑器(例如记事本和Visual Studio Code)则不会保持打开状态。Remove-Item -Force 。 function Remove-FileSystemItem {
<#
.SYNOPSIS
Removes files or directories reliably and synchronously.
.DESCRIPTION
Removes files and directories, ensuring reliable and synchronous
behavior across all supported platforms.
The syntax is a subset of what Remove-Item supports; notably,
-Include / -Exclude and -Force are NOT supported; -Force is implied.
As with Remove-Item, passing -Recurse is required to avoid a prompt when
deleting a non-empty directory.
IMPORTANT:
* On Unix platforms, this function is merely a wrapper for Remove-Item,
where the latter works reliably and synchronously, but on Windows a
custom implementation must be used to ensure reliable and synchronous
behavior. See https://github.com/PowerShell/PowerShell/issues/8211
* On Windows:
* The *parent directory* of a directory being removed must be
*writable* for the synchronous custom implementation to work.
* The custom implementation is also applied when deleting
directories on *network drives*.
* If an indefinitely *locked* file or directory is encountered, removal is aborted.
By contrast, files opened with FILE_SHARE_DELETE /
[System.IO.FileShare]::Delete on Windows do NOT prevent removal,
though they do live on under a temporary name in the parent directory
until the last handle to them is closed.
* Hidden files and files with the read-only attribute:
* These are *quietly removed*; in other words: this function invariably
behaves like `Remove-Item -Force`.
* Note, however, that in order to target hidden files / directories
as *input*, you must specify them as a *literal* path, because they
won't be found via a wildcard expression.
* The reliable custom implementation on Windows comes at the cost of
decreased performance.
.EXAMPLE
Remove-FileSystemItem C:\tmp -Recurse
Synchronously removes directory C:\tmp and all its content.
#>
[CmdletBinding(SupportsShouldProcess, ConfirmImpact='Medium', DefaultParameterSetName='Path', PositionalBinding=$false)]
param(
[Parameter(ParameterSetName='Path', Mandatory, Position = 0, ValueFromPipeline, ValueFromPipelineByPropertyName)]
[string[]] $Path
,
[Parameter(ParameterSetName='Literalpath', ValueFromPipelineByPropertyName)]
[Alias('PSPath')]
[string[]] $LiteralPath
,
[switch] $Recurse
)
begin {
# !! Workaround for https://github.com/PowerShell/PowerShell/issues/1759
if ($ErrorActionPreference -eq [System.Management.Automation.ActionPreference]::Ignore) { $ErrorActionPreference = 'Ignore'}
$targetPath = ''
$yesToAll = $noToAll = $false
function trimTrailingPathSep([string] $itemPath) {
if ($itemPath[-1] -in '\', '/') {
# Trim the trailing separator, unless the path is a root path such as '/' or 'c:\'
if ($itemPath.Length -gt 1 -and $itemPath -notmatch '^[^:\\/]+:.$') {
$itemPath = $itemPath.Substring(0, $itemPath.Length - 1)
}
}
$itemPath
}
function getTempPathOnSameVolume([string] $itemPath, [string] $tempDir) {
if (-not $tempDir) { $tempDir = [IO.Path]::GetDirectoryName($itemPath) }
[IO.Path]::Combine($tempDir, [IO.Path]::GetRandomFileName())
}
function syncRemoveFile([string] $filePath, [string] $tempDir) {
# Clear the ReadOnly attribute, if present.
if (($attribs = [IO.File]::GetAttributes($filePath)) -band [System.IO.FileAttributes]::ReadOnly) {
[IO.File]::SetAttributes($filePath, $attribs -band -bnot [System.IO.FileAttributes]::ReadOnly)
}
$tempPath = getTempPathOnSameVolume $filePath $tempDir
[IO.File]::Move($filePath, $tempPath)
[IO.File]::Delete($tempPath)
}
function syncRemoveDir([string] $dirPath, [switch] $recursing) {
if (-not $recursing) { $dirPathParent = [IO.Path]::GetDirectoryName($dirPath) }
# Clear the ReadOnly attribute, if present.
# Note: [IO.File]::*Attributes() is also used for *directories*; [IO.Directory] doesn't have attribute-related methods.
if (($attribs = [IO.File]::GetAttributes($dirPath)) -band [System.IO.FileAttributes]::ReadOnly) {
[IO.File]::SetAttributes($dirPath, $attribs -band -bnot [System.IO.FileAttributes]::ReadOnly)
}
# Remove all children synchronously.
$isFirstChild = $true
foreach ($item in [IO.directory]::EnumerateFileSystemEntries($dirPath)) {
if (-not $recursing -and -not $Recurse -and $isFirstChild) { # If -Recurse wasn't specified, prompt for nonempty dirs.
$isFirstChild = $false
# Note: If -Confirm was also passed, this prompt is displayed *in addition*, after the standard $PSCmdlet.ShouldProcess() prompt.
# While Remove-Item also prompts twice in this scenario, it shows the has-children prompt *first*.
if (-not $PSCmdlet.ShouldContinue("The item at '$dirPath' has children and the -Recurse switch was not specified. If you continue, all children will be removed with the item. Are you sure you want to continue?", 'Confirm', ([ref] $yesToAll), ([ref] $noToAll))) { return }
}
$itemPath = [IO.Path]::Combine($dirPath, $item)
([ref] $targetPath).Value = $itemPath
if ([IO.Directory]::Exists($itemPath)) {
syncremoveDir $itemPath -recursing
} else {
syncremoveFile $itemPath $dirPathParent
}
}
# Finally, remove the directory itself synchronously.
([ref] $targetPath).Value = $dirPath
$tempPath = getTempPathOnSameVolume $dirPath $dirPathParent
[IO.Directory]::Move($dirPath, $tempPath)
[IO.Directory]::Delete($tempPath)
}
}
process {
$isLiteral = $PSCmdlet.ParameterSetName -eq 'LiteralPath'
if ($env:OS -ne 'Windows_NT') { # Unix: simply pass through to Remove-Item, which on Unix works reliably and synchronously
Remove-Item @PSBoundParameters
} else { # Windows: use synchronous custom implementation
foreach ($rawPath in ($Path, $LiteralPath)[$isLiteral]) {
# Resolve the paths to full, filesystem-native paths.
try {
# !! Convert-Path does find hidden items via *literal* paths, but not via *wildcards* - and it has no -Force switch (yet)
# !! See https://github.com/PowerShell/PowerShell/issues/6501
$resolvedPaths = if ($isLiteral) { Convert-Path -ErrorAction Stop -LiteralPath $rawPath } else { Convert-Path -ErrorAction Stop -path $rawPath}
} catch {
Write-Error $_ # relay error, but in the name of this function
continue
}
try {
$isDir = $false
foreach ($resolvedPath in $resolvedPaths) {
# -WhatIf and -Confirm support.
if (-not $PSCmdlet.ShouldProcess($resolvedPath)) { continue }
if ($isDir = [IO.Directory]::Exists($resolvedPath)) { # dir.
# !! A trailing '\' or '/' causes directory removal to fail ("in use"), so we trim it first.
syncRemoveDir (trimTrailingPathSep $resolvedPath)
} elseif ([IO.File]::Exists($resolvedPath)) { # file
syncRemoveFile $resolvedPath
} else {
Throw "Not a file-system path or no longer extant: $resolvedPath"
}
}
} catch {
if ($isDir) {
$exc = $_.Exception
if ($exc.InnerException) { $exc = $exc.InnerException }
if ($targetPath -eq $resolvedPath) {
Write-Error "Removal of directory '$resolvedPath' failed: $exc"
} else {
Write-Error "Removal of directory '$resolvedPath' failed, because its content could not be (fully) removed: $targetPath`: $exc"
}
} else {
Write-Error $_ # relay error, but in the name of this function
}
continue
}
}
}
}
}
[1]我已经通过在GitHub issue #27958中运行测试数小时而没有失败，亲自验证了
20H2版本中的问题已解决； this answer建议早于1909版本就解决了该问题，从build 18363.657开始，但是Dinh Tran发现，当删除诸如18363.1316之类的大型目录树时，该问题从node_modules构建开始还没有解决。我找不到有关此主题的任何官方信息。
关于windows - 无法删除项目，目录不为空，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/53553729/