I’m no longer in the Windows 10 Insider Preview program, but I still see Microsoft’s preview build announcements. The latest is for build 14926.
The announcement for build 14926 reveals yet another reminder that we are just pawns in Microsoft’s overall strategy. Anyone participating in the Preview program must allow Microsoft to update their Windows 10 computer, and if they don’t cooperate, the computer will stop working. Specifically, it will start rebooting itself every three hours, and if that doesn’t force your cooperation, eventually the computer will stop booting altogether.
My reaction to this news (click for animated version).
Update 2016Sep22: The announcement for Windows 10 Insider Preview Build 14931 confirms that this is Microsoft’s new policy. No explanation is provided, although if pressed, I’m sure Microsoft would bloviate about ‘user experience’, ‘reliability’ and other things that sound good but deflect attention away from what’s actually going on, which is that Microsoft really wants to control what happens on your computer.
Another new version of Chrome was released yesterday. Very little has changed in version 53.0.2785.116. The full change log lists six changes related to actual functionality, and they all seem to be related to appearance and stability. There are no security fixes in this release.
Microsoft’s caution makes sense when you consider what they are doing with Windows testing. It appears that Microsoft is doing a lot less testing in-house, and pinning its hopes on user feedback. The anniversary update is being rolled out first to computers that – based on their hardware and configuration – are least likely to experience problems. This only confirms Microsoft’s disdain for power users, because they are much more likely to encounter problems.
If Microsoft hates power users so much, why don’t they just come out and say it. Then we can all just move to Linux and forget about Windows, except as an object of ridicule.
The announcement for Chrome 53.0.2785.113 highlights five security issues that are addressed in the new version. It points to this page for details, but currently nothing is listed there. According to Google, “Access to bug details and links may be kept restricted until a majority of users are updated with a fix.”
The full change log lists several dozen changes, most of which are minor bug fixes.
For most users, Chrome will update itself. To make sure you’re running the most recent version, click the menu button (at the top right; looks like three vertical dots), and select Help > About. If Chrome hasn’t already updated itself, this should trigger the update.
Microsoft’s contribution to our monthly headache is fourteen updates for their flagship software (Windows, Office, Edge, and Internet Explorer). Seven of the updates are classified as Critical. Over sixty separate vulnerabilities are addressed by these updates. One of the updates is for the version of Adobe Flash embedded in Internet Explorer 10 and 11, and Edge.
Not wanting to be left out, Adobe once again brings its own pile of patches to the table. Flash 23.0.0.162 includes fixes for at least twenty-six vulnerabilities. Google Chrome will update itself with the new Flash, and Internet Explorer 10 and 11, and Edge, get the new Flash via the update mentioned above. For all other browsers, simply visit the main Flash page to check your Flash version and update it as needed.
A new release of Vivaldi features enhancements to theme support, including theme scheduling. Panels can now be different widths, and middle-clicking the garbage icon now restores the most recently closed tab.
Wait. Theme scheduling? Does anyone really need this? Frankly, I wish the Vivaldi developers would focus on the core issues, like tabs, bookmarks, and link handling, which are still a mess, in my opinion. Why is Vivaldi the only browser that doesn’t highlight the contents of the address bar on right-click?
The latest version of Google’s Chrome web browser includes a few minor tweaks, but doesn’t fix any serious bugs or security vulnerabilities, according to the announcement and full change log. So there’s no rush to update.
Two serious security vulnerabilities in WordPress 4.6 are fixed in the latest version, 4.6.1. Several other minor issues are also addressed. See the release notes for additional details.
WordPress sites that are configured to install minor updates automatically should be auto-upgraded to version 4.6.1 in the next few days, but anyone who manages a WordPress site should immediately verify this, and install the update manually if it’s not already running 4.6.1.
Minor bug fixes and stability improvements feature in the latest version of Opera, 39.0.2256.71. The full change log doesn’t list any security fixes, so this is not an urgent update unless you’re experiencing stability issues. For most users, Opera will update itself automatically.
The full change log for Chrome 53.0.2785.89 is another one of those browser-annihilating pages that you probably shouldn’t even try to load. Included in the boat-load of changes in Chrome 53 are thirty-three fixes for security vulnerabilities, making this an important update.
For most users, Chrome will automatically update itself, but given the number of security fixes, you should probably make sure. Click the funny little menu icon (three dots in a vertical line), then select Help > About from the menu. If Chrome isn’t already up to date, this should trigger an update.
There may be some interesting new features in Chrome 53, but the announcement doesn’t mention anything in particular. If anyone out there is patient enough to read the full change log and notices anything noteworthy, drop me a line to let me know, and I’ll update this post.
Rants and musings on topics of interest. Sometimes about Windows, Linux, security and cool software.
Close
Ad-blocker not detected
Consider installing a browser extension that blocks ads and other malicious scripts in your browser to protect your privacy and security. Learn more.
boot13