My desktop has been crashing frequently and the Event Viewer shows "The HID Input Service service terminated with the following error:
The system cannot find the file specified." A little research showed this is because the file hidserv.dll only appears in my registry in a couple of obscure places. I was able to download a hidserv.dll file and tried to register it in a couple of ways from the command prompt. First I used regsvr32.exe and got the error message "hidserv.dll was loaded but the DllRegisterServer entry point was not found. This file can not be registered." Tried several times with same result.

Then I tried using regasm.exe and always get the error "hidserv.dll is not a valid .net assembly."

Can anyone advise me how to register hidserv.dll? Or, short of that, how can I avoid these mysterious crashes. The first event that occurs just before the cursor freezes is "Unable to load C:\WINDOWS\System32\iprtrmgr.dll." That is followed by "The HID Input Service service
terminated...." So I guess the triggering event is related to my HP all-in-one printer. I did look in my HP installation CD and hidserv.dll is not there.

(As I'm sure you all know, HID stands for Human Interface Device, which certainly applies to my HP printer/scanner.)

Details: computer is running Windows XP with all UPDATES & service packs. 2.8 gigahertz, 2.5 GIGS memory, 166 gigs free hard drive space. Just installed Net Framework v 4.

Thanks for any help.

AlanIf it is a .NET thing, try to un install and re install the version of .NET you need.
Do you know EXACTLY which program requires the .NET stuff?
Is "not a valid net assembly" what you mean by a ".NET thing?" Actually I installed v 4 of net framework TWO times. Once a few days ago after which I had the same problem registering then again yesterday after doing a Restore, requiring that I install net framework v 4 again. Both times the registration failed using regasm. Are you suggesting I uninstall/reinstall again?Installation of the .NET package should not require manual registration of components in most cases. The recommended practice is to fully remove a faulty package and then repair any other errors and install the package again. That is one of the reasons they give specific details about un-install issues.

blogsMSN
Silent install, repair and uninstall command lines for the .NET Framework 4

blogsdna (windows 7)
How to Completely Uninstall .Net Framework On Windows 7