Hi Jose,
Have copied and saved as suggested and attached.
Also attached is an error in the "Application" section re"Server service,
however on checking running services the "Server" service is in fact
running.
Back to lkbdhlpr, The event which shows this error is actually the very 1st
event recorded on each startup, so it is difficult to see how it can be
affected by another event.
Thank you for your tip re registry, I have downloaded and used ERUNT.
Regards
Teriel9
"Jose" <jose_ease@yahoo.com> wrote in message
news:7d29a487-a79b-4242-993e-c243cf9a145a@q23g2000yqd.googlegroups.com...
On Mar 24, 12:06 pm, "Teriel9" <te...@teriel-consultants.co.uk> wrote:
> In my Event Viewer an error occurs each time I start up "Cannot load file
> "lkbdhlpr"
> I have tried vaious options to get rid of it
> Removed and Reinstalled Logitech Software
> Changed file suffix to .old
> Located and tried to delete registry entry for "Legacy lkbdhlpr" given an
> error "Cannot remove"
> Tried the same thing in safe mode, no change, on reflection, since it is
> called for by windows, safe mode would probably still call for it.
>
> I note that there are 2 kinds of lkbdhlpr file one is .sys the other is
> .vxd
> All files with lkbdhlpr in the name have been deleted.
> Can anyone help please
> TIA
> Teriel9
Is this the same problem you had in 2006?
If you are seeing error messages, try to post exactly what they say -
don't try to put it in your own words. Do you really see a message
that says "Cannot remove" or does it really say something else?
Did you decide to edit the registry after reading about some solution
to your issue or is it just a hunch? Do you think it is a good idea
to backup your registry before you start trying things?
Before making any changes to your registry by hand or with third party
tools, be sure to make a backup of the registry first. Here is a link
to a popular registry backup tool:
http://www.larshederer.homepage.t-online.de/erunt/
You have not specified any particulars about your system and your BIOS
information is unknown, but you can provide that and we can help you
look up the documentation instead of just guessing what might be. You
need to also provide the exact message from the Event Log.
Click Start, Run and in the box enter:
msinfo32
Click OK, and when the System Summary info appears, click Edit, Select
All, Copy and then paste back here.
There will be some personal information (like System Name and User
Name), and whatever appears to be private information to you, just
delete from the pasted information.
Here is a method to post the specific information about individual
events.
To see the Event Viewer logs, click Start, Settings, Control Panel,
Administrative Tools, Event Viewer.
A shortcut to Event Viewer is to click Start, Run and in the box
enter:
%SystemRoot%\system32\eventvwr.msc /s
Click OK to launch the Event Viewer.
The most interesting logs are usually the Application and System.
Some logs may be almost or completely empty.
Not every event is a problem, some are informational messages that
things are working okay and some are warnings.
No event should defy reasonable explanation.
Each event is sorted by Date and Time. Errors will have red Xs,
Warnings will have yellow !s.
Information messages have white is. Not every Error or Warning event
means there is a serious issue.
Some are excusable at startup time when Windows is booting. Try to
find just the events at the date
and time around your problem.
If you double click an event, it will open a Properties windows with
more information. On the right are
black up and down arrow buttons to scroll through the open events. The
third button that looks like
two pages on top of each other is used to copy the event details to
your Windows clipboard.
When you find an interesting event that occurred around the time of
your issue, click the third button
under the up and down arrows to copy the details and then you can
paste the details (right click, Paste
or CTRL-V) the detail text back here for analysis.
To get a fresh start on any Event Viewer log, you can choose to clear
the log (backing up the log is offered),
then reproduce your issue, then look at just the events around the
time of your issue.
WINDOWS