Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    • 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
    • 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

    Extraction problem

    Tech Support
    6
    13
    4089
    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.
    • S
      Socrates Banned last edited by

      I am going to have to offer this post. However, I cannot send more information or do further testing right now. Sorry.

      I know this will not make you happy. For that reason, I almost didn’t offer the post at all. Yet on the off chance this might help some other user . . .

      I went back to 2010. I will try 2011 again after the full release is out and has gone through a couple of updates, perhaps late spring.

      Here’s why. Using 2011, even for the past week, has gotten my home and work computers out of sync – and I just discovered it. It will take some effort to determine exactly what files were not updated.

      I move files back and forth from home to work via archives, built by PBScripts.

      I just discovered early this morning that 2011 was not extracting all the files as it should. But there was no error message warning me of the problem. It just didn’t extract them. So I was not keeping the files in sync as I want.

      I know it wasn’t extracting pst files. I am fairly sure it wasn’t extracting at least some other files as well. But I am not certain.

      Once I uninstalled and reinstalled 2010, everything was fine. All the files extracted as exactly as they should.

      The plausible inference, is that 2011 has a glitch, or else that there is some obscure setting.

      BTW, I did have UAC elevation checked (I believe it is checked by default).

      Again, I just cannot do more right now other than offer this report.

      If this is more hassle to you than it is worth, let me know and, in the same circumstances, I will keep silent.

      My hope was that some other user might be able to see the problem as well, and help you find a solution.

      1 Reply Last reply Reply Quote 0
      • moles42
        moles42 Alpha Testers last edited by

        can’t say I’ve encountered anything of this nature since installing it buddy…done quite a bit of compressing and extracting but from what I can see all is working fine on that level of testing…if I do have a similar issue I will post back here.

        Windows 10 Pro x64
        Intel Core 2 Duo E6850 @ 3.00GHz
        4.00GB Dual-Channel DDR2 @ 399MHz
        NVIDIA GeForce GT 730

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

          I do remember experiencing transfer issues with PA 2011 during Alpha testing. This was reported and how we had to resolve this was going through all the settings again and applying.

          Now this resolved the issue for me, but not sure if its the same for you.

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

            @Socrates:

            Here’s why. Using 2011, even for the past week, has gotten my home and work computers out of sync – and I just discovered it. It will take some effort to determine exactly what files were not updated.

            I move files back and forth from home to work via archives, built by PBScripts.

            I just discovered early this morning that 2011 was not extracting all the files as it should. But there was no error message warning me of the problem. It just didn’t extract them. So I was not keeping the files in sync as I want.

            Can you send us an example archive?

            Did you have both computers using PA2011 or?

            Actual extraction engine should be the same as in 11.71 (with some updates that shouldnt have anything to do with extraction of files).

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

              was it not compressing files properly or not extracting them? I assume you used PA 2011 backup via pbs for compressing and then PA 2011 for extracting?

              or did you use PA 2010 backup for compression and then PA 2011 for extracting?

              Also, what version of PA 2010?

              thanks a lot!

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

                @Sir:

                I do remember experiencing transfer issues with PA 2011 during Alpha testing. This was reported and how we had to resolve this was going through all the settings again and applying.

                Now this resolved the issue for me, but not sure if its the same for you.

                what you had was old PBS not working in PA 2011 Backup… what he is reporting is that not all files are being compressed/extracted as they should.

                It could be million things, hard to say right now… could be something in the zip engine (although they should be very similar), there could be that one of the pbs settings is not applied and hence files are not filtered properly… or maybe it is extraction engine? :-)

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

                  Unfortunately, without (at least) the PBS files socrates used; I don’t think there is much that can be tested/checked. The number of possible variations is daunting!

                  All we know is that the PBS files were used “to synchronise” between computers (Windows 7).

                  We can infer that the archive (unknown format) was created - maybe using some form of date/modification check, maybe not.
                  Then an extraction, again maybe checking/maybe not?
                  Unless someone else “stumbles” across the problem…

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

                    due to Luxor’s post in another thread, we found an issue with extracting selected folders and fixed what we could reproduce and what luxor could reproduce.

                    please check with 12.00.38 RC2, get it via patchbeam….

                    thanks!

                    S 1 Reply Last reply Reply Quote 0
                    • S
                      Socrates Banned @spwolf last edited by

                      I had a free half hour, so I did a test.

                      The central problem appears to be the handling of .pst files. (I think there might have been other problems too. But with the help of Luxor, you may have solved them.)

                      The problem, I now see, is not only – or even primarily – extraction, but how I use 2011 to built the archive. If my transfer archive includes my .pst file AND that PST file was open when PA copied it, then that file will not successfully extract to the other computer.

                      However, if I rebuild that archive when Outlook is closed (so VSS isn’t required), it copies . . . and extracts . . . the PST file just fine.

                      That suggests that VSS within PA does not successfully handle PST files.

                      The problem appears to be PA’s use of VSS since I have successfully copied PST files with at least two different programs using VSS.

                      That’s my best guess at the moment.

                      No time for more tests for a week or three.

                      Sorry.

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

                        to make PST work with VSS, you have to enable always use: .pst VSS option… otherwise it will not work properly.

                        Using VSS is slow, so we dont want to have (in PowerArchiver), option that will “always” use VSS because we make assumption that a lot of people will use it without need… thats why the option is there.

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

                          to know that VSS has worked, you will get UAC prompt once VSS activates, that will elevate PA to Admin so UAC can be used.

                          S 1 Reply Last reply Reply Quote 0
                          • S
                            Socrates Banned @spwolf last edited by

                            I did have that option set (always use with .PST).

                            I did not get a pop up window for UAC elevation.

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

                              just did a backup on a 64bit machine, VSS enabled, Added outlook.pst to backup tracklist while outlook is open, clicked “Do Backup”, Uac appeared and clicked YES, in a few seconds compression started and all was fine.
                              Worked the same on a 32bit machine as well.

                              Do the other programs you tried VSS with show UAC?
                              can you try another locked file to see if it works with PA?

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