| Subject: Unable To Create RegHelper |
| Group: microsoft.public.internetexplorer.general |
| Date: 7/22/2008 1:50:07 PM |
| From: =?Utf-8?B?dGVuZ2Vs?= [Email Address Protection] |
I think I've found another problem with Update KB950759 which I installed on 6/29/08, and I'm hoping that someone can help. I use McAfee software provided by Comcast for virus protection, and after 6/29 the next automatically scheduled weekly virus scan would have run on 7/4 but it didn't. The last successful scheduled scan was on 6/27, just two days before the KB950759 installation. When I open McAfee Security Center and ask it to run a manual scan, I get the following error message inside of a Windows Internet Explorer box that says: Unable To Create gObjRegHelper{6A5A9B2E-3BD7-4c70-83F2-E664A86568F4} If I click OK in that box, I can run the manual scan, but I'm not able to set up an automated schedule anymore. The fact that this problem started right after the KB950759 installation (which is a security update for IE7) and the error message is coming from IE, leads me to believe that the problem is somehow related to the update. What do you think? -- Tom Engel |
| Back |
| Subject: Re: Unable To Create RegHelper |
| Group: microsoft.public.internetexplorer.general |
| Date: 7/22/2008 4:56:11 PM |
| From: "PA Bear [MS MVP]" [Email Address Protection] |
What Leonard said. PS: KB950759 was released almost 2 months ago: Why did you wait 6+ weeks to install it? -- ~Robear Dyer (PA Bear) MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002 AumHa VSOP & Admin http://aumha.net DTS-L http://dts-l.net/ tengel wrote: > I think I've found another problem with Update KB950759 which I installed > on > 6/29/08, and I'm hoping that someone can help. > > I use McAfee software provided by Comcast for virus protection, and after > 6/29 the next automatically scheduled weekly virus scan would have run on > 7/4 but it didn't. The last successful scheduled scan was on 6/27, just > two > days before the KB950759 installation. > > When I open McAfee Security Center and ask it to run a manual scan, I get > the following error message inside of a Windows Internet Explorer box that > says: > > Unable To Create > gObjRegHelper{6A5A9B2E-3BD7-4c70-83F2-E664A86568F4} > > If I click OK in that box, I can run the manual scan, but I'm not able to > set up an automated schedule anymore. > > The fact that this problem started right after the KB950759 installation > (which is a security update for IE7) and the error message is coming from > IE, leads me to believe that the problem is somehow related to the update. > What do you think? |
| Back |
| Subject: Re: Unable To Create RegHelper |
| Group: microsoft.public.internetexplorer.general |
| Date: 7/22/2008 7:50:54 PM |
| From: "Robert Aldwinckle" [Email Address Protection] |
"tengel" <tengel@discussions.microsoft.com> wrote in message news:11E6E5B7-9153-441C-8A90-40A54EB75B94@microsoft.com... >I think I've found another problem with Update KB950759 which I installed on > 6/29/08, and I'm hoping that someone can help. > > I use McAfee software provided by Comcast for virus protection, and after > 6/29 the next automatically scheduled weekly virus scan would have run on 7/4 > but it didn't. The last successful scheduled scan was on 6/27, just two days > before the KB950759 installation. > > When I open McAfee Security Center and ask it to run a manual scan, I get > the following error message inside of a Windows Internet Explorer box that > says: > > Unable To Create > gObjRegHelper{6A5A9B2E-3BD7-4c70-83F2-E664A86568F4} Could be a permissions thing. ProcMon would help. > > If I click OK in that box, I can run the manual scan, but I'm not able to > set up an automated schedule anymore. Another possible sign of a permissions thing. E.g. what account is the "automated schedule" run under? ProcMon or even Process Explorer could help with that too. > > The fact that this problem started right after the KB950759 installation > (which is a security update for IE7) and the error message is coming from IE, > leads me to believe that the problem is somehow related to the update. What > do you think? Depending on how the McAfee thing is hooked in it could be that the install of the update has broken its hooks. In that case I would uninstall the extension and reinstall it, hoping that it was still compatible enough to be reinstalled completely. If you can't figure it out I suspect you need to talk with someone at McAfee who provides more than first level support. ; ) Good luck Robert Aldwinckle --- |
| Back |