Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    • PA 21.00.18 testing via context menu causes extraction of files

      D

      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.

      Tech Support
    • Start PowerArchiver 2023 Starter when my computer starts

      Brian Gregory

      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.

      Tech Support
    • Testing .pa archives

      PA_Fan

      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 errors

      Is 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.

      Tech Support
    • PA 21.00.18 Action / Test behaves oddly for me on .PA files

      Brian Gregory

      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.

      Tech Support
    • Small UI / Theme bug in 2023

      Z

      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 :)

      Tech Support
    • PowerArchiver and PACL for macOS

      spwolf

      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

      Tech Support
    • Functions in Windows 11 context menu no longer work after last Windows Update

      T

      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.

      Tech Support

    PowerArchiver 2016 not registered anymore after updated to v16.00.56 RC3

    Tech Support
    4
    10
    4793
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      robert2098 last edited by

      I’ve already sent a support request but as I got no response yet I will post it here.

      I was using PowerArchiver Toolbox 2016 (probably v16.00.46 RC2) until it updated itself this weekend. When I started PA again it showed me the “trial expired” screen. So I tried to register it again with the key I retrieved about a month ago when PowerArchiver updated itself from 2015 to the 2016 version. After PowerArchiver restarted I still got the “trial expired” screen. Thus the Toolbox registration key that worked for 2016 RC1 does not work for RC3.

      Thus I logged in the “Order Recovery” website to request a new key. A few seconds later I got the new key but the new key does also not register PowerArchiver Toolbox (still giving the trial expired screen). I requested a new key again, but still no luck.

      Now two days later I requested again a new key, but also this key does not work.

      So I uninstalled PA 2016 v16.00.56 RC3 and reinstalled v16.00.43. After installing the older version opens already registered with the Toolbox key.
      So it seems somewhere between v16.00.43 and v16.00.56 something changed that makes existing Toolbox 2016 keys not work anymore.

      Robert

      1 Reply Last reply Reply Quote 0
      • R
        robert2098 last edited by

        OK, I downloaded several older versions to determine in what version the registration problem starts. It turns out that v16.0.0.50 is the last version where my Toolbox key works. After installing v16.0.0.51 I get the “trial expired” dialog.
        Hope this helps in tracking down the problem.

        Robert

        1 Reply Last reply Reply Quote 0
        • M
          Mili conexware last edited by

          Hi Robert,

          Was this ticket #44151?
          We replied to it yesterday, if that was it.

          Thanks for the details. Can you send the complete registration email to the reply of that ticket? You can copy the complete 2016 registration email and paste it in your reply there.
          We will take a look at it immediately.

          thanks again!

          R 1 Reply Last reply Reply Quote 0
          • R
            robert2098 @Mili last edited by

            @Mili:

            Hi Robert,

            Was this ticket #44151?
            We replied to it yesterday, if that was it.

            Thanks for the details. Can you send the complete registration email to the reply of that ticket? You can copy the complete 2016 registration email and paste it in your reply there.
            We will take a look at it immediately.

            thanks again!

            Hi Mili,

            I don’t know what ticket number it was. I didn’t receive an e-mail confirmation with a ticket number or any reply (it is not in the spambox). Seems I’ve mistyped my e-mail address in the support form. Sorry.

            I’ve sent the mail with the non working Toolbox 2016 registration code in a new support request.

            Thanks and regards,

            Robert

            1 Reply Last reply Reply Quote 0
            • M
              Mili conexware last edited by

              got it! thanks very much for sending it again

              looking into it now

              1 Reply Last reply Reply Quote 0
              • M
                Mili conexware last edited by

                Hi Robert,

                I’ve just sent another email with a question that will help us, we’re in the middle of investigating and figuring out the issue and your assistance would help.

                Many thanks again!

                R 1 Reply Last reply Reply Quote 0
                • spwolf
                  spwolf conexware last edited by

                  @robert2098:

                  I’ve already sent a support request but as I got no response yet I will post it here.

                  I was using PowerArchiver Toolbox 2016 (probably v16.00.46 RC2) until it updated itself this weekend. When I started PA again it showed me the “trial expired” screen. So I tried to register it again with the key I retrieved about a month ago when PowerArchiver updated itself from 2015 to the 2016 version. After PowerArchiver restarted I still got the “trial expired” screen. Thus the Toolbox registration key that worked for 2016 RC1 does not work for RC3.

                  Thus I logged in the “Order Recovery” website to request a new key. A few seconds later I got the new key but the new key does also not register PowerArchiver Toolbox (still giving the trial expired screen). I requested a new key again, but still no luck.

                  Now two days later I requested again a new key, but also this key does not work.

                  So I uninstalled PA 2016 v16.00.56 RC3 and reinstalled v16.00.43. After installing the older version opens already registered with the Toolbox key.
                  So it seems somewhere between v16.00.43 and v16.00.56 something changed that makes existing Toolbox 2016 keys not work anymore.

                  Robert

                  thanks for the report. It seems to have something to do with PowerArchiver version you are getting free upgrade from. I have created reproducible ticket in our system and we will figure out until next release. This is only for people who had purchased PA 2011 Toolbox English with BD.

                  In the meantime, we will add PA 2016 Tbx with 12 months of select to your account so you can continue using latest PA 2016.

                  thank you!

                  1 Reply Last reply Reply Quote 0
                  • R
                    robert2098 @Mili last edited by

                    @Mili:

                    Hi Robert,

                    I’ve just sent another email with a question that will help us, we’re in the middle of investigating and figuring out the issue and your assistance would help.

                    Strangely I didn’t get your e-mail with your question while I double checked if the e-mail address I entered in the support form was correct. Anyway, I got the e-mail with a new registration key that works. Thank you very much.

                    The non-working key was indeed from an update from PowerArchiver Toolbox with BitDefender.

                    Many thanks to both of you!

                    Robert

                    B 1 Reply Last reply Reply Quote 0
                    • B
                      bws110011 @robert2098 last edited by

                      I had the same issue with an automatic update going from 16.00.46 to 16.00.56. I found the old installation file and reverted to .46. It was still registered with no action on my part. I sent an email to support with more details, but if you need information from another ‘bad’ system I can supply it if needed.

                      (Question: Does the registration code change each time you request it? I had looked up the email from December with the registration code and tried that, then requested it again to confirm that I had it correct and it provided a different code.)

                      spwolf 1 Reply Last reply Reply Quote 0
                      • spwolf
                        spwolf conexware @bws110011 last edited by

                        @bws110011:

                        I had the same issue with an automatic update going from 16.00.46 to 16.00.56. I found the old installation file and reverted to .46. It was still registered with no action on my part. I sent an email to support with more details, but if you need information from another ‘bad’ system I can supply it if needed.

                        (Question: Does the registration code change each time you request it? I had looked up the email from December with the registration code and tried that, then requested it again to confirm that I had it correct and it provided a different code.)

                        Hello,

                        this has been solved update few days later, here is the latest release:
                        http://dl.powerarchiver.com/2016/powarc160060.exe

                        Yes, the code changes each time due to encryption used. Thanks!

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post