-
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.
-
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. -
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.
PowerArchiver 2010 and Windows 7
-
Well, the changelog says full Windows 7 support.
I’ve installed Win 7 x64 build 7057 yesterday. This came at PA installation. I’ve used the default installer settings.
-
and? I would guess it is temporary bug with temporary version of Win7.
It works fine with 7000 and 7022, you should report it to Microsoft if you can so they fix it, but I am assuming it is bug affecting many different programs.
Just like when your Notepad opens when desktop starts in 7057 :-).
-
I do hope it is just a temporary bug. When PA 2010 Beta 2 wouldn’t install on 7057 I figured no biggie I’d just drop back to beta 1.
It refused to install as well so I fell back to PA 2009. However, it wouldn’t install, either. Guess I’ll have to wait till the next Windows 7 build to (hopefully) get my PA functionality back.
-
I do hope it is just a temporary bug. When PA 2010 Beta 2 wouldn’t install on 7057 I figured no biggie I’d just drop back to beta 1.
It refused to install as well so I fell back to PA 2009. However, it wouldn’t install, either. Guess I’ll have to wait till the next Windows 7 build to (hopefully) get my PA functionality back.
we run PA 2010 on Win7 7000, 7022, 704x and 7057… all work fine.
What exactly happens? Generally speaking, there are so such bugs in Win7 that would make this happen. It is probaly Windows Installer acting up but you need to send us more info.
-
are you getting the same message as above or? I though original post was just Win7 thinking something went wrong with installation and trying to be helpfup, as that file is actually not crucial to installation.
-
After setting additional install options and my chosen install directory I’m directed to click the Install button to begin installation.
It is once I do this I get a dialog box titled “Installer information” which reads:
Error reading from file
C:\Users<username>\AppData\Local\Temp\7zSD52D.tmp\setup.msi. Verify the file exists and that you can access it.Of course the temp directory is always different, but every time I make the attempt with the different installers setup.msi is always present and seems accessible.</username>
-
seems as if Windows Installer is borked… do you have PA 2009 or PA 2010 listed when you go to Programs? If so, maybe you need to use Windows Installer Cleaner utility to clean Windows Installer if you do have PA 2009/2010 listed there.
-
No, I haven’t had PA installed on Windows 7 Build 7057 at all. Neither PA 2009 or PA 2010 get far enough to install.
I’ll try to dig up this cleaner and run it anyway just to be safe.
-
when you run setup, and go to the temp folder, all the files are properly there? what happens if you copy them to another folder and run them manually from there?
-
When I navigate to that directory there are three files:
setup.exe
setup.ini
setup.msiCopying those files to a different directory and running the setup.exe results in the same order of events above except that the error message dialog states:
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package.The error code is 2203.
Running setup.msi instead gives me the same error code 2203 message.
-
Gawd, I fixed it! Seems user SYSTEM didn’t have full control access to the temp directory.
Sorry for the wild goose chase. How it “lost” its privileges is beyond me, though.
Thanks for all the help, SPWolf!
-
:-)
i was just reading what the error means and was about to post to check that :P.
thanks, np.
-
Consider this one fixed…although after it did install I did get the dialog above that the OP posted, but I run into quite a few programs that do that upon installation.
I’m so glad I don’t have to go without PA. I rely on it so much to be able to open everything I don’t know how I’d get along without it.
-
yeah, dialogue above is basically just due to win7 build and should be fixed by them, it is just an glitch that doesnt affect anything…
by the time Win7 is released, PA is actually going to be tested by Win7 Q&A team against final build to make sure all of their issues are fixed.