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
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.
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.
PowerArchiver 2022 - Final Version - 21.00.15
Information about PowerArchiver 2022 - 21.00.15:
Thanks everyone for your assistance!
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,
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?
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.
“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
Virtual Drive Issue
I have reported this before but not pursue it too much here. I use another drive emulator which works perfectly. But I don’t like computers to win!
The problem is that when I mount an image file, a drive letter is not given, and unmounting the image a) does not clear it from the wizard and b) a second attempt causes a BSOD crash. There are no other issues with my Win 7 x64 installation regarding drive letters or partition management.
The virtual drive does work on other windows setups so something strange is going on. I have searched for similar issues and turned up nothing. I am using the latest drivers, viz SPTDinst-v183-x64.
strange… nobody else reported something similar, maybe something is clashing? Lets see with upcoming 2013, soon.
I have not got a hope in hell of tracking this down as everything else works fine. I can create drive letters without issue too.
The only hope would be if somebody else were familiar with this. Will 2013 deal with the virtual drive feature identically or will it have been modified in some way?
there is some new code so we will see…
After reading some other posts about issues being fixed by an uninstall and then a reinstall, I gave it a go and it’s fixed. UPDATE:-only fixed for one go. Does the uninstall clear out all the registry settings? If not, howcan I start from a default install?
thats strange… beta should be within 7 days.
wait, how come you are not alpha tester?
Still having the problem with the beta (14.00.16).
I am having the same issue with Starburn software (I believe that you used the SDK?) except that Starburn can remove a non-showing drive. These drives to not appear in Disk Management so I cannot manually add a letter.
i wish we could reproduce it here somehow, would give us ability to troubleshoot it.
I am happy to run any tests or debug version or do any registry editing/sleuthing to assist. Do you get any preferential treatment from the StarBurn people as you are developers rather than end users? I have also left a message on their forum.
i’ve got exactly the same problem with the virtual drive.
- i had elby’s virtual clone drive installed.
- uninstalled it, bit didn’t reboot (probably a mistake).
- downloaded and installed virtual drive through patchbeam.
- then tried to mount an iso, which caused windows to try to install a driver, but ended in a loop. tried shutting windows, which didn’t work.
- had to do a hard power off. then reboot.
- after reboot tried again to mount iso, which worked
- dismount iso also worked
- tried mounting the same iso again -> no response
- tried to dismount the iso (which ha no drive letter assigned to it)
- tried again to dismount the iso, which now hat two entrys in the list of mounted drives (again without any drive letters)
i use intel raid storage drivers
I supplied all the info Starburn requested and they could not see anything wrong. They did not reply to my last email (just come back from hols) so have sent them a ‘bump’.
I can mount a virtual drive just fine.
And I can unmount it from the system tray. No problem.
However, the “Unmount virtual drive” from within the Windows shell does not work. I DO get a message near the tray saying that the drive is unmounted. However, the drive still shows as an active drive within Windows explorer.
So the problem I have is just with the shell option.