less than 1 minute read

In case you’re using Windows (or Microsoft) Update, you’ll probably have noticed that your PC sometimes grinds to a halt after bootup. Checking with task manager usually reveals that svchost.exe is abusing your CPU, pegging it at 100%.

This thread specifies several solutions that you can try, and for me what helped was:

  • installing KB927891
  • installing Windows Update Agent 3.0 (x86 / x64)
  • cleaning of the SoftwareDistribution folder:
    1. Open a command prompt
    2. net stop wuauserv
    3. Rename Windows\SoftwareDistribution folder to SoftwareDistribution.old
    4. net start wuauserv
    5. Reboot

Doing the combination of these fixes (in this order) finally made svchost behave like it should. Look in the thread for more possible fixes ;)

Updated:

Leave a comment

You may also enjoy

Using IPv6 outside of Docker with Docker

1 minute read

I recently activated IPv6 on my Netcup VPS, and in the process of setting it up on all my LXCs I noticed that for “reasons” the IPv6 default route would vanish after starting Docker (switching it all over to Podman is on my TODO list), effectively breaking the IPv6 connectivity on this LXC.

Enabling native IPv6 on Proxmox and LXC using SDN

3 minute read

In my original deployment of Proxmox on my VPS I only enabled IPv4, and I was using socat to forward traffic from the IPv6 address of the host to the internal IPv4 addresses of the containers. Not ideal, since this masks the external IP addresses, and also creates some latency and additional CPU load when processing IPv6.

Proxmox, LXC, and Debian Trixie

3 minute read

I run Proxmox Virtual Environment as my virtualisation platform. On top of this I use virtual machines using KVM and Linux Containers using LXC - both of which are natively supported on ProxmoxVE.

Code storage

1 minute read

Code, and where to store it