-
PA2023 Win10, (same problem with older releases but never reported)
PA Soft is installed on partition D. (exclusive for installed progs)
Then I created on my partition G: the folders as configured in PA Settings ‘Folders’.0fcf1b09-1b91-4b74-b250-f8cf908a3348-Ashampoo_Snap_maandag 20 maart 2023_11h54m34s.png
Screenshot 2023-03-20 121152.png
The problem : Any activity on PA is saved in these folders…
PA ignores them and still use the default settings. Whats wrong ? Regards, Pirrbe -
I am still using Powerarchiver 2022 and it does not show pdf markups in the preview. Is there a setting to get version 2022 to show pdf markups in the preview? If not, does this work in version 2023?
-
The question that I have about PA archives is what happens if say ConeXware, as a company, dies in the future? What happens to any PA files that are created today? Can these files be decompressed with a copy of a PowerArchiver that can no longer phone home to the mothership thus can’t be registered or activated?
I mean, I can understand that new PA files wouldn’t be able to be created if the program isn’t registered but what about an un-registered copy because well, the question that I posed above?
It’s questions like this that make me not want to store anything really valuable in PA files out of fear that I, at some point in the future, might lose access to said data inside those files. OK, 7ZIP might not be able to compress as heavily as PA but at least it’s open source and any 7ZIP files will still be able to be read and decompressed ten, twenty, or fifty years from now.
-
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.
-
Is this a known problem? Is there a fix coming? This is a primary reason I buy PA.
I’ve tried both methods I know to extract multiple zips at the same time. 1) Multi Extract feature in the GUI. 2) In Windows File Explorer, select multiple zips, right click, use PA context menu to Extract or Extract To…
Is there a setting I missed? Or maybe it really is processing in parallel, but I can’t detect it? Nothing tells me in the Processes in Task Manager that multiple PA extracts are running. And my CPU, memory and disk resources do not look like a lot of extracts are running.
I’m using PA 2022 Standard version 21.00.18 on Windows 11 Pro version 10.0.22621 Build 22621.
-
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.
-
Is the version Preview 2023 also considered to be tested by the testteam ? In the past we got messages in the forum for testing out version x.x, to be downloaded by fastring, or I missed the one for 2023. (I discovered 2023 on the official web…)
CU, Pirrbe.
-
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 -
Hi there, been a user since 13 years now and in past whenever I had a problem or question I could email, however since 3 weeks it seems like everybody is dead?
Anyway, as kind of a last resort, I post this email a 4th time but in this forum instead now, in the hope for help:
"This is the 3rd time I am emailing you guys as I am missing a working code for the preview of Power Archiver 2023Can you please help me? I am a 13 years lasting customer of yours, and I am shocked thatr for whatever reason my support tickets are ignored now, why?
thanks in advance!
All the best!
Joerg" -
Re: Explorer.exe Crash on right click
This appears to be happening again with the Power Archiver 2022 shell extensions.
When I have Use Explorer Shell Extensions enabled in Power Archiver Configuration and right-click on c:\Users\username\Start Menu, (hidden Junction file), File Explorer crashes.
I have version 21.00.15 (03/2022) 64-bit installed in Windows 10 Version 21H2 (Build 19044.1826).
-
PA 21.00.18 running on Windows 7 64 bit.
I made a big .PA file and thought I’d check it was made correctly with Menu / Actions / Test.
Discovered:
a) PA always issues a UAC prompt to do this!
b) PA always says there are many errors in PA files. -
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.
Missing SPTD driver after PAVD install
-
I’m having an issue with SPTD option in PowerArchiver 2011. When I use the SPTD option and try to use the burner the drives are not detected even after installing PAVD. When I installed the PAVD driver from PA Burner, the StarPort Lite driver is installed but the SPTD driver failed to install. There is no sptd.sys driver in the c:\windows\system32\drivers folder. I’m running Windows 7 64-bit edition. When I try to run sptd.exe in the PowerArchiver folder it says not a valid Win32 application.
-
I have no trouble getting the VDs to load with the latest version (.59).
But I did have the following odd behavior.
If I unmount it from the shell, I get a message near the system tray saying that the VD was successfully uninstalled.
However, it still showed in my list of drives in Windows Explorer – even after a reboot.
If I open Burner and then tell it to uninstall the VD, all is fine.
-
with what version?
-
@Keith:
I’m having an issue with SPTD option in PowerArchiver 2011. When I use the SPTD option and try to use the burner the drives are not detected even after installing PAVD. When I installed the PAVD driver from PA Burner, the StarPort Lite driver is installed but the SPTD driver failed to install. There is no sptd.sys driver in the c:\windows\system32\drivers folder. I’m running Windows 7 64-bit edition. When I try to run sptd.exe in the PowerArchiver folder it says not a valid Win32 application.
do you get some message during installation? only with final? we didnt change that part of PA in a long time, there should be nothing new happening with SPTD drivers.
-
I haven’t used PAVD for a long time, I waited until after final came out and then when I installed PAVD there was a warning message from Duplex Secure asking to install the driver and even when I click the Install button, the sptd.sys driver is still not installed to the c:\windows\system32\drivers folder and the SPTD option in the configuration causes the burner to not detect any drives. PAVD is a separate download from the main PA and is installed via PatchBeam when using Virtual Drive for the first time. The only workaround for this issue is to download the SPTD v1.78 driver from http://www.duplexsecure.com/en/downloads and install it manually. Can you bundle the PAVD driver with SPTD v1.78 in the next PAVD update on PatchBeam? SPTD v1.78 fixes BSODs during file copy on some systems.
-
I tried PAVD on 32-bit and it automatically installs SPTD 1.62 when I install PAVD but on 64-bit it fails to install SPTD and there is no installing SPTD 1.62 message on the screen during installation of PAVD as it does on 32-bit and thus the SPTD driver is missing on 64-bit. This is a 64-bit specific issue.
-
@Keith:
I tried PAVD on 32-bit and it automatically installs SPTD 1.62 when I install PAVD but on 64-bit it fails to install SPTD and there is no installing SPTD 1.62 message on the screen during installation of PAVD as it does on 32-bit and thus the SPTD driver is not missing on 64-bit. This is a 64-bit specific issue.
did you use sptd from their own site, and that works?
-
I didn’t use SPTD from their own site during this test for this issue on 64-bit. Can you reproduce the issue on the 64-bit issue. Uninstall PAVD if already installed, then uninstall SPTD with the standalone SPTD installer from its own website and reboot and then reinstall PAVD from the Virtual Drive link in PA Burner. When I install PAVD from the Virtual Drive link on 32-bit it automatically displays SPTD v1.62 setup and installs the SPTD driver just before the StarPort driver installation. The 64-bit OS is my main OS and the 32-bit OS is a guest OS on VirtualBox. I was testing 32-bit temporarily to see if the issue only occurs on 64-bit. I later installed SPTD v1.79 from its own site after this testing on 64-bit and it works. The sptd.exe file in the PowerArchiver folder in 32-bit OS is 860KB and has a DuplexSecure icon and then when I double-click it it shows the SPTD v1.62 setup screen with a button to install/update, uninstall, or cancel and the one in 64-bit OS is 512KB and only has plain Windows icon and when I double-click it it says invalid Win32 application. I then removed the 32-bit guest when this testing is completed.
