(I don’t like having this option turned on since it creates an unnecessary root folder in an archive if a single folder is zipped)

Create a folder on your desktop called “test” and place two text files in it.

Right-click on the folder and choose “Compress with Options” and click “Add”

At this point you end up with an archive which contains the two text files along with an unnecessary and empty folder structure.

If you were to choose “Compress to “test.zip”” instead, a proper archive is built.

The reason I felt it had to do with password protected files is that I would choose “Compress with Options” to include a password and “Compress to…” otherwise.

Having researched this further, I’ve discovered that when you simply choose “Compress with Options”, you get that issue regardless of whether or not you password protect it as shown in the steps above.

I extracted and recompressed…
Just the WD_Apps_2.0.0.12.dmg to another 7z with same parms, tested fine
Just the WD_Apps_2.0.0.12.dmg with parent folder “WD Apps for Mac” to another 7z with same parms, tested fine
“WD Apps for Mac”. “WD Apps for Windows”, WD Apps Setup.exe" and locks up on “dotNetFx40_Full_x86_x64.exe” when testing so I’m thinking PA has trouble with multiple “WD Apps*.*” items (yes I’m wrong about the DMG theory)
PA 2017 RC2 build 87
Windows 10 Pro x64 RS2

Yes, I guess so. I have edited my post, it should read … source file… (not source folder which was in my initial post) and added 1 pw for all files.
Let’s say it is a bit like when I am searching for all *.txt files in all subfolders, it will find various files in various folders.
Now select the files and rightclick compress to individual, pw-protected .exe files.
(I seldomly use the GUI, only use context menu, is much faster)
Did not check if any other archiver/zipper can do this though.
Later
1. Add examples of batch zip
======[1]=====Adding multiple files to be zipped - note new pw thing==
======[2]=====before and after===
Maybe it could be considered to add a batch zip to exe profile?
(Options->Compression Profiles) and have that added to context menu?
Just a suggestion …
later: maybe this one should be moved to the wishlist part…
=

this is a unrar.dll problem and should be reported in the winrar makers as its ther dll that is fault with the error message. Powerarchiver are only allowed to use the unrar.dll so they are bound by that code, hence the problem.

@spwolf:
not sure that windows xp supports large zips properly, i believe it was added in Vista.
Here is the test release, please check it out and let us know:
http://www.powerarchiver.com/test/release10/powarc116028.exe
thanks!
It FIXED the problem. Tested it with the BAK and VmWare image and both were now OK.
Great…BIG thanks for the quick support….and fix
:):)