I thought you had decided to uninstall and not use adaware Lavasoft! In previous threads Pete explained that Lavasoft-adaware has become less than desirable or outdated. It's not the great utility it used to be.
You had agreed to try "superantispyware" instead. I use this myself and find it works well.
Jv16power tools was only suggested as long as lavasoft adaware was still in the picture. No lavasoft means no need for jv16powertools means you can stop struggling with the installation of both.
msvcr90.dll would either be in system32 folder or if a fussy app needs a particular version in the folder where the application is located.
Download Superantispyware and give it shot.
Just for your information: Simplified
MSVCP90.dl is library belonging to the visual basic runtimes. This, as a runtime, is a file that is used by the people who wrote and coded the software, using visual basic (in this case Adaware). There are many versions and many runtime files. Some software expects and needs certain versions. Maybe older or newer. Choose wrong version, corrupted dll or place in an unexpected directory....etc and at runtime or when the application
, dependent on the dll, loads to run, it will spit out an error and not run as expected.
While some applications can be made to work around this issue. In this case the problem you were having was fixed most often with suggested method. Unfortunately you really needed to clean all references to ad
-aware thoroughly before attempting reinstall. Hence suggestion of registry cleaning using jv16tools.
Solution: Forget lavasoft adaware, uninstall and forget jv16power tools, it was only going to be usable for 30 days anyway.
Download and use superantispyware.
Hope this helps to clear some things up for you.
On the flip side, if your continuing to try to install jv16power tools as a mater of principle now, Try turning off any security protection you may have running that would interfere with the installation and running of this jv16.
I, when I installed this did get a popup telling me that jv16 recognized that I had avira antivirus running and that continuing to run this in combination with jv16 could cause kv16 to malfunction. This may hold true in your case.
Please note!!! Pete has suggested you don't not use the desktop shortcut but use the startmenu programs file shortcut instead, you may even wish to go to and run the exe
Phew!!! and if the above isn't enough reading for you and you are still awake how about the below personal experience:
I downloaded this out of curiosity. As you have done:
page1> I clicked on the uncrippled (<-no feature limitations) jv16 PowerTools 2009 30 day trail.
page2> Got curious and didn't fill in email, I just continued to click "download", It worked.
Got dialogue popup to "save" and I chose my desktop as location.
Download was done and have jv16pt_setup_hh.exe sitting on desktop.
Clicked twice on this
Told Uac popup to allow (windows 7 feature, you won't have this, but you need administrator rights)
next! Clicked accept on "license agreement"
next! let it install in "programs files" per default
next! Chose full installation
next! let it put shortcuts in startmenu
next! chose addtional tasks, allowed all shortcut places except quicklaunch
next! setup warning that it was ready to begin, I clicked install button
next! install completed, now asked if I want to open the handbook or the program immediately. Nope and nope, unchecked both.
If given the choice, I always choose to do this as per my own preference.
Now I went the startmenu and chose to start the program from there as opposed to the desktop shortcut, Why? dunno, just did.
Again I had to allow uac.
At this point My memory gets a bit foggy. It had to configure itself with my user preferences. I didn't allow updates, I didn't allow scannow. Once the program (cpl opened with component icons) I used toolbar to allow an update check. From there, I was good to go, did a quick system analysis etc etc.
I did note that the initial configuration stated that it detected my antivirus program running in the background and that this may interfere with the Jv16 functions. I should have temporarily disabled avira but didn't. I would have had I detected that it did indeed cause a problem or conflict, I lucked out this time.