Skip to main content

Windows 键盘问题一例

今天打开电脑，进入Windows，登陆时竟然发现键盘不能用！冷静了一下后用软键盘登了，登陆后发现还是不行！

于是用鼠标和软键盘操作，看Device Manager,键盘设备有个黄叹号，设备状态里显示

Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged (code 19)

Google之，在http://www.edmartechguide.com/2009/02/windows-cannot-start-this-hardware.html里得到线索

于是进入Regedit，在HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class项下逐个检查，直到找到{4D36E96B-E325-11CE-BFC1-08002BE10318}，发现Class值是Keyboard，那么应该就是这项了

由于权限问题，改名和删除都不行，于是仔细观察各项，发现"UpperFilters"里有个可疑的alidevice，于是删掉，把"kbdclass alidevice"改成"kbdclass"

然后去Device Manager里Uninstall键盘设备，然后刷进，于是可以用了。

这样看来，应该是淘宝的驱动挂了，或者是让我搞挂了。

另外是Device Manager里的PS/2鼠标也不能用，这里是我笔记本上的触摸板。我用的鼠标是USB的，不过注册表里没有发现可疑项，重启以后自然能用了。

另外庆幸我的USB鼠标还能工作，否则输入设备一个都没了。。。好险
Labels:

Comments

Post a Comment

Popular posts from this blog

A Rocky Migration: Moving from docker-compose to Podman and gVisor

I've been running a few containers for several years. They were all running under rootless Docker with a single user. Initially, I planned to  migrate the containers to VMs , but I couldn't get a stable workflow after about two months of effort. Later,  gVisor caught my attention , and I decided to migrate to Podman with gVisor instead. The new plan is to run each container with  --userns=auto  and use Quadlet for systemd integration. This approach provides better isolation and makes writing firewall rules easier. I'm now close to migrating all my containers. Here are a couple of rough edges I'd like to share. Network Layout I compared  various networking options  and spent a few hours trying the one-interface-per-group approach before giving up. I settled on a single macvlan network and decided to use static IP addresses for my containers. To prevent a randomly assigned IP address from conflicting with a predefined one, I allocated a large IP range for my ...
Post a Comment
Read More »

Exploring Immutable Distros and Declarative Management

My current server setup, based on Debian Stable and Docker, has served me reliably for years. It's stable, familiar, and gets the job done. However, an intriguing article I revisited recently about Fedora CoreOS, rpm-ostree, and OSTree native containers sparked my curiosity and sent me down a rabbit hole exploring alternative approaches to system management. Could there be a better way? Core Goals & Requirements Before diving into new technologies, I wanted to define what "better" means for my use case: The base operating system must update automatically and reliably. Hosted services (applications) should be updatable either automatically or manually, depending on the service. Configuration and data files need to be easy to modify, and crucially, automatically tracked and backed up. Current Setup: Debian Stable + Docker My current infrastructure consists of several servers, all running Debian Stable. System Updates are andled automatically via unattended-upgrades. Se...
Post a Comment
Read More »

mkosi: First Impressions

I stumbled upon the Gentoo wiki page for systemd-nspawn , which in turn led me to nspawn.org , mkosi , and later systemd-sysupdate . mkosi quickly caught my eye because it's almost exactly what I wanted to build myself, as mentioned in a previous post . So, I decided to spend my "sysadmin fun quota" on it. Overview mkosi is similar to docker build or podman build , but it's designed for creating full OS images. It focuses on development and testing. For example, much like nix-shell , mkosi can quickly launch a sandboxed shell with a specific distribution and selected packages installed. The systemd project itself uses mkosi for testing across different distros. The re-introduction article  is a great read. Speed Note that this is by no means a rigid benchmark. My setup is an SSD with LUKS and an ext4 filesystem (without reflink support). Building Container Images mkosi is pretty fast. A simple mkosi command creates a fresh Debian image. I used the --incrementa...
Post a Comment
Read More »