Windows does not ship with a command line utility to extract ZIP files
If you are trying to unzip something in a bigfix action without any extra downloads or dependencies, then the only real solution is to use VBScript to extract the files.
// Extract ZIP file using VBScript
delete __createfile
createfile until END_OF_FILE
' https://github.com/jgstew/tools/blob/master/VBS/zipExtractSimple.vbs
strOutputDir = "{ pathname of folders "__Download" of client folders of current sites }"
strZipFilePath = "{ pathname of files whose(name of it as lowercase ends with ".zip") of folders "__Download" of client folders of current sites }"
'
CreateObject( "Shell.Application" ).NameSpace( CreateObject("Scripting.FileSystemObject").GetAbsolutePathName( strOutputDir ) ).copyHere ( CreateObject( "Shell.Application" ).NameSpace( CreateObject("Scripting.FileSystemObject").GetAbsolutePathName( strZipFilePath ) ).Items() ), 1044
END_OF_FILE
delete __Download\zipExtractSimple.vbs
copy __createfile __Download\zipExtractSimple.vbs
// Extract Now
waithidden cscript //B //Nologo __Download\zipExtractSimple.vbs
The above actionscript will only work if there is exactly 1 zip file in the downloads folder, but could be modified to handle more. The reason it only works with exactly 1 zip file is that it dynamically looks for a zip file in the downloads folder. The advantage to this approach is that this actionscript can be dropped in and used in any action that involves extracting a single zip file.
I intend to add a bit more error checking to this one. (see the TODO: lines near the end) I use an unnamed parameter for the zip file since it is essential, but if not provided I look for a zip file in the current folder before failing. I used a named parameter for the output folder, but I assume current directory if it is not given.
The simplified one is relying on the relevance to handle the folder output location and zip file existing.