PSP X5 with SP2: missing Typelib key in registry

[JRosenfeld]

Running Paintshop pro X5 on windows XP pro SP3. Update from SP1 to SP2 was successful, the program behaves normally for those bits I use. However, after installing SP2 a scan of the registry with CCleaner flagged a missing Type lib reference, {2E3D1417-1E33-4145-AF85-A151B9E95302}

This is referenced in the Type lib key under the following keys but is not defined under HKEY_CLASSES_ROOT\TypeLib\

ICorelRipple:
HKCR\Interface\{761E5581-E7DB-46A0-B0AD-DD19747844D6}
ICorelWindTiles:
HKCR\Interface\{80980957-0A6E-4067-B7E2-FD156341965D}
ICorelSlice:
HKCR\Interface\{8D19C5F8-B023-4CB4-B4B5-EBF05F5F8067}
ICorelRefractedPanes
HKCR\Interface\{977E44C2-31EF-4079-A484-FD421BB11E24}
ICorelBlownTiles:
HKCR\Interface\{AC27EBCF-F016-4C40-A85B-AF965FB8AD19}
ICorelWindmill:
HKCR\Interface\{D1B4844B-8FF8-4380-8B02-78146111A6A9}
ICorelSwirl:
HKCR\Interface\{E7466824-2029-4AB9-8246-471F396AD918}
ICorelPanZoom:
HKCR\Interface\{E9CD442F-F69D-471B-9A5A-54B4CA8A145D}
ICorelShapeWipe:
HKCR\Interface\{EF05E487-E1AF-4AD7-9B66-54AB9D431515}
ICorelStrips:
HKCR\Interface\{FBE56E76-DD7D-4309-9ACC-11672988528A}
ICorelPaintStroke
HKCR\Interface\{FD87A717-2DD6-4F1A-8007-9C7B316C243B}

As I don't know what operations in PSP X5 those keys control, I don't know whether anything is broken as a result of the missing typelib key, or indeed whether those registry keys were made redundant by SP2, but not removed by its installation.

Perhaps someone from Corel could advise and, if needed, provide the appropriate reg file to insert the typelib key into the registry, under HKEY_CLASSES_ROOT\TypeLib\.

[photodrawken]

Sigh.

One of the reasons the Windows Registry is somewhat obscured is so that users won't muck it up. If PSPX5 is working fine, then sit back, relax, and enjoy life. Be happy.

Of much greater concern should be the fact that you're long overdue to upgrade to Win7 (or later).

[LeviFiction]

For the longest time Geeks and Nerds were recommending that people clean their Registry to prevent unused entries from interfering with normal Windows operations and potentially slowing down the system. But eventually these cleaners will try to clean something unnecessary or potentially harmful and end up being the exact same thing that causes problems in the first place. They are just as capable of erasing the good as well as the bad. So I suggest you stop using CCleaner to clean your registry.

Here is a post that quotes a blog maintained by a recipient of Microsoft's MVP awards. It should give a decent overview of why you don't want to use a registry cleaner if you can avoid it.

http://chris.pirillo.com/are-registry-c ... fe-to-use/

[hartpaul]

Your key statement:

the program behaves normally for those bits I use.

So what is your problem? Don't worry about ghosts , use the program and enjoy it.

[JRosenfeld]

You have perhaps misunderstood my reasons for posting:

I am an experienced user. I am quite familiar with most aspects of the registry, not addicted to 'cleaning' the registry per se, but I do like to check after installing software or update, whether there are changes in the registry that appear to indicate a faulty install or potentially missing keys (not an uncommon experience in commercial software). I have generally found it helpful when some software does misbehave in one or other way as it may help to diagnose problems.

The fact that those apparent errors in the registry after updating to SP2 have not broken any of the (relatively limited) parts of PSP X5 that I use does not necessarily imply that some other functions, that I happen not to have tried, may be broken. Thus it may be helpful to others to know whether there is a missing type lib, or whether those other keys are redundant.