Zoom Cannot Start Video With Older Webcams in Windows 10

I've had a Logitech QuickCam Fusion webcam since around the time Windows 7 was still mainstream. Other than from my work laptop I don't do online meetings so the camera largely went unused on my home desktop, even after upgrading to Windows 10. 

Then, one day my wife and I installed Zoom and wanted to test it out prior to her joining some Zoom calls with some of her old high school classmates. While her setup with Windows 10 and a relatively new (ca. 2021) webcam worked flawlessly, mine did not. Repeatedly Zoom would complain whether in the video settings or upon joining a meeting, "Cannot start video":

My solution took some trial and error but ultimately worked. First, unplug your webcam from its USB port, and then open Device Manager, and under Imaging devices, right-click on Logitech QuickCam Fusion (or whatever your older webcam is):

Ensure "Delete the driver software for this device" is checked so that whatever driver Windows may have initially used is removed, then click Uninstall and follow any prompts to remove the drivers:

Next, download and install the latest available drivers you can find for your old webcam, ideally for Windows 10, but at least for Windows 7. With some older webcams it's entirely possible you won't find any drivers let alone ones for Windows 7 or newer. If that's the case, skip the following.

Otherwise, on Logitech's site, upon searching for QuickCam Fusion, you'll notice the default operating system is set to Windows 11. Click and choose the only other option, Windows 7, and you'll be prompted to download the newest Windows drivers. 

Plug the webcam into a free USB port, and Windows will proceed to install either the driver you found and installed, or a compatible driver included with Windows. Assuming all goes well, from the Start menu type "Camera privacy settings" and ensure "Allow apps to access your camera" is set to On:

Further down the screen, ensure all apps (except Zoom, if listed) are set to Off:

Now, ensure "Allow desktop apps to access your camera" is set to On:

If you haven't already, install the latest Zoom desktop client. Before you proceed, go ahead and restart your PC to let Windows complete any post-configuration or housekeeping stuff that may linger. Then, once back at the desktop, create a system restore point to preserve things in case something blows up (unlikely, but always a possibility; my system decided to BSOD at least once during the process, better safe than sorry).

That's it. Upon opening Zoom and going into Settings => Video, you should see your face or whatever your webcam is currently seeing, and in meetings with video enabled things should proceed just fine.

Mouse Back/Forward Buttons Stop Working in Windows 10

Recently, inexplicably, my wireless bluetooth iClever mouse decided that its thumb buttons used for stuff like forward and back in browsers and Windows Explorer and other applications should no longer work.

No idea if a recent Windows 10 update was the culprit or what, but I found a very simple solution via a post on Reddit. Simply unplug the mouse's little USB transceiver and plug it into a different USB port on your PC. 

That's it. That's the post.

I'd already tried removing all bluetooth devices from Device Manager including hidden ones and rebooting, no joy. No clue if should this happen enough times if I might eventually run out of USB ports my mouse deigns to allow control of it. 

Prevent Docker for Windows Auto Update

I recently installed Docker Desktop in order to then install PiHole on my Windows 10 desktop PC. PiHole is a cool and free little utility that you can install as a Docker container to provide ad blocking capability that goes a step further than a browser ad blocker add-on like say UBlock Origin. Once installed you can have your PC serve as a sort of DNS proxy for your entire network which bypasses a wide array of blacklisted IP addresses and domains.

One annoying and frankly impolite "feature" of Docker Desktop in general is that some time ago (possibly after version 2.5 or thereabouts) they removed an option through the GUI to disable automatic updates. This is irritating because what you might expect happened to me; a newer, buggy version once installed caused Docker to behave erratically and crash frequently. 

I took a quick look at the Docker documentation (Dockermentation??) and while there are command line options to disable auto updates in the Docker daemon I haven't got the patience to figure out what syntax to use; I mean come on, I'm so lazy I'm using Windows 10, right?

Instead I tried to find out where Docker downloads its updated versions, and I believe I found that folder as shown below. From the Start menu you can type in C:\Users\<Windows username>\AppData\Local\Docker Desktop Installer:

Docker's systray icon will conspicuously show a little "i" to inform you of a looming upgrade, and at the next restart of Docker Desktop the upgrade ordinarily will be installed. However, in lazily taking a stab at preventing this behavior I decided to alter the file system attributes of the folder containing the updates to make it and its contents read-only.

The idea is to both prevent updates from being downloaded in the first place, and in case Docker normally attempts to write any temp files to that folder as part of the upgrade process to kneecap its ability to do so and maybe indicate to that logic something's up that makes upgrading a bad idea.

I altered the folder attributes and applied them, then exited Docker via the systray icon and after a minute or so opened the shortcut. I checked the version first of all:

I was rewarded not with Docker dictating the 3.2.x version I'd use going forward, but rather the previous 3.1.x version I downgraded to in order to not get stuck with the buggy behavior of the newer but less stable version. Success!

I also noticed the conspicuous "i" was gone, as if the logic quietly decided the attempt to upgrade never even happened, which is fine by me.

Of course this isn't the optimal way to prevent software from doing its thing despite user preference, but in these "challenging" times laziness reigns supreme in my headspace. Possible caveats may be that the next time you manually upgrade to a newer version you might need to reapply this change to your file system (too lazy to post a batch file to do it, sorry!) but that's minor compared to browsing on my tablet across the house from my PC and having Docker crash and take out my PiHole.

Steam Failed to Start Game (App Already Running)

A few Steam client versions prior to the 4/29/2016 build, I began receiving the following error when attempting to start Garry's Mod (aka GMod):

 

Steam reports it is still running even though I had cleanly exited via GMod's interface:

Following the Steam support site link got me nowhere, and googling revealed this bug has occurred in the past more than once (perhaps Valve needs to do better at regression testing?), with no solutions that jumped out. I did discover though that ending the Steam.exe process tree in Task Manager, and then deleting some cached files in Steam's appcache folder, seems to at least work around the problem. 



 

 
Manually this is a bit of a pain, but there is a way to automate this particular workaround which involves creating a batch file to run GMod instead of using the default shortcut Steam creates for it. Here's how. 

1. Right-click on the desktop shortcut for Garry's Mod, then click Properties.
   
2. Click twice to select the text in the URL box, then hit Ctrl-C to copy it to the clipboard.
   
   
3. Open a text editor (I like Notepad++) and hit Ctrl-V to paste the URL into it, and then type the word START and a blank space so that it looks like this:

   START steam://rungameid/4000

   
   
4. Above the URL you just pasted, copy and paste the following text:

   TASKKILL /IM "Steam.exe" /T /F

   
   The batch file should now look something like this:
   
   
   
   
5. Save the file with whatever file name (I used gmod) and the extension .BAT (for batch file) on your Desktop or wherever makes sense. Then, you can either click twice to run it directly, or create a shortcut and use that instead.
   
      

 
When the batch file is run, this will tell Windows to first execute TASKKILL (a built-in Windows utility) and tell it to close Steam.exe (/IM "Steam.exe") along with any child processes in its process "tree" (/T) forcibly (/F). After that, it will then start a new process to open Steam and then GMod. It'll be as if you'd gone through the steps described above manually, only without the manual part.

The above can be adapted for most any other Steam game having this problem; you'd simply open that other game's shortcut in step 2 and go from there to create a new batch file for it.