Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    • 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
    • File Explorer Shell Extension crash on Junction

      W

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

      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
    • Functions in Windows 11 Context Menu don't work in some directories

      P

      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.

      Tech Support
    • Missing virtual driver in Patchbeam

      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

      Tech Support
    • 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
    • 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

    Logo is corrupt during install

    Tech Support
    3
    12
    5694
    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.
    • guido
      guido last edited by

      see image.

      Guido
      attachment_t_2204_0_logo.jpg

      Windows 11 Pro ENU x64
      Intel Core I7
      32 GB RAM

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

        depending on your settings, image might be stretched to cover complete width of the window…

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

          on what settings?

          if I look at the logo in the tips form, it looks ok?

          guido

          Windows 11 Pro ENU x64
          Intel Core I7
          32 GB RAM

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

            @guido:

            on what settings?

            if I look at the logo in the tips form, it looks ok?

            guido

            yeah but logo in tips form is not in MSI installer :-).

            1 Reply Last reply Reply Quote 0
            • guido
              guido last edited by

              in XP and vista they are corrupted. I would guess it would look good in one of the two

              Guido

              Windows 11 Pro ENU x64
              Intel Core I7
              32 GB RAM

              TBGBe 1 Reply Last reply Reply Quote 0
              • TBGBe
                TBGBe @guido last edited by

                Not sure if this is the same, but …
                The logo in the Help File (Introduction) is the same - also has that “corruption” :confused:

                1 Reply Last reply Reply Quote 0
                • guido
                  guido last edited by

                  I don’t see any corruption in the help on XP

                  Guido

                  Windows 11 Pro ENU x64
                  Intel Core I7
                  32 GB RAM

                  TBGBe 1 Reply Last reply Reply Quote 0
                  • TBGBe
                    TBGBe @guido last edited by

                    Are you not referring to the pixellation and red dot at the corner of the clamp - next to the text 2007?

                    guido 1 Reply Last reply Reply Quote 0
                    • guido
                      guido @TBGBe last edited by

                      This is how my icon looks on XP

                      Guido
                      attachment_p_10505_0_help_logo.jpg

                      Windows 11 Pro ENU x64
                      Intel Core I7
                      32 GB RAM

                      TBGBe 1 Reply Last reply Reply Quote 0
                      • TBGBe
                        TBGBe @guido last edited by

                        That’s what I thought you meant, the red dot is there :confused:

                        1 Reply Last reply Reply Quote 0
                        • guido
                          guido last edited by

                          The red dot is not the corruption. Look at the first image I attached to the post and look at the second 0 of 2007

                          Guido

                          Windows 11 Pro ENU x64
                          Intel Core I7
                          32 GB RAM

                          TBGBe 1 Reply Last reply Reply Quote 0
                          • TBGBe
                            TBGBe @guido last edited by

                            @guido:

                            The red dot is not the corruption. …

                            OK then :p

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