At Encodo, we’re much more cautious about installing massive Windows updates. Since a couple of us (including me) have started experiencing memory leaks in the previous version, we installed it on select machines.
The memory leak we were experiencing was only on a couple of machines. It manifested as Task Manager reporting a very high RAM-usage percentage and, occasionally, Windows popping up a message box asking to close applications. Also, Win + S no longer responded on the first try (i.e. the Windows shell became only partially responsive).
Investigating with the RAMMap tool from Microsoft revealed a large amount (8GB) of “Process Private” RAM that couldn’t all be accounted for in Task Manager or the Resource Monitor.
Initial results are better and seem to indicate normal behavior: if an application that uses a lot of RAM (e.g. Visual Studio) is closed, the reported RAM usage drops correspondingly.
NB; this is not at all a scientific conclusion. We applied the update and memory management on a previously misbehaving machine is better. That’s all.
The Task Manager has two immediately obvious improvements:
One drawback, though, is that you can no longer see which solution is open in which instance of Visual Studio.
Microsoft, as usual, has re-enabled settings that you may have turned off. They did this with the mind-boggling feature called “Aero Shake”: when you grab a Window title and shake it with the mouse, all other Windows are minimized. At first, just the feature was bizarre; now, it’s Microsoft’s fixation with re-enabling this feature that is truly worrying.
We’ve disabled it in the group policies on our domain controller so our users never have to suffer again.
We have not found any drawbacks to this update with our software and development tools and will roll it out to the rest of our users immediately.