BETA: PowerArchiver 2023 - 22.10.02

[Mr-Fly]

No Problem.
It actually appears right after installation and at every start.
First installation was an upgrade from Beta 3.
I am running a Windows XP Multi-Language Edition with German Language-Pack running (this is also stated in my signature btw.).

I just have to start PA for it to happen. It is reproduceable every time.
I did a full uninstall and then tried to reinstall with no change :-(

[spwolf]

nice, thank you!

[Mr-Fly]

Shell extension is also not working at all.
Neither extract to… nor Extract to folder.
An open through double click will open powerarchiver, give the error on start and then will NOT load the double tabbed zip.
I have to manually open the file through the menu.

Regards
Fly

[spwolf]

did you try restarting after installation?

what is double tabbed zip?

thanks,

[Mr-Fly]

yes, restarted a couple of times.
before install, after install, before deinst etc.

tabbed should have meant tapped :-)
just a typo.

Regards and good night
Thorsten

[Mr-Fly]

Ok, now I am really stuck.
The beta3 installation does not work anymore.
It comes up with a requester showing the temp-directory as installation source.
I never got the PA to uninstall correctly, so I had to stop the process.
it looks like the MSI installation is buggy as it does not react on some situations.

I will try to clean my system if possible.

Regards Thorsten

[Mr-Fly]

Maybe it helps.
Anytime the installation stucks, the _PASetup.exe takes nearly 100 % CPU and will never stop.

[spwolf]

did you uninstall Beta 4 properly through Add/Remove programs?

[spwolf]

If you cant, because you deleted files from the folder, download Beta 4 again and run it… it will give you an option to Uninstall then.

[Mr-Fly]

Ok.
I have found the problem.
Somehow the permissions on the HKCU\Software\Powerarchiver was not set right.
Administrator had only read-access.
This leads to the problem, that the deinstall hangs, the start cannot write the settings, so that seems to be the message.

Kind Regards
Thorsten

[ivan]

Although I don’t know who set read-access rights, I have done some changes so this error message doesn’t show in the future even if the access is read-only.