-
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.
SOLVED FIPS
-
activating FIPS by following the requester of the latest version .39 caused me a lot of trouble, because the culprit was not obvious
an extensions for ms visual studio was not prepared for FIPS and refused compiling and building
implications
blogs.msdn.microsoft -
Should work better now in version .41, please let us know and thanks for the report
https://powerarchiver.cachefly.net/2019/powarc190041.exe -
activating FIPS by following the requester of the latest version .39 caused me a lot of trouble, because the culprit was not obvious
an extensions for ms visual studio was not prepared for FIPS and refused compiling and building
implications
blogs.msdn.microsoftFIPS is meant to be activated only by users who have legal requirement to use FIPS, it is not recommended for anyone else.
What can we do to improve this process? -
currently the decision to use FIPS is very prominent at every start of the program until you say yes, it should be reduced to a check mark in settings
-
-
there is a setting in the Configuration menu that allows you set FIPS to ON, that turns on FIPS in PowerArchiver. The following confirmation dialog is confirms the enabling of FIPS in the Windows settings.
In my test, it appeared once, after clicking Yes, it did not appear anymore.
Is it continuously appearing for you?
Let us know, we’ll give it a thorough check.Thanks!
-
there is a setting in the Configuration menu that allows you set FIPS to ON, that turns on FIPS in PowerArchiver. The following confirmation dialog is confirms the enabling of FIPS in the Windows settings.
In my test, it appeared once, after clicking Yes, it did not appear anymore.
Is it continuously appearing for you?
Let us know, we’ll give it a thorough check.Thanks!
it should never appear unless someone changed fips setting to ON… by default that should never appear, so we have to make sure it doesnt appear by default.
It is possible that someone left FIPS setting on in previous version of PA though.
-
there is a setting in the Configuration menu that allows you set FIPS to ON, that turns on FIPS in PowerArchiver. The following confirmation dialog is confirms the enabling of FIPS in the Windows settings.
In my test, it appeared once, after clicking Yes, it did not appear anymore.
Is it continuously appearing for you?
Let us know, we’ll give it a thorough check.Thanks!
it should never appear unless someone changed fips setting to ON… by default that should never appear, so we have to make sure it doesnt appear by default.
It is possible that someone left FIPS setting on in previous version of PA though.
checked, with the default setting on, no confirmation dialog appears. When changed to On, the confirmation dialog appeared once.
Will wait on @qrti 's details and settings to test the same and make sure it works as intended. -
I never touched a FIPS setting, I even don’t know where to find it, the requester popped up at every start of version .39 until I said yes, after that PA started without the requester
-
Thanks for the information @qrti
Could you please go to the Options tab and click the Set Defaults button.
That will set PowerArchiver to the default settings, does it occur then, after the default settings have been set?Thanks for your help!
-
- 2019 .39 was not installed anymore
- so I uninstalled the current 2018 version
- and did a fresh installation of 2019 .39 version
- no FIPS requester
maybe the FIPS message was a settings conflict with the previous .33 version, I did an update from .33 to .39 and no fresh installation at that time
-
I’m running 19.00.39, which was updated a couple of days ago, and since when I get the “Enable FIPS” popup. It’s impossible to turn it off in the AI setting screen, so I followed the recommendation to reset to Defaults which seems to fix it i.e. the popup doesn’t appear.
As far as I can judge, I have no need at all for FIPS to be enabled on this machine, and there seem to be a number of recommendations against enabling it on Windows.
I have my PA set up in a particular way (incorporating some of the points/features that were problematic in the test phase), and I’d hate to have to keep resetting it from defaults to my preferences.
Out of interest, I’d like to know this. I reset to defaults, then rejig my configuration to suit me, and then save the settings as the reg. entry. Would importing these settings always get me back to my configuration but minus FIPS and associated popup?
-
I’m running 19.00.39, which was updated a couple of days ago, and since when I get the “Enable FIPS” popup. It’s impossible to turn it off in the AI setting screen, so I followed the recommendation to reset to Defaults which seems to fix it i.e. the popup doesn’t appear.
As far as I can judge, I have no need at all for FIPS to be enabled on this machine, and there seem to be a number of recommendations against enabling it on Windows.
I have my PA set up in a particular way (incorporating some of the points/features that were problematic in the test phase), and I’d hate to have to keep resetting it from defaults to my preferences.
Out of interest, I’d like to know this. I reset to defaults, then rejig my configuration to suit me, and then save the settings as the reg. entry. Would importing these settings always get me back to my configuration but minus FIPS and associated popup?
How do you mean it is impossible to turn it off? There is an Off setting there.
And yes, saving your HKCU settings and restoring them will always bring your full settings.
From next release, we will show warning only when in Enforced mode for FIPS.
-
Should work better now in version .41, please let us know and thanks for the report
https://powerarchiver.cachefly.net/2019/powarc190041.exe