aldel 0 Posted July 13, 2019 Share Posted July 13, 2019 I've had an issue with my type cover for my surface pro 5 not being recognized when it is plugged in from day one. it happens all the time, using my surface pro is not something i can count on cause of this issue. i have bought both the surface and type cover from major retailers and the correct model, ive tried reinstalling windows, drivers, cleaning the contacts with alcohol. it just wont recognize until it wants to. just today, after it started working, i went into the drivers for the type cover in device manager and was surprised to see one of the 3 drivers being issued by eset. i dont know if this is the problem but it seems likely. its called 'ekbdflt.sys'. snapshot is attached. thanks for any help you can provide! Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted July 13, 2019 Administrators Share Posted July 13, 2019 You can try temporarily uninstalling ESET Internet Security and see if it makes a difference. Link to comment Share on other sites More sharing options...
itman 1,659 Posted July 13, 2019 Share Posted July 13, 2019 (edited) Your Win Device Manger screen shot shows what appears to be two identical entries for HID Keyboard Device. Do you have an external keyboard attached to the Surface Pro? In any case, there might be a conflict there; IRQ sharing, etc.. Edited July 13, 2019 by itman Link to comment Share on other sites More sharing options...
aldel 0 Posted July 15, 2019 Author Share Posted July 15, 2019 Yes I see those. I uninstalled all 3 from device manager and then scanned again and all 3 came back. Tried doing this a while ago too and deleting the driver along with uninstalling. No luck. Link to comment Share on other sites More sharing options...
itman 1,659 Posted July 15, 2019 Share Posted July 15, 2019 On 7/13/2019 at 6:01 AM, Marcos said: You can try temporarily uninstalling ESET Internet Security and see if it makes a difference. Did you try this? If the type error persists with Eset unistalled, Eset is not the source of the issue. Link to comment Share on other sites More sharing options...
aldel 0 Posted July 15, 2019 Author Share Posted July 15, 2019 The problem doesnt happen sometimes for days and I dont want to leave it without protection for an extended period of time, but if it comes down to it I would try that. Hoping I can resolve the issue without doing that. Link to comment Share on other sites More sharing options...
itman 1,659 Posted July 15, 2019 Share Posted July 15, 2019 5 minutes ago, aldel said: The problem doesnt happen sometimes for days This is symptomatic of a hardware issue. If Eset's driver was the issue, it should manifest each time you boot. Link to comment Share on other sites More sharing options...
aldel 0 Posted July 15, 2019 Author Share Posted July 15, 2019 (edited) I was thinking the same thing and its probably true. But then again it does affect certain functionality. For example when I'm logging in with IR webcam it seems to block the first attempt windows does to turn on IR and then it succeeds on second attempt. And I'm in the process of seeing exactly how long I wait from to dismiss the lock screen and seeing if it makes a difference in whether the keyboard works. Just a hypothesis but I think I've seen a pattern where I have to wait a bit but not too long and the keyboard works. Edit: I'm gonna turn on logging for all blocked operations to see if its listed there. Edited July 15, 2019 by aldel Link to comment Share on other sites More sharing options...
aldel 0 Posted July 16, 2019 Author Share Posted July 16, 2019 Any idea why its blocking this csrss.exe? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted July 16, 2019 Administrators Share Posted July 16, 2019 It is normal to get a lot of records like this after enabling logging of all operations. I'd say that only Microsoft knows why is that happening since csrss.exe is a system process, not ours. Most likely it has nothing to do with your issue. Link to comment Share on other sites More sharing options...
aldel 0 Posted July 16, 2019 Author Share Posted July 16, 2019 2 minutes ago, Marcos said: It is normal to get a lot of records like this after enabling logging of all operations. I'd say that only Microsoft knows why is that happening since csrss.exe is a system process, not ours. Most likely it has nothing to do with your issue. But what I'm wondering is why eset is blocking a Microsoft system process? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted July 16, 2019 Administrators Share Posted July 16, 2019 10 minutes ago, aldel said: But what I'm wondering is why eset is blocking a Microsoft system process? Because the system process was attempting to suspend ESET's processes. As to why, only Microsoft knows. Link to comment Share on other sites More sharing options...
Recommended Posts