-
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.
-
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).
-
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. -
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 :)
This Looks Bad!
-
Is this for real?
It looks suspicious as hell……Chuck
-
what exactly is suspicous?
-
:confused:
-
Update fails to install. I’ve never had that happen before, so I thought it was a phony. :o
-
hey my update also fails, and i thougt my windows is broken :)
maybe the installer is broken.
My installation Process sais:
Aktion gestartet um 17:48:09: AI_DELETE_SHORTCUTS.
MSI (s) (F0:74) [17:48:09:937]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI4.tmp, Entrypoint: DeleteShortcuts
MSI (s) (F0:A4) [17:48:09:937]: Generating random cookie.
MSI (s) (F0:A4) [17:48:09:953]: Created Custom Action Server with PID 2012 (0x7DC).
MSI (s) (F0:D0) [17:48:10:000]: Running as a service.
MSI (s) (F0:D0) [17:48:10:000]: Hello, I’m your 32bit Impersonated custom action server.
MSI (s) (F0!28) [17:48:10:031]: PROPERTY CHANGE: Modifying AI_SHORTCUTSREG property. Its current value is ‘0|0|0|’. Its new value: ‘1|1|1|0’.
MSI (s) (F0!28) [17:48:10:031]: Note: 1: 2205 2: 3: IniFile
MSI (s) (F0!28) [17:48:10:031]: Note: 1: 2228 2: 3: IniFile 4: DELETE FROM
IniFileWHEREIniFile.Section=‘InternetShortcut’ ANDIniFile.DirProperty=‘StartupFolder’MSI (s) (F0:74) [17:48:10:031]: Leaked MSIHANDLE (4) of type 790541 for thread 808
MSI (s) (F0:74) [17:48:10:031]: Note: 1: 2769 2: AI_DELETE_SHORTCUTS 3: 1
DEBUG: Error 2769: Custom Action AI_DELETE_SHORTCUTS did not close 1 MSIHANDLEs.
Bei der Installation dieses Pakets ist ein unerwarteter Fehler aufgetreten. Es liegt eventuell ein das Paket betreffendes Problem vor. Der Fehlercode ist 2769. Argumente: AI_DELETE_SHORTCUTS, 1,
Aktion beendet um 17:48:10: AI_DELETE_SHORTCUTS. Rückgabewert 1.
MSI (s) (F0:AC) [17:48:10:046]: Doing action: RemoveExistingProducts
Aktion 17:48:10: RemoveExistingProducts. Anwendungen werden entfernt
Aktion gestartet um 17:48:10: RemoveExistingProducts.
Aktion beendet um 17:48:10: RemoveExistingProducts. Rückgabewert 1.
MSI (s) (F0:AC) [17:48:10:046]: Doing action: InstallInitialize
Aktion 17:48:10: InstallInitialize.
Aktion gestartet um 17:48:10: InstallInitialize.
after that my pc hangs and i can click around but i can’t reboot etc… because msiexec.exe hangs and cannot be terminated!
-
@Charles:
Update fails to install. I’ve never had that happen before, so I thought it was a phony. :o
what error did you get?
-
re-download the beta and try again. it is newer version although it doesnt have anything to do with this issue…
-
Worked fine this time, but why???
Before, it just kept quitting in the middle of the install (not the download)
and disappeared.:(Chuck
-
nice… strange ways of Windows Installer… :-)
-
I can replicate the error……
On the installation choices window, uncheck the box to add PA to the start menu.
When it starts to install, I get an error. If I check the box and let the installer create a start menu folder, then it installs correctly.
Am I crazy, or what?;)
Chuck
-
sweet
-
Hi,
I think my Windows was broken, I tried to install FarCry, and the setup wizzard didn’t finish, too(I think it uses InstallShield not MSI).
So there was a problem with my Installers :)I think I fixed it.
I took an Knoppix DVD and did this:mkfs.vfat -F 32 /dev/hda1
:P at the moment im reinstalling Windows. I think the fresh installation won’t have this misterious installer bug.
PS: for those how aren’t familar with linux I formated my disc :) (like format c: )
