Software Uninstaller Inconsistent

ckag

I am using v550 on an XP SP3 machine and a Vista Home Premium machine. I find that the Software Uninstaller is inconsistent. I have been using jv16pt for some years now so I'm relatively familiar with its operation. Getting back to the inconsistency, it seems to work on some programs but not others. Specifically, it will not remove Adobe Shockwave. This has been happening for a couple of versions of both jv16pt and Shockwave. Since jv16pt has been in flux, I've just been waiting for a fix but I thought I'd speak up now.

Typically, I use Add/Remove to uninstall software. Then I run jv16pt Software Uninstaller (I like Software Manager better..<grin>..) to remove any leftover threads as well as any related 3rd party threads. Finally, I run the Registry Cleaner to remove any leftovers.

As noted above, Software installer works most of the time but it barfs on Adobe Shockwave v11.5.0.595. Same-same for the previous version of Shockwave. The uninstaller starts (bar meter appears) and then it stalls. I've waited for 5 minutes for it to complete and it doesn't.

HOWEVER, if I skip the Add/Remove step and use only jv16pt Software Uninstaller, then the Software Uninstaller works. In that test, when I clicked on Uninstall, the Adobe remover popped up momentarily and then the Software Uninstaller meter came up and completed.

I also tried using Software Uninstaller *after Add/Remove) to remove the last traces of Adobe Reader v9.1 with the same stall. Hence, it may just be the Adobe stuff that is barfing Software Uninstaller.

jv16

Could you try to run the Uninstall to Adobe Shockwave with Debug Mode enabled? After the program hangs, wait a few minutes, kill it and then send me the debug log it created, could you please do that for me? It would help me to fix the problem.

ckag

>> could you please do that for me? It would help me to fix the problem. <<

OUCH!.. Normally, I would be more than happy to do that for you. Alas, I'm up to my neck in alligators just now and am trying to get ready to go out of town for a week.

I'll try to scrape together some time to do the test but I can't promise it. If I don't get it done this week, then I'm sure I can do that for you in a couple of weeks when I get back home.

ckag

>> It would help me to fix the problem. <<

Okay.. I made the time to do the debug. I am attaching the two debug files that were generated.

As is my usual routine, I used Add/Remove to uninstall Adobe Shockwave v11.5.0.595. I then loaded jv16pt (in debug mode), got into the Software Uninstaller, and attempted to remove the leftover Shockwave entry. As expected, the bar meter came up and then jv16pt stalled. I waited about 5 minutes before closing jv16pt. I zipped the 2 log files that were generated and am attaching it here.

anwaypasible

adobe shockwave (the recent version) was slow to uninstall using the jv16 software uninstaller on my computer.

when i tried to uninstall shockwave with the windows xp add/remove software.. i got a message popping up telling me that the install log could not be found.

so i used the jv16 software uninstaller to get rid of shockwave.

indeed, the progress bar was slow.. but eventually the list of related registry keys was compiled in the window for deletion.

BUT but..

i am having the same barf stall when trying to uninstall mozilla firefox.

the reference that jv16 is giving me dates back to december 13th 2008.. and i dont remember installing the browser.

it was probably a one day trial to compare performance against internet explorer.

anyways.. mozilla firefox is not listed in the windows xp add/remove software.

my only choice seems to be using jv16's software uninstaller.

and the progress bar hasnt moved in the passed 15 minutes.

i've only got a 2gb solid state IDE flash drive in this laptop so keeping things clean is a MUST.

i'm down to about 111MB of free space and i have come across this problem while doing some routine cleaning.

so to the original poster.. NO it is not just an adobe thing.

jv16

I think I know what's the problem. So ckag, you have PowerTools installed to "C:\Program Files\jv16 PowerTools\", right? According to the debug log, one important file is missing "C:\Program Files\jv16 PowerTools\Settings\MetaDB.xbin".

I think PowerTools doesn't properly handle the case of that file being missing, and that causes the problem.

jv16

This problem should now be fixed, thank you for reporting! The fix will be included to the next released version due out later in this month.

ckag

Sorry for the late reply.. Just got back from a trip. I try not to do computers when I'm on vacation...<grin>..

Glad to hear that the fix is in. I'll be looking forward to the new version.

ckag

Okay.. 552 seems to have fixed the Software Uninstaller problem re Adobe Shockwave v11.5x. It's not as snappy as I'm used to, but after a couple of minutes it did seemingly complete. This is on my XP SP3 desktop.

The HP Vista Home Premium laptop is another story. I installed 552. At the end where you have the option to start jv16pt (default is to start it), I unchecked the "start jv16pt" and clicked Finish. After that, my laptop was useless. I had to drop the battery out of it in order to turn it off and restart in Safe Mode. In Safe Mode, I set up CHKDSK on all of my partitions and rebooted. The CHKDSK completed without problems. I then tried to reboot into normal mode and Vista never completed loading.

I'm pressed for time the rest of today and tomorrow so I'm just restoring back to my previous condition from a True Image backup. I'll re-try the install of 552 when I get a chance. I have no idea what went salty. I don't know if it was just a freak occurrence or if something is truly conflicting with the install of 552.

davidco

552

MetaDB.xbin still missing, this after an over-install

Weird flickerings going on.

ckag

Re my HP Vista Home Premium laptop, I eeked out another hour out of today so after the restore from image, I tried installing 552 again. Same result, nothing worked after the install. This time, I let jv16pt start when I clicked on Finish. Same result. I am again restoring from image. This is definitely the end of the road for testing for me for a couple of days. No more time.

ckag

P.S. While 552 seems to be working on my XP SP3 desktop, there is no MetaDB.xbin in Settings. There is, however, a MetaDB.xdat in Settings, if that makes a difference.

tullik

ckag wrote
P.S. While 552 seems to be working on my XP SP3 desktop, there is no MetaDB.xbin in Settings. There is, however, a MetaDB.xdat in Settings, if that makes a difference.

MetaDB.xdat is the correct name.

ckag

EUREKA!.. IT WOIKS!...

Seriously, the new 580 now works on both my XP SP3 desktop and my Vista Home Premium SP1 laptop, at least from my perspective (the stuff I use). It takes a little more than a minute for the Software Installer to remove Shockwave, but at least it gets the job done.

One note, on the Vista laptop, jv16PT does NOT play nice with my AV, which is Eset's NOD32 v3.x. If the AV is enabled, it takes 3min 10 secs for jv16pt to load. Without the AV enabled, jv16pt loads as one might expect. I'm using the same AV on the XP SP3 desktop and jv16pt loads okay there (don't need to disable the AV).

boofo

Add jv16PT.exe to the NOD32 ignore list.

ckag

>> Add jv16PT.exe to the NOD32 ignore list. <<

Yah.. I thought about that but in the end decided that it was just as easy to disable NOD32 and then turn it back on again. It's just 2 mouse clicks in each direction.

boofo

I would add it to the ignore list. NOD32 is known for taking its sweet time on scanning certain files. Disabling the AV is never an option as you have no idea what can slip through in the interim.

roberta

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

ckag

>> Disabling the AV is never an option as you have no idea what can slip through in the interim. <<

Okay, you guys twisted my arm.. I'll go that route. Thanx!

boofo

Please let us know if that fixes your slow-starting problem.