You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tree: a324484ef0

ai/coverage-unknowns

ai/gate3-published-rc7-acceptance

ai/release-5.0.0-rc6

ai/test-coverage-assessment

master

test/transfer

4.2.6

4.2.4

4.2.3

5.0.0-rc7

5.0.0-rc6

5.0.0-rc5

5.0.0-rc4

5.0.0-rc3

5.0.0-rc2

5.0.0-rc1

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'a324484ef0'

${ noResults }

NTFSSecurity/NTFSSecurity/LinkCmdlets

History

Raimund Andree a324484ef0 fix: write non-terminating errors from the hard link cmdlets on shares and for folders Windows can't list the names of a file on a network share and answers with (50) The request is not supported. The new live tests found that Get-NTFSHardLink then stopped with a terminating error, so that it skipped the remaining paths, and that New-NTFSHardLink -PassThru did so after it had created the link. A folder stopped Get-NTFSHardLink the same way. Both cmdlets now write a non-terminating GetHardLinkError and go on. The tests reach the sandbox over the administrative share of its drive, which behaves like the share of a file server, and skip where that share isn't available, such as for a basic user. The pages describe the limit on shares. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: AI Assistant <ai@example.com>		4 days ago
..
GetHardLink.cs	fix: write non-terminating errors from the hard link cmdlets on shares and for folders	4 days ago
NewHardLink.cs	fix: write non-terminating errors from the hard link cmdlets on shares and for folders	4 days ago
NewSymbolicLink.cs	fix: bind file and folder objects passed by position as their full path	1 week ago