IMGBurn right-click problem

[setarip_old]

On a system running XP Pro SP3, in Explorer, rather than popping up immediately as properly happens with ANY other program, rightclicking on the filename of any version of "IMGBurn.exe" (and ONLY "IMGBurn.exe") results in an inordinate delay (close to or more than one full minute) until the options appear (e.g. "Open", "Properties", etc.) and an additional lengthy delay if "Properties" is then selected.

This odd behavior occurs regardless of version, relocating on the same hard drive, or locating on a different drive and/or partition.

Can anyone provide an explanation for this unusual behavior?

[blutach]

Doesn't happen here. Are you getting hover info?

Try to see what is going is with Process Explorer and Process Monitor. Maybe your virus checker is doing its thing.

Regards

[setarip_old]

Are you getting hover info?Yes - and it appears promptly
Maybe your virus checker is doing its thing.As I said, this happens ONLY with "IMGBurn.exe" and not any other file on this system, so that suggestion seems to defy logic.

Thanks anyway...

[Sharktooth]

doesnt happen here. check your shell extensions.

[setarip_old]

@Sharktooth

Hi!check your shell extensions.For what, specifically?

BTW - A correction that makes this even more curious - Rightclicking on "DVDDecrypter.exe" and selecting "Properties" both exhibit the same significant delay!

I've randomly checked well over 100 other program files and none exhibit this behavior.

Is it possible that there is some kind of registry conflict created by having both programs installed?

[Inventive Software]

I have both installed, and no problems that you mention. I'd use JkDefrag just to get the HDD in order and then see if the problem still arises.

[blutach]

Have you used Process Monitor like I suggested? Some checker is probably getting in the way. Also, try in safe mode. If this has just started, do a system restore.

Regards

[setarip_old]

@Inventive Software

Hi!

I'd already defragged the hard drives - no change in the behavior.

I just installed both programs on another system and it doesn't exhibit the unusual behavior either so I guess I'll do some further research...