search

maurice-daly / DriverAutomationTool

Home of the Driver Automation Tool
https://www.msendpointmgr.com
BSD 2-Clause "Simplified" License
399 stars 120 forks source link

7-Zip Update #540

Open tstone18 opened 7 months ago

tstone18 commented 7 months ago

Can the 7-Zip.sfx file please be updated to a newer version? Also, it would be great if documentation would be provided on how the file is re-compiled so we can update it ourselves in case there are any vulnerabilities.

Thanks!

stk86WB commented 7 months ago

I second this, it would be nice to be able to update the 7-Zip.sfx file.

40MC commented 6 months ago

The issue is not with the sfx file.

There is a filter added to the 23+ versions of 7-zip:

https://sourceforge.net/p/sevenzip/bugs/2423/

If there is a way to add the -mf- to DAT?

ehousse commented 3 months ago

Line 20262 in DriverAutomationTool.ps1 v7.2.3 $7ZipArgs = "a -sfx7z.sfx DriverPackage.exe -r " + ' "' + $DriverExtractDest + '"'

I don't know if disabling all filters would cause additional issues, since it might leverage the better compression ratio from "BJC2 filter improvements." The issue with Lenovo driver packs is the power management ARM64 folders, I just cleared them in the extracted source files, deleted the completed archive in source, deleted the SCCM object and exe in the destination folder and triggered another Import.

This explains why that actually worked, since the filter wouldn't detect ARM64 executables and wouldn't apply any ARM64 optimizations. Didn't really understand why Lenovo would just randomly plug ARM64 drivers into an enterprise package of models that only had Intel CPUs.

Edit: Looking at some of the other 7-zip posts by Igor on SourceForge, looks like disabling only ARM64 isn't possible, another person tested 7-zip 23.00 https://superuser.com/questions/1792413/on-the-command-line-how-can-i-tell-7-zip-to-disable-the-new-in-23-00-arm64-fil specifically setting BCJ2 specifically. Might give it a try on the latest version.