-
-
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
Corrupt backup archive. If VirtualStore\Program Files folder is selected.
-
Corrupt backup archive. If VirtualStore\Program Files folder is selected.
Ran my normal backup script which backed up and tested fine.
Ran it again and there was a long delay before things seemed to happen. Tested the archive and it was corrupt (first time ever that has happened to me). Lots of CRC Errors.Been testing things and I noticed that if I select Overwrite previous file (I don’t usually select that) Then I can run the backup time after time and no error. But If I deselect Overwrite option, then it’s back to the errors again.
I only have 1 other older script that I could test and it is only 1 folder with a couple of sub-folders and not very large, no error on that one.
So I made a new backup of a couple of folders, ran it, tested it. Ran it again and tested it and it was fine. Another new backup a couple of folders now with the addition of a few files. ran it and tested it. Ran it again and tested it all was fine.
Thought that maybe it was just a problem with an old script, so just made a new backup same files and folders as my old one.
Ran it, tested it all fine. Ran it and tested again. Corrupt archive once again.
Started to remove files and folders 1 by 1 and ran and tested after each was removed. Same results. It was only after I removed a folder from C:\Users\Username\AppData\Local\VirtualStore\Program Files that I could keep running the backup without errors.
Edited my old script and removed that folder from it and it works time and again.
I think I have found a bug.
Edit: Scratch all that I have obviously spent too long on trying solve this and boobed. When I removed the folder from C:\Users\Username\AppData\Local\VirtualStore\Program Files from my backup I must have checked the Overwrite previous file again.
Coming back to it now and trying again even with the VirtualStore\Program Files folder removed I am getting a corrupted archive.
I am wondering now if it is a size of archive problem.
That will have to wait until tomorrow before I can start testing that.Sorry for the misleading info.
-
ok so it can not read the backup archive, can you open it manually after sucessful cration>
anything specific? encryption? settings? etc?
(if overwrite works, without overwrite it tries to update backup archive)
-
size?
-
ok so it can not read the backup archive, can you open it manually after sucessful cration>
The one thing I forgot to try.
No problem after successful creation but If I try to open it after running it again I get Error: the Password is incorrect.anything specific? encryption? settings? etc?
Nothing special, fairly standard and I have used it a long time with no trouble.
Overwrite Previous File - No
Add Time Stamp - Yes
-D-M-Y
Use as suffixFormat: ZIP
Method: Deflate
Compression: Maximum
Backup Type NormalEncrypt with password - yes
Encryption method AES 256-bitI turned off encryption to see if that would make a difference.
It still asked for a password and was still full of errors.
I also tried Method: Optimized and Backup Type: UltraSize ?
Total 2,170 files, 113 dirs, 178,531 kB [125,811kB]
I created a new backup, adding 1 folder at a time between tests.
Results of this:
Total 38 files, 5 dirs, 32,501 kB [31,328kB] still working
Total 60 files, 6 dirs, 33,575 kB [32,018 kB] still working
Total 67 files, 8 dirs, 36,258 kB [34,618 kB] still working
Total 80 files, 9 dirs, 84,157 kB [76,157 kB] still working
Total 105 files, 13 dirs, 86,631 kB [76,734 kB] still workingNot a great number of files or directories and still working as you can see, so I stopped and created another new backup. This time selecting different folders with more in them.
Results of this one:
Total 58 files, 20 dirs, 1,731 kB [1,209 kB] still working.
Total 86 files, 22 dirs, 31,980 kB [30,415 kB] Fails with errors.Not as many files as the first one but more directories. Failed after the second folder was added.
Another new backup, 1 folder this time but a lot of files as you can see.
Total 1,062 files, 27 dirs, 52,998 kB [28,771kB] Fails with errors.Luxor
-
was the new try with encryption or without?
or do you think it is due to number of folders you added to the list? what if you add one folder with many subfolders?
or it might be due to name of certain folder?
-
was the new try with encryption or without?
With encryption.
or do you think it is due to number of folders you added to the list? what if you add one folder with many subfolders?
I was beginning to think that way Spywolf, but as you can see from the results above there was one with 105 files & 13 dirs that worked. One with 86 files & 22 dirs that failed. The last one 1062 files & 27 dirs that failed. So fairly mixed with differing results.
or it might be due to name of certain folder?
I really don’t know to be honest.
-
please check with official beta 1, and let us know if this has been fixed… thank you!
-
thanks for checking it out luxur when you have time, would love to get this for beta 2 at least….
-
Sorry for delay spywolf.
Still getting the same errors unfortunately.
-
you need to delete old file and try without encryption again.
it asks you for password becase it is updating old file, which was encrypted.
so you need to try updating non-encrypted backup…?
thanks!
-
New backup same folder structure as original.
Settings
Overwrite Previous File - No
Add Time Stamp - Yes
-D-M-Y
Use as suffixFormat: ZIP
Method: Deflate
Compression: Maximum
Backup Type NormalEncrypt with password - No
Ran backup. Extracted Ok.
Deleted what I had just extracted and ran the backup again.
Tried to extract but no luck, see screen shots 1,2,3,4,5 and 6
1 Almost the width of my screen. Clicked Yes
2 Too large for my screen. Clicked Yes
3 Too large for screen. Clicked Yes
4 Asks for password. Typed in password of usual backup.Message: Error the password is incorrect. as in screen shot 5.
Tried the password another few times, same message.
Hit Cancel then tried my usual password in the box once again, this time it extracted.
Screen shot 6 shows the folder contents after extraction.
Off now to bang my head against a wall.
-
luxor, do not bang your hand off the wall please… me and mili take a hit for you here :-).
can you create completly new backup and try it out? same result?
-
Ok, same folder structure slightly different result.
This time when attempting to extract I got the steps in screen shot 1 then as in screen shots 4,5 & 6.
No screen shot 2 or 3 this time.
Did another new backup.
This time only backed up My Documents folder.Size: 1,343 files, 105 dirs, 189,362kb [130,726 kb]
Backed up and extracted fine, ran again, extracted fine and again and again.
Note that there are no folders included from C:\Users\Username\AppData included in this back up. In all the failed ones there has been.
Luxor
-
ok, so maybe some specific filenames are casuing this issue… any particular appdata folders?
-
i think i found it, updating of zip files does not work via shell in certain conditions… reported it, should be fixed soon!
-
These are the main folders Spywolf
C:\Users\Username\AppData\Roaming\PocoMail
C:\Users\Username\AppData\Roaming\MailWasherPro
C:\Users\Username\AppData\Roaming\Opera\Opera\profile
C:\Users\Username\AppData\Roaming\FreeCommander
C:\Users\Username\AppData\Local\VirtualStore\Program Files\KeePass\(I’m not putting these spaces in the file names by the way, just when I pasted them in here that is occuring).
Of course most of folders these have many sub-folders.
-
i think i found it, updating of zip files does not work via shell in certain conditions… reported it, should be fixed soon!
Excellent, knew you would get there in the end. :p
-
send us an email via support form and i will send you an link to test version, if you have time…
thanks
-
Have done spywolf. No link yet though.
<drums fingers=“” impatiently=“”>;)Edit: And 2 minutes later I’m sent the link.</drums>
-
Well pretty much the same results with this test version.
Created a new backup:
SettingsOverwrite Previous File - No
Add Time Stamp - Yes
-D-M-Y
Use as suffixFormat: ZIP
Method: Deflate
Compression: Maximum
Backup Type NormalEncrypt with password - No
Ran, extracted. Ran again tried to extract. this time it took me straight to this screen asking for my password.
You can see in the screen shot just below where it says “Current File” that it is going to be full of errors anyway as it’s all strange symbols.Entered a password any way.
Message: Error the password is incorrect.
Hit cancel, used my normal password again and it extracted but result just like screen shot 6 in the previous post.Made another new backup this time encrypted with a password. Same result.
Even though I had set a password I still got the Message: Error the password is incorrect.
Hit cancel, retried password and it extracted to the same corrupt files.Luxor.
-
mili sent you b1 by mistake, thats not new version :-)
-
LOL that explains that then.
-
sorry, we are working on fixing last of the bugs first…
-
Please try this interim version:
http://www.powerarchiver.com/test/alpha115/powarc1150b1new.exeit should solve those issues, several bugs were fixed, we still have to test few things with it…
thanks
-
Problem sorted with this build spywolf.
Working fine with backups created with and without password. :) -
there will be more updates for that version during the day…
-
Please check your issue with latest 11.50.30 release:
http://dl.powerarchiver.com/2010/powarc1150b1.exeand let us know if this works better now.
thanks!
-
and let us know if this works better now.
Looks to me to be the same than it was in build 11.50.27.
Should I be noticing any difference in 11.50.30 ?Luxor
-
Looks to me to be the same than it was in build 11.50.27.
Should I be noticing any difference in 11.50.30 ?Luxor
if everything works fine, then cool :-)