Problem Installing R17

[flourbag81]

Re: Problem Installing R17

Hi
Yes, that allowed it to install thanks.
Onviously something about R17 that Kaspersky doesn't like as previous installs presented no problems
Still, all is good now so I'll let somebody else worry about the problem

[Dat Ei]

Re: Problem Installing R17

Sounds like a false positive by your security software. Can you disable it for a test?


Dat Ei

[flourbag81]

Re: Problem Installing R17

The message box pops up instantly after double clicking the exe file

[Spoon-]

Re: Problem Installing R17

When you run the install does it show some files installing and it gets stuck later on, or seems to be the first file?

[flourbag81]

Re: Problem Installing R17

I have just purchased R17 and when I try to install it I get the message "unable to extract a file from install"
I've checked my AV software, Kaspersky, and can't see anything there
I retried R16.5 and that ran perfectly
Is there something different about R17 or have I got a faulty file?

[Spoon-]

Re: Problem Installing R17

You are best to uninstall.

[Dillydipper]

Re: Problem Installing R17

I've got V.14 still on my workstation. Should I uninstall all V.14 utilities before installing V.17, or does it go nicely right on top of them?

[Spoon-]

Re: Problem Installing R17

You can safely ignore that entry.

[joemusic75]

Re: Problem Installing R17

See:

https://forum.dbpoweramp.com/showthr...625*post197625

Hello, thank you, I did what you mention in the other post and here is what I found inside the "HKEY_LOCAL_MACHINE\SYSTEM\\CurrentControlSet\\Con t rol\\Session Manager" folder:

\??\C:\Program Files\Common Files\McAfee\ClientAnalytics\Plugins\clock


Now, do I need to do something about it?

Thanks!

[Spoon-]

Re: Problem Installing R17

See:

https://forum.dbpoweramp.com/showthread.php?44992-Installer-asks-to-reboot-PC-before-install&p=197625*post197625

[joemusic75]

Re: Problem Installing R17

Hello!
Please Im having exactly the same problem:
1)I installed the trial versión of dBpoweramp Reference [Music Converter & CD Ripper] for afew days
2)I decided to buy the full version
3)I uninstalled the trial version
4)I paid for dBpoweramp Reference [Music Converter & CD Ripper]
5)I downloaded dBpoweramp Reference [Music Converter & CD Ripper]
6)I tried to install dBpoweramp Reference [Music Converter & CD Ripper]
7)I got a message error telling me that there are pending uninstall actions and that I need to restart the PC
8)I restarted PC several times but didn't work
9)I turned off PC for 30 minutes then turned it on again I tried installing and still got the same message error
10)I searched for any single file in my PC that had "poweramp" as part of its name
11) I found a few files that had "poweramp" as part of their name
12) I deleted them all
13) I restarted PC
14) I tried installation but still the very same error message telling me there are uninstall stuff pending
15) I got tired and I just click the option "yes, continue no matter what in spite it is not recommended"
16) Installation was succesful

Now, what do you think? Should I do something now?
Maybe unistall it and re install it again?
Maybe just leave it as is?
Please, help, thanks"

[Gavin Blackett]

Re: Problem Installing R17

Thanks, Spoon, I've ignored the warning (despite it sounding quite dire to do so) and the install has completed.

[Spoon-]

Re: Problem Installing R17

You can force the install, sometimes uninstall actions stick in the registry, so it can be ignored if you have restarted the PC.

[Gavin Blackett]

Re: Problem Installing R17

Or rather not entirely solved. Since I've got a family pack registration I tried installing it on a 'virginal' PC elsewhere in the house - and I got the same message. Again, a simple re-boot didn't work. Any idea how I track down the impending action?

[Gavin Blackett]

Re: Problem Installing R17

Problem solved! I took a guess that it was dbPoweramp itself that was pending an uninstall. I uninstalled manually, re-booted and the R17 installation has now worked. I'm not sure if I did something wrong initially but I guess this could be a bug?