You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to run this utility, I am getting this error message:
ERROR System.IO.InvalidDataException: Entries larger than 4GB are not supported in Update mode.
at System.IO.Compression.ZipArchive.Init(Stream stream, ZipArchiveMode mode, Boolean leaveOpen)
at System.IO.Compression.ZipFile.Open(String archiveFileName, ZipArchiveMode mode, Encoding entryNameEncoding)
at Microsoft.Management.Service.IntuneWinAppUtil.ZipUtil.CreateFromDirectory(String sourceDirectoryName, String destinationArchiveFileName, Nullable`1 compressionLevel, Boolean includeBaseDirectory, ReportProgress reportProgress, Boolean useExistingZipFile)
at Microsoft.Management.Service.IntuneWinAppUtil.ZipUtil.ZipFolder(String folder, String zipFile, AppContext context, Boolean noCompression, Boolean includeBaseDirectory, Boolean appendFile, Boolean useExistingZipFile)
at Microsoft.Management.Service.IntuneWinAppUtil.PackageUtil.CreatePackage(String folder, String setupFile, String outputFolder, String catalogFolder)
at Microsoft.Management.Service.IntuneWinAppUtil.Program.Main(String[] args)
I'm using version 1.8.6.0 and the total size of the files in the folder are only 2.87 GB in Windows, so I'm not quite sure where it's getting the 4GB error from. I do see the log entry immediately before it starts removing temp files:
INFO Calculated size for folder <...> is 3084957570 within 4 milliseconds
The text was updated successfully, but these errors were encountered:
When trying to run this utility, I am getting this error message:
I'm using version 1.8.6.0 and the total size of the files in the folder are only 2.87 GB in Windows, so I'm not quite sure where it's getting the 4GB error from. I do see the log entry immediately before it starts removing temp files:
INFO Calculated size for folder <...> is 3084957570 within 4 milliseconds
The text was updated successfully, but these errors were encountered: