Since build 1607 of Windows 10, it automatically restarts after updates, regardless of your wishes or unsaved documents. And since I do most of my work on a Virtual Machine that runs 24/7, this is not desired behaviour (putting it mildly).
In previous builds, there were options to postpone restarts until you manually approved. Not anymore...

This article by Martin Brinkmann shows a way to fix this: http://www.ghacks.net/2016/09/20/disable-reboot-after-automatic-windows-updates/
I did not install the "Take Ownership" program; doing that manually is easy enough.

Note: This solution worked fine for a while - however, recently (June 14th 2017) Windows somehow undid the fix (all settings were set back to their old status) and restarted my VM anyway. Bugger. I've implemented the fix again, hopefully Windows will keep its dirty hands off this time...

It happened again, while multiple applications were running (Feb 14th 2018)... So I had another go at it; this time I tried the suggestions mentioned here: https://docs.microsoft.com/en-us/windows/deployment/update/waas-restart. Fingers crossed.

Adobe Photoshop and Lightroom claim a lot of disk space on your C drive for caching purposes. I wanted to move those files to another SSD (E in my case), so they wouldn't be included in the daily C disk image backups. Of course this applies to other applications as well, this is just an example.

For Camera Raw cache files this is easy, just change the location in Photoshop or Lightroom itself.

For the Lightroom Catalog Previews, this is a bit more complicated. There is no setting for that one, so we'll have to use a symbolic link. A great article on those can be found at https://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/.
I moved the Lightroom Catalog Previews.lrdata directory from C:\ to E:\Adobe\ and created a symbolic link like this:

mklink /J "C:\Lightroom Catalog Previews.lrdata" "E:\Adobe\Lightroom Catalog Previews.lrdata"

I have some scaling problems with VMware ESXi 5.5 vSphere Client (and VMware Workstaton Player 15.5) on Windows 10, escpecially since buying a 4K monitor. This problem is not limited to VMware of course, any old piece of software may have similar problems, so the fix here might be of use.

Windows 10 is now 5 years old, and still multi-monitor scaling has issues. Sigh.
I would really like Microsoft to concentrate on fixing bugs instead of adding new features (99% of which I never use anyway).
And this is by no means the only old bug in Windows they refuse to repair - just last week Windows Explorer failed to remove a folder from it's Navigation Pane after removing that folder in its main window. I have been running into that stupid little bug since at least Windows 2000...

I'm not a gamer, but there are a few games I sometimes play for nostalgic reasons - Like Doom, Carmageddon, Blockout, and even Football manager (on a ZX Spectrum emulator, now that really is old school...).
Quake 2 is also one of my favourite retro games, but ever since I got my new desktop PC, the brilliant Quake2XP mod, also known as quakeIIxp or q2xp, has been giving me some problems.

My setup: AMD Ryzen 9 5900X, B550M, 32GB Ram, 1 TB Samsung 980 Pro, Gigabyte Radeon RX 560 OC 4G (rev. 2.0), 3 monitors (the main one is 4K), Windows 10 Pro.
So as you can see, this is quite a serious workstation, but the R560 videocard is not suited for "serious" gaming. When I bought the new PC hardware, I used the graphics card from the previous one. At the moment prices for videocards are outrageous, and this one still works fine and does all I need it to do. Except for running Quake2XP properly, that is...

The issues I had:

• Very slow load times. The first map would take about 85 seconds (!) to load - after that things were a bit quicker.
• Slow framerates - sometimes always immediately, sometimes after a few minutes the framerate would steadily drop to less that 20 fps, which is unplayable.
• Horizontal black "noise" lines would flash on and off, sort of like an old CRT with a bad antenna connector. A rather nice retro look actually, but not ideal.

What complicates matters is that I also run some 3D software on my desktop that really requires AMD Radeon PRO drivers, as opposed to the regular Andrenalin (gaming oriented) drivers. Switching to the regular AMD drivers might have solved the Quake problems, but that is not an option for me.
The latest version (at the time of writing) is 21 Q3 but I had weird issues with that one. Sometimes on starting my PC, all 3 monitors would display only noise - needless to say, that was a bit of a shock the first time that happened...
An older version, 21 Q1 works just fine, so I'm sticking with that. Also, all the glitches in Quake 2 XP were exactly the same in both versions, so I didn't bother with the Q2 version.

So after a Sunday morning spent playing around with Video settings in Quake 2 XP, this is what I came up with:
These settings fix the issues I had with Quake2XP, plus Windows 10 and all other applications work just fine as well.
It is still not ideal however - every once in a while the framerate still drops to an unplayable level. It doesn't happen nearly as often, so I can live with that. Some bug-free graphics drivers would be nice though...
The maximum (16:9) resolution I can now use, while maintaining a minimum of 60 fps 99% of the time, is 1600 x 900. Switching to 1920 x 1080 is quite useable, but it drops the framerate to under 50 fps sometimes.

On my Windows 11 PC with two monitors, video playback (of any kind - VLC, browser, Media Player, etc) on the second monitor always stuttered.
It's an AMD Ryzen 5900X with 32 GB of RAM and an Nvidia RX4060, so driving two 2560x1440 monitors should be a piece of cake...

Turns out I needed to change two settings to get this fixed:

• Disable the "Hardware-accelerated GPU scheduling" Windows feature, under Settings -> System -> Display -> Graphics.
  Info: https://forum.level1techs.com/t/solved-vlc-stutters-on-second-monitor/221444.
• AND set the refresh rate of both monitors the same. I had the primary monitor set to 120 Hz and the secondary to 60 Hz - setting both to 60 Hz solved this.

While setting up a new Windows 11 laptop, I ran into an issue with my Synology NAS - I couldn't access the network share anymore.
The share worked fine on about 6 other PC's, so clearly the new Windows installation was to blame.

So it turns out this was caused by the account that was used.
Usually I create a local account (even though Windows 11 really tries to prevent you from doing that), but this time I used a Microsoft (i.e. emailaddress) account.
Which causes the network share to become unusable, because the Windows Credentials that are needed are missing - and Windows doesn't give you any clues or warnings about it.

So thank you very much Microsoft, for causing this, for not giving me an error message that is even slightly useful, for not prompting me for a username/password for the share, and for not documenting it anywhere (at least not where I could find it).

Anyway, this is the fix:
Info: https://kb.synology.com/en-sg/DSM/tutorial/Why_cant_access_shared_folder

• >On that site, go to “On your client computer” and expand “For Windows PC”
• On your PC go to Control Panel > User Accounts > Manager Your Credentials > Windows Credentials
• Add the network share with its IP address, username and password
• Add the network share with its network name, username and password