Progress during large file copy (Copy-Item & Write-Progress?)

Question

Is there any way to copy a really large file (from one server to another) in PowerShell AND display its progress?

There are solutions out there to use Write-Progress in conjunction with looping to copy many files and display progress. However I can't seem to find anything that would show progress of a single file.

Any thoughts?

Nacht · Answer 1 · 2016-12-21T22:06:31.127

122

It seems like a much better solution to just use BitsTransfer, it seems to come OOTB on most Windows machines with PowerShell 2.0 or greater.

Import-Module BitsTransfer
Start-BitsTransfer -Source $Source -Destination $Destination -Description "Backup" -DisplayName "Backup"

edited Dec 21 '16 at 22:06

answered Sep 09 '14 at 01:17

Nacht

3,140
3
24
39

Great! Indeed, this also gives me a (powershell) progress indicator. – mousio Nov 24 '14 at 10:33
it wouldn't probably leverages BITS capabilities if you are not pulling source from remote location, but it works smooth. – mCasamento Mar 07 '15 at 16:04
4

Exactly what I was after- worked perfectly and gives a progress bar! – Shawson Jan 04 '16 at 12:44
I used this to copy VMs around in 2012 R2 Hyper-V free. – johnny Aug 26 '16 at 22:01
I'm using this on a Hyper-V Server with minimal GUI and it works great! – MemphiZ Dec 05 '16 at 15:25
3

This should be the top answer. – tyteen4a03 Sep 06 '17 at 14:32
Does not work with Powershell Core 6.1.0 at least. I get an import error saying "BitsTransfer.psd1 does not support current PowerShell edition 'Core'" – Manuzor Dec 06 '18 at 09:39
1

Strangely, when I run the command, nothing at all happens with no output? I use for example -Source "\\comp1\c$\folder" -Destionation "\\comp2\c$\folder" , any idea what could be wrong? I have access to both folders, no issue there. If I use copy-item it works but with no progress obviously. – Rakha Mar 29 '19 at 14:04
In Ps 5.1 I get: `user is not registered in Network.` I copy from Network share. I use the 2 Parameters `source` and `Destination`. – Timo Aug 07 '19 at 10:18

score 51 · Accepted Answer · edited Jul 31 '20 at 01:48

51

I haven't heard about progress with Copy-Item. If you don't want to use any external tool, you can experiment with streams. The size of buffer varies, you may try different values (from 2kb to 64kb).

function Copy-File {
    param( [string]$from, [string]$to)
    $ffile = [io.file]::OpenRead($from)
    $tofile = [io.file]::OpenWrite($to)
    Write-Progress -Activity "Copying file" -status "$from -> $to" -PercentComplete 0
    try {
        [byte[]]$buff = new-object byte[] 4096
        [long]$total = [int]$count = 0
        do {
            $count = $ffile.Read($buff, 0, $buff.Length)
            $tofile.Write($buff, 0, $count)
            $total += $count
            if ($total % 1mb -eq 0) {
                Write-Progress -Activity "Copying file" -status "$from -> $to" `
                   -PercentComplete ([long]($total * 100 / $ffile.Length))
            }
        } while ($count -gt 0)
    }
    finally {
        $ffile.Dispose()
        $tofile.Dispose()
        Write-Progress -Activity "Copying file" -Status "Ready" -Completed
    }
}

edited Jul 31 '20 at 01:48

VeeTheSecond

3,016
3
19
16

answered Mar 12 '10 at 21:47

stej

27,607
11
68
102

6

Interesting solution. When I tried it I received an error - Cannot convert value "2147483648" to type "System.Int32". Error: "Value was either too large or too small for an Int32." After replacing the [int] to a [long], it worked great. Thanks – Jason Jarrett Mar 23 '10 at 13:44
That means that you copy files bigger than 2GB? I guess so. I'm glad it works :) – stej Mar 23 '10 at 14:23
+1 simple solutions are best! Am copying big (8GB+) files across from one network location to another ... gigabit network ... (*indication only*) ... using blocks of 1Mb means network adapter runs at about 50% (I suspect some throttling on our switch) ... smaller blocks weren't great though. – Aidanapword Mar 11 '13 at 11:09
1

Small .NETy gripe: the finally should call Dispose() rather than Close(). Good solution though. I'm sad there's no built-in progress available. – TheXenocide May 07 '13 at 15:59
Right, missing using statement in PowerShell :) – stej May 09 '13 at 13:09
@TheXenocide Why? Stream.Close() just calls Stream.Dispose()? http://referencesource.microsoft.com/#mscorlib/system/io/stream.cs – Keith Hill Sep 25 '14 at 00:00
That's right, but basically whenever the object is IDisposable, I call Dispose(). Imo it's safer and also you don't need to know the internals. – stej Sep 25 '14 at 16:33
5

Well, this is more of a programming quip than a scripting one (if you choose to differentiate), but from a computer science point of view: you are relying on internal implementation details of an object which are not guaranteed and can change at any time, and additionally not following an established pattern for the public contract. This both violates a primary tenant of object oriented design and also ignores the public IDisposable contract (which you *are* supposed to know exists) that has well established best practices that state it should always be disposed. – TheXenocide Sep 25 '14 at 18:37
You should replace the `[io.file]::OpenWrite($to)` to `[io.file]::Create($to)` otherwise it will not overwrite files properly. – Scott Chamberlain Oct 16 '15 at 16:29
What does it mean "properly"? – stej Oct 22 '15 at 05:33
If anyone is trying to get this to work with a PSDrive you'll want to change $ffile initialization to (Get-ChildItem $from).OpenRead() and the $tofile initialization to (new-item $to -Type File -Force).OpenWrite() – Nick May 18 '17 at 13:52
I changed the [int]$total into [long]$total to take large files into account, like Jason suggested. – VeeTheSecond Jul 31 '20 at 01:49

score 30 · Answer 3 · edited Jul 13 '12 at 11:19

30

Alternativly this option uses the native windows progress bar...

$FOF_CREATEPROGRESSDLG = "&H0&"

$objShell = New-Object -ComObject "Shell.Application"

$objFolder = $objShell.NameSpace($DestLocation) 

$objFolder.CopyHere($srcFile, $FOF_CREATEPROGRESSDLG)

edited Jul 13 '12 at 11:19

Tisho

7,870
6
42
52

answered Jul 13 '12 at 10:10

Chris M

301
3
2

1

This is brilliant, how do you specify the "ALWAYS OVERWRITE" flag for this method, is it possible? So it doesn't prompt when files exist. – Rakha Jun 06 '19 at 18:39
@Rakha you just need to pass 16 as sec param to CopyHere function like this: `$objFolder.CopyHere($srcFile, 16)` – R‌‌‌.. Jul 17 '21 at 04:37

score 29 · Answer 4 · edited Apr 04 '18 at 08:51

29

cmd /c copy /z src dest

not pure PowerShell, but executable in PowerShell and it displays progress in percents

edited Apr 04 '18 at 08:51

wonea

4,425
17
82
137

answered Jan 05 '15 at 13:38

Jirka Jr.

401
4
3

Great answer. I also used [this answer](https://stackoverflow.com/a/31015007/4163002) to output progress. – ZX9 Jan 07 '20 at 20:04

score 17 · Answer 5 · edited Mar 19 '14 at 13:00

17

I amended the code from stej (which was great, just what i needed!) to use larger buffer, [long] for larger files and used System.Diagnostics.Stopwatch class to track elapsed time and estimate time remaining.

Also added reporting of transfer rate during transfer and outputting overall elapsed time and overall transfer rate.

Using 4MB (4096*1024 bytes) buffer to get better than Win7 native throughput copying from NAS to USB stick on laptop over wifi.

On To-Do list:

add error handling (catch)
handle get-childitem file list as input
nested progress bars when copying multiple files (file x of y, % if total data copied etc)
input parameter for buffer size

Feel free to use/improve :-)

function Copy-File {
param( [string]$from, [string]$to)
$ffile = [io.file]::OpenRead($from)
$tofile = [io.file]::OpenWrite($to)
Write-Progress `
    -Activity "Copying file" `
    -status ($from.Split("\")|select -last 1) `
    -PercentComplete 0
try {
    $sw = [System.Diagnostics.Stopwatch]::StartNew();
    [byte[]]$buff = new-object byte[] (4096*1024)
    [long]$total = [long]$count = 0
    do {
        $count = $ffile.Read($buff, 0, $buff.Length)
        $tofile.Write($buff, 0, $count)
        $total += $count
        [int]$pctcomp = ([int]($total/$ffile.Length* 100));
        [int]$secselapsed = [int]($sw.elapsedmilliseconds.ToString())/1000;
        if ( $secselapsed -ne 0 ) {
            [single]$xferrate = (($total/$secselapsed)/1mb);
        } else {
            [single]$xferrate = 0.0
        }
        if ($total % 1mb -eq 0) {
            if($pctcomp -gt 0)`
                {[int]$secsleft = ((($secselapsed/$pctcomp)* 100)-$secselapsed);
                } else {
                [int]$secsleft = 0};
            Write-Progress `
                -Activity ($pctcomp.ToString() + "% Copying file @ " + "{0:n2}" -f $xferrate + " MB/s")`
                -status ($from.Split("\")|select -last 1) `
                -PercentComplete $pctcomp `
                -SecondsRemaining $secsleft;
        }
    } while ($count -gt 0)
$sw.Stop();
$sw.Reset();
}
finally {
    write-host (($from.Split("\")|select -last 1) + `
     " copied in " + $secselapsed + " seconds at " + `
     "{0:n2}" -f [int](($ffile.length/$secselapsed)/1mb) + " MB/s.");
     $ffile.Close();
     $tofile.Close();
    }
}

edited Mar 19 '14 at 13:00

Chris J

29,695
5
65
106

answered Dec 01 '12 at 11:24

Graham Gold

2,397
2
24
34

Nice script, but it gives a divide by zero. I had to add: if ( $secselapsed -ne 0 ) { [single]$xferrate = (($total/$secselapsed)/1mb); } else { [single]$xferrate = 0.0 } – 79E09796 Jun 20 '13 at 10:11
Not something I've come across in my daily use of this code, what powershell version are you using? Does it ever work for you? Just curious. Anything that makes it more robust is fine by me :-) – Graham Gold Jun 21 '13 at 23:12
On Powershell 2.0.1.1 it did work intermittently, but most times not. It seemed it might be copying the first block too fast and then rounding down the $secelapsed. I've put in the update, might save someone some time. Thanks again, it's a useful script. – 79E09796 Jun 25 '13 at 08:39
I owe @stej for the original code that I adapted, but thanks :-) – Graham Gold Jun 25 '13 at 10:39
Nice script, but the divide by zero error is in the line: "{0:n2}" -f [int](($ffile.length/$secselapsed)/1mb) + " MB/s."); You check for $secselapsed -eq 0 up above in the script, but don't at that point. – Sako73 Mar 03 '15 at 02:05
You should replace the `[io.file]::OpenWrite($to)` to `[io.file]::Create($to)` otherwise it will not overwrite files properly. – Scott Chamberlain Oct 16 '15 at 16:29
@ScottChamberlain never had a single overwrite fail with the `::OpenWrite` method yet but will bear that in mind if I do – Graham Gold Oct 18 '15 at 15:12
@GrahamGold Copy a file, then copy a 2nd file with the same name but a smaller filesize. The resultant file will have the end of the first file tacked on after the end of the 2nd file. – Scott Chamberlain Oct 18 '15 at 15:17
@ScottChamberlain explains why I wouldn't hit it in my usage of the above code - that scenario isn't possible in the script where I use it, if overwrite option is chosen at runtime then each file existing file is renamed as a temp file name before new file copied then temp file removed on completion of copy. – Graham Gold Oct 18 '15 at 15:22
How do I get Start-BitsTransfer (really, Write-Progress) to log updates as text to standard output instead of just the PowerShell progress bar? – John Zabroski Feb 12 '18 at 20:04

Keith Hill · Answer 6 · 2010-03-12T22:42:01.220

9

Not that I'm aware of. I wouldn't recommend using copy-item for this anyway. I don't think it has been designed to be robust like robocopy.exe to support retry which you would want for extremely large file copies over the network.

edited Mar 12 '10 at 22:42

answered Mar 12 '10 at 18:39

Keith Hill

184,219
38
329
358

1

Valid point. In this particular case I'm not too worried about robustness. It's copying a 15gig file between two servers on the same back-plane. However in other situations I would definitely consider a more robust solution. – Jason Jarrett Mar 23 '10 at 13:28

score 4 · Answer 7 · edited Jan 30 '21 at 02:45

Hate to be the one to bump an old subject, but I found this post extremely useful. After running performance tests on the snippets by stej and it's refinement by Graham Gold, plus the BITS suggestion by Nacht, I have decuded that:

I really liked Graham's command with time estimations and speed readings.
I also really liked the significant speed increase of using BITS as my transfer method.

Faced with the decision between the two... I found that Start-BitsTransfer supported Asynchronous mode. So here is the result of my merging the two.

function Copy-File {
    # ref: https://stackoverflow.com/a/55527732/3626361
    param([string]$From, [string]$To)

    try {
        $job = Start-BitsTransfer -Source $From -Destination $To `
            -Description "Moving: $From => $To" `
            -DisplayName "Backup" -Asynchronous

        # Start stopwatch
        $sw = [System.Diagnostics.Stopwatch]::StartNew()
        Write-Progress -Activity "Connecting..."

        while ($job.JobState.ToString() -ne "Transferred") {
            switch ($job.JobState.ToString()) {
                "Connecting" {
                    break
                }
                "Transferring" {
                    $pctcomp = ($job.BytesTransferred / $job.BytesTotal) * 100
                    $elapsed = ($sw.elapsedmilliseconds.ToString()) / 1000

                    if ($elapsed -eq 0) {
                        $xferrate = 0.0
                    }
                    else {
                        $xferrate = (($job.BytesTransferred / $elapsed) / 1mb);
                    }

                    if ($job.BytesTransferred % 1mb -eq 0) {
                        if ($pctcomp -gt 0) {
                            $secsleft = ((($elapsed / $pctcomp) * 100) - $elapsed)
                        }
                        else {
                            $secsleft = 0
                        }

                        Write-Progress -Activity ("Copying file '" + ($From.Split("\") | Select-Object -last 1) + "' @ " + "{0:n2}" -f $xferrate + "MB/s") `
                            -PercentComplete $pctcomp `
                            -SecondsRemaining $secsleft
                    }
                    break
                }
                "Transferred" {
                    break
                }
                Default {
                    throw $job.JobState.ToString() + " unexpected BITS state."
                }
            }
        }

        $sw.Stop()
        $sw.Reset()
    }
    finally {
        Complete-BitsTransfer -BitsJob $job
        Write-Progress -Activity "Completed" -Completed
    }
}

Justin · Answer 8 · 2020-02-23T02:24:57.500

i found none of the examples above met my needs, i wanted to copy a directory with sub directories, the problem is my source directory had too many files so i quickly hit the BITS file limit (i had > 1500 file) also the total directory size was quite large.

i found a function using robocopy that was a good starting point at https://keithga.wordpress.com/2014/06/23/copy-itemwithprogress/, however i found it wasn't quite robust enough, it didn't handle trailing slashes, spaces gracefully and did not stop the copy when the script was halted.

Here is my refined version:

function Copy-ItemWithProgress
{
    <#
    .SYNOPSIS
    RoboCopy with PowerShell progress.

    .DESCRIPTION
    Performs file copy with RoboCopy. Output from RoboCopy is captured,
    parsed, and returned as Powershell native status and progress.

    .PARAMETER Source
    Directory to copy files from, this should not contain trailing slashes

    .PARAMETER Destination
    DIrectory to copy files to, this should not contain trailing slahes

    .PARAMETER FilesToCopy
    A wildcard expresion of which files to copy, defaults to *.*

    .PARAMETER RobocopyArgs
    List of arguments passed directly to Robocopy.
    Must not conflict with defaults: /ndl /TEE /Bytes /NC /nfl /Log

    .PARAMETER ProgressID
    When specified (>=0) will use this identifier for the progress bar

    .PARAMETER ParentProgressID
    When specified (>= 0) will use this identifier as the parent ID for progress bars
    so that they appear nested which allows for usage in more complex scripts.

    .OUTPUTS
    Returns an object with the status of final copy.
    REMINDER: Any error level below 8 can be considered a success by RoboCopy.

    .EXAMPLE
    C:\PS> .\Copy-ItemWithProgress c:\Src d:\Dest

    Copy the contents of the c:\Src directory to a directory d:\Dest
    Without the /e or /mir switch, only files from the root of c:\src are copied.

    .EXAMPLE
    C:\PS> .\Copy-ItemWithProgress '"c:\Src Files"' d:\Dest /mir /xf *.log -Verbose

    Copy the contents of the 'c:\Name with Space' directory to a directory d:\Dest
    /mir and /XF parameters are passed to robocopy, and script is run verbose

    .LINK
    https://keithga.wordpress.com/2014/06/23/copy-itemwithprogress

    .NOTES
    By Keith S. Garner (KeithGa@KeithGa.com) - 6/23/2014
    With inspiration by Trevor Sullivan @pcgeek86
    Tweaked by Justin Marshall - 02/20/2020

    #>

    [CmdletBinding()]
    param(
        [Parameter(Mandatory=$true)]
        [string]$Source,
        [Parameter(Mandatory=$true)]
        [string]$Destination,
        [Parameter(Mandatory=$false)]
        [string]$FilesToCopy="*.*",
        [Parameter(Mandatory = $true,ValueFromRemainingArguments=$true)] 
        [string[]] $RobocopyArgs,
        [int]$ParentProgressID=-1,
        [int]$ProgressID=-1
    )

    #handle spaces and trailing slashes
    $SourceDir = '"{0}"' -f ($Source -replace "\\+$","")
    $TargetDir = '"{0}"' -f ($Destination -replace "\\+$","")


    $ScanLog  = [IO.Path]::GetTempFileName()
    $RoboLog  = [IO.Path]::GetTempFileName()
    $ScanArgs = @($SourceDir,$TargetDir,$FilesToCopy) + $RobocopyArgs + "/ndl /TEE /bytes /Log:$ScanLog /nfl /L".Split(" ")
    $RoboArgs = @($SourceDir,$TargetDir,$FilesToCopy) + $RobocopyArgs + "/ndl /TEE /bytes /Log:$RoboLog /NC".Split(" ")

    # Launch Robocopy Processes
    write-verbose ("Robocopy Scan:`n" + ($ScanArgs -join " "))
    write-verbose ("Robocopy Full:`n" + ($RoboArgs -join " "))
    $ScanRun = start-process robocopy -PassThru -WindowStyle Hidden -ArgumentList $ScanArgs
    try
    {
        $RoboRun = start-process robocopy -PassThru -WindowStyle Hidden -ArgumentList $RoboArgs
        try
        {
            # Parse Robocopy "Scan" pass
            $ScanRun.WaitForExit()
            $LogData = get-content $ScanLog
            if ($ScanRun.ExitCode -ge 8)
            {
                $LogData|out-string|Write-Error
                throw "Robocopy $($ScanRun.ExitCode)"
            }
            $FileSize = [regex]::Match($LogData[-4],".+:\s+(\d+)\s+(\d+)").Groups[2].Value
            write-verbose ("Robocopy Bytes: $FileSize `n" +($LogData -join "`n"))
            #determine progress parameters
            $ProgressParms=@{}
            if ($ParentProgressID -ge 0) {
                $ProgressParms['ParentID']=$ParentProgressID
            }
            if ($ProgressID -ge 0) {
                $ProgressParms['ID']=$ProgressID
            } else {
                $ProgressParms['ID']=$RoboRun.Id
            }
            # Monitor Full RoboCopy
            while (!$RoboRun.HasExited)
            {
                $LogData = get-content $RoboLog
                $Files = $LogData -match "^\s*(\d+)\s+(\S+)"
                if ($null -ne $Files )
                {
                    $copied = ($Files[0..($Files.Length-2)] | ForEach-Object {$_.Split("`t")[-2]} | Measure-Object -sum).Sum
                    if ($LogData[-1] -match "(100|\d?\d\.\d)\%")
                    {
                        write-progress Copy -ParentID $ProgressParms['ID'] -percentComplete $LogData[-1].Trim("% `t") $LogData[-1]
                        $Copied += $Files[-1].Split("`t")[-2] /100 * ($LogData[-1].Trim("% `t"))
                    }
                    else
                    {
                        write-progress Copy -ParentID $ProgressParms['ID'] -Complete
                    }
                    write-progress ROBOCOPY  -PercentComplete ($Copied/$FileSize*100) $Files[-1].Split("`t")[-1] @ProgressParms
                }
            }
        } finally {
            if (!$RoboRun.HasExited) {Write-Warning "Terminating copy process with ID $($RoboRun.Id)..."; $RoboRun.Kill() ; }
            $RoboRun.WaitForExit()
            # Parse full RoboCopy pass results, and cleanup
            (get-content $RoboLog)[-11..-2] | out-string | Write-Verbose
            remove-item $RoboLog
            write-output ([PSCustomObject]@{ ExitCode = $RoboRun.ExitCode })

        }
    } finally {
        if (!$ScanRun.HasExited) {Write-Warning "Terminating scan process with ID $($ScanRun.Id)..."; $ScanRun.Kill() }
        $ScanRun.WaitForExit()

        remove-item $ScanLog
    }
}

score 3 · Answer 9 · edited Jun 20 '20 at 09:12

This recursive function copies files and directories recursively from source path to destination path

If file already exists on destination path, it copies them only with newer files.

Function Copy-FilesBitsTransfer(
        [Parameter(Mandatory=$true)][String]$sourcePath, 
        [Parameter(Mandatory=$true)][String]$destinationPath, 
        [Parameter(Mandatory=$false)][bool]$createRootDirectory = $true)
{
    $item = Get-Item $sourcePath
    $itemName = Split-Path $sourcePath -leaf
    if (!$item.PSIsContainer){ #Item Is a file

        $clientFileTime = Get-Item $sourcePath | select LastWriteTime -ExpandProperty LastWriteTime

        if (!(Test-Path -Path $destinationPath\$itemName)){
            Start-BitsTransfer -Source $sourcePath -Destination $destinationPath -Description "$sourcePath >> $destinationPath" -DisplayName "Copy Template file" -Confirm:$false
            if (!$?){
                return $false
            }
        }
        else{
            $serverFileTime = Get-Item $destinationPath\$itemName | select LastWriteTime -ExpandProperty LastWriteTime

            if ($serverFileTime -lt $clientFileTime)
            {
                Start-BitsTransfer -Source $sourcePath -Destination $destinationPath -Description "$sourcePath >> $destinationPath" -DisplayName "Copy Template file" -Confirm:$false
                if (!$?){
                    return $false
                }
            }
        }
    }
    else{ #Item Is a directory
        if ($createRootDirectory){
            $destinationPath = "$destinationPath\$itemName"
            if (!(Test-Path -Path $destinationPath -PathType Container)){
                if (Test-Path -Path $destinationPath -PathType Leaf){ #In case item is a file, delete it.
                    Remove-Item -Path $destinationPath
                }

                New-Item -ItemType Directory $destinationPath | Out-Null
                if (!$?){
                    return $false
                }

            }
        }
        Foreach ($fileOrDirectory in (Get-Item -Path "$sourcePath\*"))
        {
            $status = Copy-FilesBitsTransfer $fileOrDirectory $destinationPath $true
            if (!$status){
                return $false
            }
        }
    }

    return $true
}

score 1 · Answer 10 · edited Apr 04 '18 at 08:52

1

Trevor Sullivan has a write-up on how to add a command called Copy-ItemWithProgress to PowerShell on Robocopy.

edited Apr 04 '18 at 08:52

wonea

4,425
17
82
137

answered Apr 20 '16 at 10:14

Wouter

2,082
27
57

score 1 · Answer 11 · answered Jan 08 '18 at 21:45

Sean Kearney from the Hey, Scripting Guy! Blog has a solution I found works pretty nicely.

Function Copy-WithProgress
{
    [CmdletBinding()]
    Param
    (
        [Parameter(Mandatory=$true,
            ValueFromPipelineByPropertyName=$true,
            Position=0)]
        $Source,
        [Parameter(Mandatory=$true,
            ValueFromPipelineByPropertyName=$true,
            Position=0)]
        $Destination
    )

    $Source=$Source.tolower()
    $Filelist=Get-Childitem "$Source" –Recurse
    $Total=$Filelist.count
    $Position=0

    foreach ($File in $Filelist)
    {
        $Filename=$File.Fullname.tolower().replace($Source,'')
        $DestinationFile=($Destination+$Filename)
        Write-Progress -Activity "Copying data from '$source' to '$Destination'" -Status "Copying File $Filename" -PercentComplete (($Position/$total)*100)
        Copy-Item $File.FullName -Destination $DestinationFile
        $Position++
    }
}

Then to use it:

Copy-WithProgress -Source $src -Destination $dest

This will report the number of files copied in `$Filelist`, whereas the question is asking how to report the progress of copying a single file (i.e. the count of bytes/blocks copied thus far). If this code were used to copy a single, large file it would give no indication how far the copy operation has progressed within that file. From the question body: "There are solutions out there to use Write-Progress in conjunction with looping to copy many files and display progress. However I can't seem to find anything that would show progress of a single file." — Lance U. Matthews, May 16 '18 at 01:40

Progress during large file copy (Copy-Item & Write-Progress?)

11 Answers11

This recursive function copies files and directories recursively from source path to destination path

If file already exists on destination path, it copies them only with newer files.

Linked