-
In the latest version of PA, on W11 (latest build/SP) when you try to use the first level context menu - NOTHING HAPPENS (particularly when you do this from Downloads or Documents folders) - however I noticed that it DOES WORK when you use the context menu from the Desktop. Going to the second level context menu does work however.
-
PA 2023 22.00.08
Long time no seeing. So I start up the new year with a first problem : the virtual driver cannot be installed. Reason : it is missing in the Fast Ring PatchBeam Update Service…
Virtual driver PA 2023-01-28 152607.png
It seems a standard problem with new releases :-)
Can I have a link or can it be fixed. Thank you. CU later -
When the function for testing archives is invoked via the shell context menu (PowerArchiver > Test) then all the files in the archive get extracted to the current folder.
The test dialog reports as many errors as there are files in the archive but it fails to give any hint as to which files are supposed to be erroneous or what the nature of the problem might be. Comparing the extracted files to the originals shows no differences at all.
The .7z in question was produced with maximised compression settings in 7zip (taking forever but resulting in smaller archives than .7z produced by PowerArchiver with maximised settings). Therefore I wanted to see whether PowerArchiver can at least test .7z that it produced itself. Hence I had PowerArchiver convert a .pa with the same contents to .7z. There weren’t any errors reported but the resulting .7z contained fewer than half of the files contained in the .pa (137 of 366), so I scratched that test.
Performance is abysmal when testing via the context menu (e.g. almost 2 minutes for testing a .7z that 7zip tests in 4 seconds), but that is most likely due to the fact that the extracted files are written to disk. Testing the same .7z in the PowerArchiver GUI takes only 8 seconds but causes the mysterious appearance of a UAC dialog, as reported elsewhere.
The testing function is vital because PowerArchiver has a history of producing archives that it cannot unpack without errors or that do not conform to the respective file format standards (e.g. ZIP) so that other programs report them as erroneous.
The point of creating archives is that the files in them will most likely have to be extracted at some point. If the extraction cannot be guaranteed to produce correct results then the whole program is absolutely pointless. Actually, worse than pointless - it causes data loss and hence damage.
-
In PowerArchiver 2023 22.00.06 configuration, the option labelled “Start PowerArchiver 2023 Starter when my computer starts” seems to be redundant.
I am only allowed to change this option when PA Starter is disabled, and then it seems to be ignored.
When I enable PA Starter this option is forced to the enabled state.
I think it’d be good to remove “Start PowerArchiver 2023 Starter when my computer starts” completely. I’ve always found it confusing having both options.
Added later: However i don’t particularly want to use queue but I do like having the PAStarter icon in my tray area.
-
W10 Pro 22H2 - 64 -bit
PA 22.00.06 (PA 2023)
It has been the case with previous versions of PowerArchiver, but I had hoped that the latest might behave differently. Not so, I’m afraid.
I have, for various obscure reasons, created a few .pa archives, mainly in the hope that they will save me some more space. From time to time, I use the “Test” option to check that important archives are OK and uncorrupted.
With every .pa archive I’ve tested, the process runs through OK but then reports that there are errors. This is always the number of files in the archive e.g. if 11 files, then 11 errors reported.
In the .pa, I can:-
preview the files (usually PDF) extract some or all files and look at or use them convert the .pa to a .zip or .zipx archive, which then works fine and tests without errorsIs it the case that the Test routine isn’t designed for .pa archives, or is there another reason? Although the .pa seems to function properly, despite the test reporting errors, I would like to be sure that every .pa is OK and not “broken”.
Some of the .pas are quite old and produced with earlier PA versions (they are truly “archives”). If I extract all the files in the old .pa, create a new, fresh .pa and add back the files to that, then test the new, no errors (at least in the .pa I’ve tried this on) are reported. This would suggest a mismatch between old .pas and newer versions of PA itself.
-
-
Clipboard02.jpg
See the, supposedly, blank space where the green box is? It’s like that in Modern Light theme too. I can toggle it, but it’s missing text or shouldn’t be there I guess?
Thanks :)
-
Dear @Alpha-Testers and all of our users,
time has come for testing of PowerArchiver and PACL for macOS.
Please let us know here if you have Mac and can test latest builds.Features implemented:
PowerArchiver 2020 - tabbing, opening, extracting, adding, testing, favorite folders, support for multiple languages, opening via Finder, explorer mode, installer.
PACL 10 - support for most formats and features in Windows version.Upcoming: Tools such as archive converter, batch zip, multi-extract.
To start testing, please sign up here in this thread, and we will send you latest build.
thank you!
Ashampoo_Snap_Wednesday, November 20, 2019_12h54m56s_008_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m05s_009_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m14s_010_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m30s_011_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m39s_012_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m49s_013_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h56m00s_014_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h54m43s_007_.png
76e97ab9-8d75-4175-9ce8-446500031f38-image.png
-
For some reason, the PowerArchiver functions in the Windows 11 context menu no longer work after the last Windows Update. Only the functions in the classic context menu function as they should.
I’ve tried uninstalling PowerArchiver and using RevoUninstaller to remove all bits and pieces that were left behind and did a clean install of PowerArchiver, it didn’t fix the issue. Other items in the Windows 11 context menu work.
Wiping temp files after decrypting
-
I want to be sure of one thing . . . and I could not find an answer in the help file. Sorry if I missed it.
Suppose I have an encrypted archive (any form of encryrption). I open the archive to look at one file.
Does PA WIPE the temporary file after I close the encrypted file?
If not, could this be added?
Hugh
-
Yes.
Wasn’t 100% sure but I just tested it and once I closed PA the temp file was deleted from the temp folder.
-
Thanks, Luxor,
I want to make sure sure, though, of two things.
(1) is the file deleted or is it wiped?
(2) If so, Is this something done by default on encrypted files, or is there some special setting.Best,
-
Thanks, Luxor,
I want to make sure sure, though, of two things.
(1) is the file deleted or is it wiped?
Deleted as far as I know. spwolf will hopefully tell us if it is wiped. I have my doubts about that but I don’t know enough to know for sure.
@Socrates:(2) If so, Is this something done by default on encrypted files, or is there some special setting.
Best,
It’s by default would be my answer. But again let’s wait for spwolf or one of the other devs for the definitive answer. :)
-
Thanks, Luxor,
I want to make sure sure, though, of two things.
(1) is the file deleted or is it wiped?
(2) If so, Is this something done by default on encrypted files, or is there some special setting.Best,
it is currently deleted, not wiped… wiped would mean data was overwritten by zeroes several times.
-
it is currently deleted, not wiped… wiped would mean data was overwritten by zeroes several times.
Maybe it’s worth adding that to the request list. for Pro and Toolbox users.
Goverment Wiped Temp’s made from PA.
However, for the users who are wanting to wipe this data if you download a free app called CCleaner it has multiple wiping options and customisable locations to add.
PowerArchiver has the ability to custom the location of temp files you can change this in the config screen.
Until the team have made something that wipes data whenever that will be you could use my suggestion.
-
Sir Richard always tries to limit our PA Standard users, bad Richard, bad! :-)
-
it is currently deleted, not wiped… wiped would mean data was overwritten by zeroes several times.
Not just zeroes, though ;)
-
Sir Richard always tries to limit our PA Standard users, bad Richard, bad! :-)
I just think that a feature such as Goverment Wiping is more towards end users who are heavy users and use things like encryption, backup etc more than most.
So pro and toolbox falls into line.
dont get me wrong, if you want to offer it for all then good on you ;) i keep coming up with increasing your sales for Pro + and you keep knocking me down. LOL
-
@Sir:
I just think that a feature such as Goverment Wiping is more towards end users who are heavy users and use things like encryption, backup etc more than most.
So pro and toolbox falls into line.
dont get me wrong, if you want to offer it for all then good on you ;) i keep coming up with increasing your sales for Pro + and you keep knocking me down. LOL
government wiping? sounds like the feds will be soon all over us :-).
-
lol, As long as you have me on your team i’ll keep them pesky feds at bay :)
-
I often keep private correspondence and financial files in encrypted archives.
I am trying to understand precisely how PA handles both the creation and extraction of the constituent files. I would prefer to leave no residue of said files floating around as flotsam and jetsam on the hard drive.
I have software that will wipe files – if I know precisely where those files are. However, if PA deletes but does not wipe a file, then I am not sure how I can properly wipe it.
Relatedly . . . if I include the setting that says “use the current file as the temp file” does that mean that all files used to build the archive, AND all files extracted from said archive will be in the current folder? That might make my task easier.
And how does THIS setting supplement, override, or compete with the temp file location setting?
Perhaps one solution is to just not have PA ever create temp files, at least not for encrypted archives.
No rush on an answer . . . I am just trying to better understand my options.
-
best option would be for us to wipe (overwrite the data and then delete) it :-).
few people have asked about it already so it will probably come soon enough.
-
best option would be for us to wipe (overwrite the data and then delete) it :-).
few people have asked about it already so it will probably come soon enough.
Dam rite! another good thing for those concirned about Securing their data without the added hassle of additional software.
I have a few archives containing documents with confidential info, they are of course encrypted, but i always wipe the Temp location after i have finished with certain tools available.
However, if PA offered a FIPS wipe method that would be boss!
-
it would be nice on the same level to have the files put in a folder that cannot be opened except through powerarchiver and with there original password. cause once its in the temp file anyone on a network computer can read your temp file and copy the files.
just an idea
-
best option would be for us to wipe (overwrite the data and then delete) it :-).
few people have asked about it already so it will probably come soon enough.
That would be great. I now use FileEncyption XL to handle my most sensivitive data (including PA archives) since (a) it doesn’t create a temp file, and (b) it has an option to wipe files that are included in encyrpted files, and those extracted from encrypted files. So if PA had this, I could dump the other program.
Still, I know PA cannot do everything – you must pick choose. So this is just a wish . . … nothing more.
-
added wiping to 12.5 beta… to be released this week… thanks for the suggestion.
-
I am impressed. Look forward to seeing it.
I assume it will be upgradable via PatchBeam.
I also assume that you will let us know if you want us to alpha test ZTE.
-
added wiping to 12.5 beta… to be released this week… thanks for the suggestion.
This is fantastic news! It’s a good step forward with the significant steps forward within the security aspects only recently introduced into the PA Suite… ie FTP; Backup and Encryption options being FIPS Validated.
Now Wiping on Temp’s, this is something the competitors DONT do!
Without being pushy! and accepting its not a fully finished product, is there an option to verify the number of writes made like you would have in CCleaner, or steganos etc etc or is it a preset number?
Ideally if PA could have a Quick, Secure & Paranoid mode or custom wipes and detail of what that means then that too would be another fantastic feature… It also means you are ticking many firm’s buttons when it comes to wipe options regarding confidential archives.
-
there are options: 1, 3 and 7 passes, based on that DoD 5220.22-M standard/suggestion. Is that what you meant Richard?
-
there are options: 1, 3 and 7 passes, based on that DoD 5220.22-M standard/suggestion. Is that what you meant Richard?
:) Yes! that is exactly what i meant and is exactly what the security conscious user want’s see!
Thank you Drazen! Thank you ConeXware
-
Just to confirm that a recent update to PA that resolve’s ISO Driver’s also contains the 1st ever Wipe Facility for Archive’s…
http://www.powerarchiver.com/test/alpha120/powarc125003.exeAlthough, this is a very new feature and I am sure there may be possible bugs and improvments it would be nice to get some feedback and possible feature requests. Remember that this is a Archive tool not a goverment wiping program so anything outside that of Backup’s, Zips, FTP etc is not possible.
One area, that i would like to see within the “Configuration -> Security -> Wipe” Settings would be wipe options on specific file types and size’s within a custom box for example;
Type - Size From - Wipe Method
*PAE >5,000KB RCMP (DSX)
*PAE <500KB GUTMANN 35
*Zip ALL SIZES RANDOM
*7Z ALL SIZES US DoD 5220.22-M (E)And a normal Tick Box saying on the lines of “Wipe All Formats Same” and the Typical Drop Box.
Another feature within Shell Extensions under Extract “Extract & Wipe Archive” then under Compress “Compress & Wipe Original” it would also be good to see a new split “Wipe Options” including wipe PA History, Wipe Selected Archives “Brings up a Dialog Box and user can select multiple Archives for Wiping”
All of this is based around securing Temps, old archives, encrypted files used with PA only.
It would also be a good idea to see this particular Config Screen including passwork manager , policies and wipe methods lockable via a Password.
Obviosly, these are my idea’s some may disagree… however, i feel that this is a strong step forward for Conexware and i can see it scoring many firms tick boxes and personal users concirns about securing their personal files.
-
why would you base your security policy on size of type of archive?
Also, while functionality is there, options are explanations of those windows are not final.
-
why would you base your security policy on size of type of archive?
Also, while functionality is there, options are explanations of those windows are not final.
As always, I understand that “Beta” and “Alpha” dont represent a final product so I expect that the product isnt finished :) so no worries there fella.
With regards as to the file size, there are a few reasons;
1. Some Users would Encrypt with a specifc file and as such would want a higher level of security of that than others.
2. Wiping can take significant resources & time to finalize depending on the size having the ability to scale those options can aid… “You could even add a time of wipe ie when screensaver turns on”
3. Also reference size, some users would encrypt highly confidential files in splits in order to make it harder to find and compile as such the file sizes are smaller so again having a setting for *PAE to wipe on files always less than 2megs on Maximum Gutman.
When i worked for “Urenco” i worked in a small project team to write with a firm a security application to “secure” files some of those settings i mentioned were key aspects raised by end users dealing with specific secure files extracted from systems. Certain files of their sizes were destroyed with the highest form were others although larger in size but less confidential were wiped with a ramdom wipe “still secure” but not as timely.
These afterall are suggestions.
It would also be advised to have a Log just like you have backup log. this log writes a confirmation of wipe per file. something some firms request to validate secure wiping of confidential data. it also aids to confirming there were no interuptions.
-
Here is 12.5 Pre-Beta release:
http://www.powerarchiver.com/test/alpha120/powarc125003.exeit has it now properly named… you have 3 options:
1, 3, 7 passes, all based on DoD 5220.22-M.Obviously if you use 7 passes, it will overwrite those files 7 times, which means it will be slower than normal file delete.
-
Here is 12.5 Pre-Beta release:
http://www.powerarchiver.com/test/alpha120/powarc125003.exeit has it now properly named… you have 3 options:
1, 3, 7 passes, all based on DoD 5220.22-M.Obviously if you use 7 passes, it will overwrite those files 7 times, which means it will be slower than normal file delete.
Top Notch Boss! I shall count this as a Birthday present from ConeXware lol. I look forward to this being expanded on further as time goes on. and as always, happy to aid in testing, suggestions etc
-
anything other than this, write up new thread… for instance, separate wipe tool for deleting files securely? Wishlist forums :-)