-
when clciking on powerarchiver update from within powerarchiver we get a windows for the update but it nows sayes script errors. I think it could be due to windows update in windows 10 can you look into it. By pressing cancel it seems to be ok. It seems that the page being displayed as erros on it.
-
From within PA on the extract popup, buttons are hidden, I must resize the window to get access to the OK/Cancel buttons. Tried on the default notebook screen (Macbook M1 Max 14") as well as on my external monitor (4k).Screenshot_2022-05-12_10-02-10.jpg
-
Just uncompressed a RAR file that has a folder within, PA created the folder but the files inside are not being saved into folder because directory separator is a BACKSLASH (Windows style) instead of SLASH (macOS).Screenshot_2022-05-12_09-59-08.jpg
-
Hello,
When clicking on the main ribbon for a new version I get a script error message.
Actual version: 21.00.15 - French version
OS: W10 21H2 19044.1645Best regards
WilfridPS: Keep building such good software
-
Ho già contattato il supporto con il modulo presente qui https://www.powerarchiver.com/it/contact/ da settimane ma non ho ricevuto riscontro e ora che ho aggiornato alla versione 21.00.15 ho notato che il problema persiste.
Quando clicco PDF Encrypt & Sign nel tab Crittografia appare la schemata riportata sotto come se mancassero le funzionalità.I’ve already contacted support with the form here https://www.powerarchiver.com/it/contact/ weeks ago but I haven’t received any feedback and now that I’ve updated to version 21.00.15 I’ve noticed that the problem persists.
When I click on PDF Encrypt & Sign in the Encryption tab the schematic below appears as if the functionality is missing.de9b4a2d-07e7-4323-a5a3-1b91e73dafc0-image.png
-
I have tried to burn a DVD with PowerArchiver 2022 Final, but it didn’t work because PA didn’t found the external DVD-Burner.
I have tried several burners from Sony, LG, Dell.
I have connected the burners with several USB-Ports but unfortunately without any success.
With other burning software, e. g. Nero, all burner worked perfect on each USB-Port.
The same problem occured with PA2018 and it was solved with an update, but I don’t remember the detailed software version.
Could you check the possibility of an bug, please?
Thank you for your support in advance! -
Quando creo un archivio zip con un altro programma ad esempio Winrar se apro il file con Winrar vi sono visualizzati anche le date originali di Accesso e Creazione.
Se ottimizzo quel file zip con la funzione Ottimizza archivio di PowerArchivier (o creo un nuovo archivio) il file risultate non ha più le date originali di Accesso e Creazione.
C’è una opzione per preservare questi dati? (Non l’ho trovata nelle impostazioni del programma e ho già abilitato le opzioni “salva info complete cartella” presente in “Profili di compressione”)
/
When I create a ZIP archive with another program such as Winrar, if I open the file with Winrar, the original Access and Creation dates are also displayed.
If I optimize that zipper file with the Optimize Archive function of PowerArchivier (or create a new archive) the resulting file no longer has the original Access and Creation dates.
Is there an option to preserve this data? (I haven’t found it in the program settings and I have already enabled the “save complete folder info” options in “Compression Profiles”) -
Upgraded from 2021 to 2022. Selecting ‘backup’ no scripts are showed. Only after editing and saving an existing script (explorer) it shows up in the PA backup folder.
So is the ‘backup’ icon to open the Backup screen only for creating ‘new’ ones. This means that you have to open ALL your old pbs files and to save them again… not user friendly.
No way to improve this ? Thank you.b606f084-9d96-461e-b93b-6ba9310a0f6c-image.png
-
PowerArchiver 2022 - Final Version - 21.00.15
Download:
https://powerarchiverdl.cachefly.net/2022/powarc210015.exeInformation about PowerArchiver 2022 - 21.00.15:
https://www.powerarchiver.com/2022/04/05/welcome-to-owerarchiver-2022/Thanks everyone for your assistance!
-
Hi,
I have a 31" 4K screen with 3840x2160 pixel, which PA is able to handle - except of a scaling other than 100%.
Access violation at address 0000000..DF47A4 in module 'powerarc.exe'. Schreiben of address 0000...00330.
When changing scaling for this screen to 125%, starting PA brings the following exception:After closing this message, PA seems to work fine.
PA version 21.00.15 (03/2022) 64bit (tested with Win 10 and after upgrade Win 11)Is there any chance to avoid this access violation or this message?
Thanks and regards,
Karsten -
-
-
-
-
-
Hi,
the new Windows 11 context menu is not localized in PA 21.00.13.
While the classic context menu is localized, when it’s opened on a file on my desktop, it’s English, when it’s opened from a file on my C drive.@Mili Are there updated localization files available?
-
Hi,
I thought, I’ll give it a try and upgrade my PA 2018 Toolbox on my production machine to PA 2021 (20.10.03)
Sending registration codes in your order recovery doesn’t seem to work at the moment (I also checked my junk folder), online activation works Using registry to disable modules (for example HKLM\SOFTWARE\PowerArchiverInt\General\DisableBurning) doesn’t work as expected with modern ui. The module is visible, but I’ll get the trial nag, if I try to open it. It’s almost fine in classic and ribbon mode.7989017c-3cd2-4a99-a1f6-06ce62329dec-image.png
“DisableClouds” and “DisableExplorer” seem not to be respected at all, while the classic UI seems to respect the setting to disable any other unused module:
In settings I won’t be able to access the SmartAI settings and the settings for the internal editor if the FTP module is disabled
89843f23-ad89-45bf-92bc-406b1a11dfc9-image.pngcc40877b-d8d0-404c-b7f8-d5ae0a1ee445-image.png
-
PA Queue does not compress file optimally with same parameters if used in Queue mode.
Being able to save advanced option, and set a default profile and archive type for compression so I can save clicks.
The above two are majorly affecting my efficiency with archiving stuff with PA 20.10.03.
Can someone confirm if they are resolved with the 2022 RC1?
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.