-
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. -
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).
-
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.
-
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.
-
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
Issue with virtual drive
-
I’m running the PA 2012 beta with the virtual drive.
I can mount and access the ISO files without issue, but there is an issue when I go to unmount or remove the virtual drive.The initial attempt says everything succeeded, but then I get a message from Windows that it was unable to remove the device and the drive remains mounted.
Running Windows 7 SP1 x64.
-
Bookwyrm,
Thank you, for your post.
Can you verify that you have downloaded Beta 2 (12.00.18)
I can clarify that this is a known issue the alpha team and developers have been discusing.
You should be able to Unmount the drive by right clicking on PAStarter and Selecting “Unmount & Remove Device…”
Try and ensure the “My Computer” Window is closed to ensure this unmounts the device.
It seems that when the user is in “My Computer” it goes through the process of unmounting but something is locking PoweArchiver’s Driver from doing it. But when the user removes the drive using other dismount options in PA’s program it works.
My view on this is the 1st port of call for a user would be to right click on a device and dismount it. Although, there are other ways this shouldnt mean we should give up and find a fix. :)
-
I’m running the PA 2012 beta with the virtual drive.
I can mount and access the ISO files without issue, but there is an issue when I go to unmount or remove the virtual drive.The initial attempt says everything succeeded, but then I get a message from Windows that it was unable to remove the device and the drive remains mounted.
Running Windows 7 SP1 x64.
did you by any chance download and install beta 1 first?
-
I have always occasionally had this problem too with successive versions of PA. But if I did, I just went to the “Safely Remove Hardware” icon in the system try, clicked on the VD I wanted to remove, and that solved the problem. Always seemed, at most, like a minor glitch, one with an easy workaround. Besides, I assumed (perhaps wrongly) that it was just something else going on somewhere in my system.
-
I have always occasionally had this problem too with successive versions of PA. But if I did, I just went to the “Safely Remove Hardware” icon in the system try, clicked on the VD I wanted to remove, and that solved the problem. Always seemed, at most, like a minor glitch, one with an easy workaround. Besides, I assumed (perhaps wrongly) that it was just something else going on somewhere in my system.
there was an bug in b1 that made it impossible to unmount VD, it was fixed in b2 however it involves that user uninstalls the driver and reboots before installing new one. Which is why i asked if he used b1.
-
there was an bug in b1 that made it impossible to unmount VD, it was fixed in b2 however it involves that user uninstalls the driver and reboots before installing new one. Which is why i asked if he used b1.
I did indeed use B1 and upgrade to B2. I’ll do the uninstall of the virtual drive and reboot/reinstall and see what I get.
-
Unfortunately the uninstall/reboot/reinstall did not seem to resolve the issue. :(
-
Unfortunately the uninstall/reboot/reinstall did not seem to resolve the issue. :(
did you uninstall PowerArchiver Startport drivers, reboot and then downloaded and installed latest drivers? It has to work :-)
-
did you uninstall PowerArchiver Startport drivers, reboot and then downloaded and installed latest drivers? It has to work :-)
I did the uninstall via Programs & Features control panel and rebooted.
The install of the latest drivers, I just opened PowerArchiver and selected Virtual Drive and let it install them. According to PatchBeam the virtual drive is version 1.05.02
-
but you uninstalled the drivers right? Since uninstalling PA wont do anything.
Patchbeam just shows virtual drive version, not actual driver version.
-
but you uninstalled the drivers right? Since uninstalling PA wont do anything.
Patchbeam just shows virtual drive version, not actual driver version.
The app I uninstalled via Control Panel was “StarPort Drivers for PowerArchiver Virtual Drive Emulator”, I assume that’s the right one?
The controller I see in Device Manager is ‘StarPort Storage Controller (Lite)’. The drive is StarPortLite.sys with version 3.5 Build 20080111
-
that should work… how are you unmounting? Did you try via shell or any other way?
-
that should work… how are you unmounting? Did you try via shell or any other way?
I did the unmount via the PowerArchiver gui; selected the Virtual Drive from the ribbon and selected unmount.
Is there a different way to try?
-
lets try this,
Uninstall Starport drivers
reboot computer
download and install this driver;
http://dl.patchbeam.com/conexware/pavdint2012/files/pastarport15002int.exe -
why I can not install any games with PA 2012 Toolbox?Is there any solution for this?
-
Vinko,
What sorts of issues are you having which make it seems like there is something wrong with PA VD?
Personally, I’ve installed some programs/games using PowerArchiver’s VD and it worked fine. Of course, that does not mean it has to work fine for you.Please let us know some details and we’ll do our best to help.
-
I want to install the game. I choose .iso image, right click, mount VD and then wait VD and nothing happens….
-
Vinko,
Please try the following;
Open PowerArchiver
Go to the Burner menu
Click on the Virtual Drive button
You should be asked whether to install drivers, click Yes.
Once they are installed, go back to the same Virtual Drive button and click it, you should get PA 2012 VD working then and the right click option should also work as well.Let me know if that worked.
Thanks
-
no luck …. now I have a computer crashes every time when PA VD wants to install software…
how sorry I am that I bought a license for PA 2012 Toolbox -
I also tried with daemon tools and Alcohol 120% and even with these softwares I could not install the game and office… what could be the cause of my problem?
-
Are you running PA with administrator privileges? If not, the installation may not work.
Or perhaps you are not running the setup on your VD with administrator privileges.
Since this is not a problem I have ever heard mention, I am betting that it is a problem with a setting like those mentioned above, or some other clash on your system.
-
Hi Vinko,
Were you able to install the VD drivers properly?
If not, here is the direct link to them;
http://dl.patchbeam.com/conexware/pavdint2012/files/pastarport15003int.exeIf you have, then what errors are you getting when trying to use the VD.
Also, please do try running PA as admin as noted by Socrates and see if that helps.
-
re-install Windows 7 was the only solution …. PA 2012 Toolbox is now working very well…
-
Glad it was fixed. But what a time-consuming solution. Sorry.
-
Glad it works Vinko!!
-
I’d be lost without my virtual drive…:)
-
who knows, probably some driver messed up all the virtual drives as you tried them all…. I will be closing this thread so if something else comes up, open new one… thanks.
