TrueShadow21

Since I purchased my Vista 64-bit laptop a few months ago I have been experiencing a bug in CCleaner where it deletes regestry keys belonging to my Synaptics Touchpad drivers and this stops them from functioning. The touchpad still works (probably falling back on a generic driver included by Vista) but the scroll bars (the edge of the Touchpad that servers the equivalent function as the scroll wheel) do not function at all. There is also a failed to start or crash error (can't remember exactly) whenever I login. I've been able to get the driver working again by reinstalling it, but any time I run the regestry cleaner without unchecking all the Synaptics touchpad entries, the problem arises again. To help with fixing this issue, I've saved a text file listing the Synaptics registry keys that were deleted. ActiveX/COM Issue Synaptics.AbsTouchPad - {2A833A93-6641-11D3-B5FE-00104B0A87C2} HKCR\Synaptics.AbsTouchPadActiveX/COM Issue Synaptics.AbsTouchPad.1 - {2A833A93-6641-11D3-B5FE-00104B0A87C2} HKCR\Synaptics.AbsTouchPad.1ActiveX/COM Issue SynCom.PointingDevice - {9345312C-D098-4BB1-B2B2-D529EB995173} HKCR\SynCom.PointingDeviceActiveX/COM Issue SynCom.PointingDevice.1 - {9345312C-D098-4BB1-B2B2-D529EB995173} HKCR\SynCom.PointingDevice.1ActiveX/COM Issue SynCom.PointingDevice.2 - {9345312C-D098-4BB1-B2B2-D529EB995173} HKCR\SynCom.PointingDevice.2ActiveX/COM Issue SynCom.PointingDevice.3 - {9345312C-D098-4BB1-B2B2-D529EB995173} HKCR\SynCom.PointingDevice.3ActiveX/COM Issue SynCom.SynAPI - {9C042297-D1CD-4F0D-B1AB-9F48AD6A6DFF} HKCR\SynCom.SynAPIActiveX/COM Issue SynCom.SynAPI.1 - {9C042297-D1CD-4F0D-B1AB-9F48AD6A6DFF} HKCR\SynCom.SynAPI.1ActiveX/COM Issue SynCom.SynDisplay - {248AFB1A-27C4-4A30-BF45-6544146648BC} HKCR\SynCom.SynDisplayActiveX/COM Issue SynCom.SynDisplay.1 - {248AFB1A-27C4-4A30-BF45-6544146648BC} HKCR\SynCom.SynDisplay.1ActiveX/COM Issue SynCom.SynDisplay.2 - {248AFB1A-27C4-4A30-BF45-6544146648BC} HKCR\SynCom.SynDisplay.2ActiveX/COM Issue SynCom.SynPacket - {E0C6335D-27F8-424B-A5C2-561291A902A0} HKCR\SynCom.SynPacketActiveX/COM Issue SynCom.SynPacket.1 - {E0C6335D-27F8-424B-A5C2-561291A902A0} HKCR\SynCom.SynPacket.1ActiveX/COM Issue SynCom.SynPacket.2 - {E0C6335D-27F8-424B-A5C2-561291A902A0} HKCR\SynCom.SynPacket.2ActiveX/COM Issue SynCtrl.SynAPICtrl - {F418EBA0-6A10-4482-AC2B-2D10C807073A} HKCR\SynCtrl.SynAPICtrlActiveX/COM Issue SynCtrl.SynAPICtrl.1 - {F418EBA0-6A10-4482-AC2B-2D10C807073A} HKCR\SynCtrl.SynAPICtrl.1ActiveX/COM Issue SynCtrl.SynDeviceCtrl - {2060435E-AB52-49E1-A2EA-5D31645887CF} HKCR\SynCtrl.SynDeviceCtrlActiveX/COM Issue SynCtrl.SynDeviceCtrl.1 - {2060435E-AB52-49E1-A2EA-5D31645887CF} HKCR\SynCtrl.SynDeviceCtrl.1ActiveX/COM Issue SynCtrl.SynDeviceCtrl.2 - {2060435E-AB52-49E1-A2EA-5D31645887CF} HKCR\SynCtrl.SynDeviceCtrl.2ActiveX/COM Issue SynCtrl.SynDisplayCtrl - {206D8F65-689B-40D0-8F07-8D974CD8884B} HKCR\SynCtrl.SynDisplayCtrlActiveX/COM Issue SynCtrl.SynDisplayCtrl.1 - {206D8F65-689B-40D0-8F07-8D974CD8884B} HKCR\SynCtrl.SynDisplayCtrl.1ActiveX/COM Issue SynCtrl.SynPacketCtrl - {a220a2df-406f-4d68-9b62-995669ae0c92} HKCR\SynCtrl.SynPacketCtrlActiveX/COM Issue SynCtrl.SynPacketCtrl.1 - {a220a2df-406f-4d68-9b62-995669ae0c92} HKCR\SynCtrl.SynPacketCtrl.1 I believe this bug has been around a while, because I also found this post by Pfipps dated March of '07. Thank you for any assistance you may be able to provide, and I hope to see this fixed in future releases of CCleaner. registry.txt registry.txt