It freezes the system when doing quick scan. Remove the AIsuite completely as per the guide and then install once more. I did what you suggested but I am still getting same warnings and errors. There is major incompatibility between them. For example iControl and bitdefender firewall don't work to-gather well. This update won't install on my system either. This should install without having to remove AI Suite. Note: The file paths I state here are for a 64 bit machine. I imagine that they would differ for a 32 bit machine.
There are actually 4 services background processes responsible in one way or another for making the hotkeys work:.
There is also a copy of AsusService. It can be started and stopped like any windows service. This service seems to act like some sort of a manager for other Asus services. As far as I can tell though, its only function is to launch other Asus Services My information here is based on what I have seen in Task Manager after performing some basic experiments. AsusService launches other Asus services by somehow reading launch requests from AsusSender. These are all started by the AsusService after a request is sent by AsusSender.
This is how its done using the CapsHook utility as an example :. The way I verified this behaviour was through a very simple experiment. I somehow figured out that if I end the HotkeyService. So I performed the following experiment:.
At first I thought this was some sort of registry error that occurred when I upgraded windows, but after I learned how AsusSender is used in the above mentioned situation I thought that these entries must represent SYSTEM calls to AsusSender with different command line args.
Unfortunately, Task Manager does not give information on what each of the command line args are. There were equivalent entries for each of the other 4 services being started at login. The other 4 services were:. Interestingly, it seems that only HotkeyService. You can verify this by ending the HotKeyMon. So it appears that HotKeyMon is another manager type service of some sort like AsusService , and the only function I have seen it perform directly is to monitor whether or not HotkeyService.
Maybe I am missing something, but to me the whole system seems bloated and unnecessarily complex. Launching the service in compatibility mode for Windows 7 seems to resolve this though. I decided to try this because of some other solutions I had read on the internet which did similar things. Probably the problem is as simple as HotkeyService looking for the wrong driver file driver name changed on windows 8 or looking in the wrong location driver file location changed on windows 8.
Unfortunately, at least on my machine, this only resolves the problem of the missing ACPI driver. It does not completely resolve the issue, as afterwards HotkeyService will continuously start, crash, and restart, and the hotkeys will still not work.
The reason for this turned out to be of all things! This was really hard to figure out… This is how I did eventually realize it out though.
Once I got a log file this is what was recorded inside:. Without properly being able to interface with the touchpad this hotkey would not work. However, getting the latest update from the synaptics website did work. View all post by Luca Website. This totally worked!
I have tried everything without succes but after following this guide I could finally adjust my volume with my hotkeys again. Thanks allot! Welcome and thank you for posting your query in Microsoft Community. I suggest you to refer the following discussion and check if it helps.
Let us know if you have any further query on Windows, we are glad to assist you. Was this reply helpful? Yes No. Sorry this didn't help. Thanks for your feedback. Hi, I solved the issue by downloading the driver from another asus model. The KB filter did not work even in compatibility mode. The pop up was still there. What I did discover is this is a tough little computer, even with various changes it keeps plodding along. Computer I've had in the past would have crashed by now.
All good. I haven't tried connecting to a printer yet, til I get home.
0コメント