This extracts the zip file to a new directory “My_Extraction_Folder” beneath the __Download folder, and saves a detailed log of the extraction process to extraction_log.txt.
PowerShell can extract zips on its own, but I’ve found the easiest way to capture the terminal output is to wrap the PowerShell command in a cmd.exe shell.
Thanks for the tip! I wasn’t aware of that.
The archive I’m dealing with is 10 GB total but none of the individual files in the archive are that large.
For anyone hitting that ceiling, I've found that using the .NET class [System.IO.Compression.ZipFile]::ExtractToDirectory in the same PowerShell block often bypasses those legacy limitations, provided the target has a modern version of .NET