Category Archives: Windows

Windows 10 Insider Preview Build 11082

It could be argued that it’s unfair to talk about problems with Windows 10 preview builds, since they are provided to us for testing purposes and expected to have issues. I hold the opposite view: everyone is better off if we report problems as publicly as possible. But I’ll try to stick to the facts and avoid complaining.

With the arrival of Windows 10 Insider Preview Build 11082, my test PC started doing some very weird things. The extent to which these problems are specific to my hardware remains unclear.

  • On logging in for the first time after the new build was installed, Windows reported that the application CCleaner was not compatible with the new Windows build, and had been removed. CCleaner (formerly CrapCleaner) is primarily a tool for removing junk and temporary files from Windows systems. The message pointed to this page, which says “If you try to use this app with Windows Insider Preview , it might not work correctly or might not work at all.” Not too helpful. I reported the problem to the CCleaner developers.
  • Normally, when File Explorer copies, moves, or deletes files, it displays a progress dialog. Those dialogs no longer appear. File operations still work, but there’s no visual indication of what’s going on.
  • Audio stopped working completely. A reboot didn’t help. Powering off the computer completely and then back on did fix the problem. There was nothing in the Windows events logs to point to a possible cause.

None of these issues are show-stoppers for me. I used the Windows 10 Feedback app to report the File Explorer dialog problem.

This is the first Windows 10 preview build with which I’ve had any serious problems, aside from privacy concerns. It will be interesting to see how quickly Microsoft responds.

Update 2015Dec21: The CCleaner developer responded to my report, saying that they have received similar reports and that they are looking into it.

Patch Tuesday for December 2015

Another month, another pile o’ patches from Microsoft and Adobe. This month Microsoft is pushing out twelve updates, affecting 71 vulnerabilities in Windows, Internet Explorer, Edge, Office, .NET and Silverlight. Eight of the updates are flagged as Critical.

Microsoft has also published a few security advisories since the last monthly update.

Adobe’s chimed in this month with a new Flash (aside: how weird would it be if they didn’t?) The new version addresses at least 78 security vulnerabilities in the veritable piece of swiss cheese we know as the Flash player. The new version is designated 20.0.0.228 on most platforms, but the version designed for use in Firefox and Safari on Windows and Mac is 20.0.0.235.

Windows 10 miscellany

Ed Bott noticed that the latest release of Windows 10 (1511) was mysteriously removed from availability via the Media Creation Tool. The new version can still be obtained through Windows Update. Microsoft’s explanation isn’t very helpful, and it’s rather annoying to system builders who missed the brief window during which release 1511 was available via MCT. Update #1: Ars Technica reports on the situation, noting that there are reports of serious problems with release 1511 when installed via the MCT. Update #2: Ars Technica confirms that upgrading via MCT was causing privacy settings to be reset to defaults. The problem has been fixed, and build 1511 is once again available via MCT.

Meanwhile, Microsoft apparently updated its privacy policy in response to concerns about information gathered and transmitted by Windows 10. Changes to the policy make it clear that Microsoft will only provide law enforcement access to your data on their servers, not data stored locally on your computer. Encryption keys are backed up to Microsoft servers, but Microsoft will not use them to decrypt disks or files on your computer. The collection of telemetry data cannot be disabled, but it can be limited so that only very basic data is collected, and none of it personal.

And finally, Microsoft has relented somewhat on its Windows 10 activation policy, allowing for legitimate installs using old, unused activation keys from Windows 7 or 8.

Microsoft to start pushing Windows 10 on business customers

Microsoft is turning its sights on businesses and other large customers, making changes to Windows 10 that it hopes will entice IT departments to try the new O/S.

With the arrival of build 10586, Windows Update for Business is now ready for use in Windows 10. This is bound to be helpful for business users, since it allows updates to be delayed, but there’s still no way to avoid updates indefinitely. Microsoft is still promising to provide better information about updates, but as yet that hasn’t actually happened.

There’s also now a business-oriented version of the Windows Store. Most importantly, there are options for disabling telemetry and other data sent to Microsoft from Windows 10 computers. Hopefully that change will find its way to regular Windows 10 versions as well.

It’s far too early to decide whether these changes will have any influence over business and corporate decision makers. I certainly wouldn’t recommend Windows 10 for use in business or educational environments; there are simply too many unresolved issues related to privacy, updates, and the user interface.

Ars Technica has additional details.

Google to discontinue support for Chrome on Windows XP

Google recently announced that they will no longer support Chrome running on Windows XP after April, 2016. Chrome will still run on Windows XP, but Google won’t address any new security issues in Chrome that don’t affect newer versions of Windows.

Standard advice to anyone still running Windows XP has included avoiding Internet Explorer in favour of a browser that’s still being updated, like Chrome. After next April, Chrome will be potentially as risky to use on XP as Internet Explorer.

Update MS15-115 re-released to fix crashing issues

One of the updates released by Microsoft on Tuesday apparently caused serious crashing problems on Windows 7 and Windows Server 2008 computers. Microsoft has re-issued the update to resolve these problems. Anyone who already installed MS15-115 on affected Windows systems should run Windows Update again to get the new version.

The MS15-115 bulletin has been updated to show the change.

From the associated knowledge base article:

This security update was rereleased on November 11, 2015, for Windows 7 and Windows Server 2008 R2 to resolve the following issues:

* Resolves crashing that occurred in all supported versions of Microsoft Outlook when users were reading certain email messages.
* Resolves problems that occurred while users were logging on to the system. For example, after a user restarted the computer and then pressed Ctrl+Alt+Delete at the logon screen, the screen flashed and then went black. The user was then unable to continue. There may be other, similar logon issues that are related to this issue.

Patch Tuesday for November 2015

It’s that time again. This month’s crop of updates from Microsoft addresses security problems in the usual suspects, namely Windows, Office, .NET and Internet Explorer. Adobe joins the fun with yet another batch of fixes for Flash, and Google releases another version of Chrome with the latest Flash.

The Microsoft security summary bulletin for November 2015 gets into all the technical details. There are twelve separate bulletins with associated updates. Four of the updates are flagged as Critical. One of the updates affects the Windows 10 web browser Edge. A total of 53 vulnerabilities are addressed.

Flash 19.0.0.245 includes fixes for at least seventeen vulnerabilities. As usual, Internet Explorer in recent versions of Windows will be updated via Windows Update. Chrome gets the new Flash via its internal updater. Anyone still using a web browser with Flash enabled should install the new Flash as soon as possible.

Chrome 46.0.2490.86 includes the latest Flash (see above) and fixes a security issue in its embedded PDF viewer.

Only Windows 10 on new PCs after October 2016

Microsoft has confirmed that OEMs will no longer be allowed to sell new computers with Windows 7 or 8.x after October 31, 2016. If you buy a new PC after that date, you won’t have any options besides Windows 10.

Support for Windows 7 – including security updates – will continue to 2020, so it’s still a perfectly viable operating system. But it’s unclear whether you will still be able to purchase Windows 7 OEM separately, from Microsoft or any other seller, after October 31, 2016. I certainly hope so, although it seems unlikely. So if you’re planning to build any new Windows 7 computers between October 2016 and 2020, you should stock up on Windows 7 OEM licenses now.

Windows 10 build 10586

Microsoft is happy with the latest Windows 10 Insider Preview build, designated 10586. That means it will find its way to your Windows 10 computer over the next week or so as the Windows 10 Fall Update. This will roughly coincide with next week’s Patch Tuesday.

My Insider Preview test machine is configured to get the latest updates, so I’ve been using 10586, and the builds that were available in the interim since the last public release (10240) for a while. Now that the test computer is running the new release version, the ‘Insider Preview build’ message is once again gone from the desktop. That will change when Microsoft pushes out the next preview version.

There’s not a lot to talk about here. Most of the changes are fairly minor, including coloured title bars, tab previews in Edge, general cleanup in user interface elements, and improvements to the Start menu. Skype will get several enhancements. Several bugs have also been fixed.

Update 2015Nov15: Ars Technica has a list of changes in the new release, and really, there’s not much of interest.

With this release, Microsoft has also changed the way it identifies Windows 10 versions. The previous release was “Version 10.0 (Build 10240).” The new release is “Version 1511 (OS Build 10586.3)” where “1511” refers to the 11th month of 2015. They like to keep us confused, don’t they?

Windows 10 privacy concerns are legitimate

Microsoft Corporate Vice President Joe Belfiore has finally admitted what we’ve known all along: Windows 10 talks to Microsoft servers even if you’ve disabled every available privacy-related setting.

Of course, Belfiore says that this is nothing to worry about, since it’s being done to make Windows 10 work better for everyone. He’s probably not lying about Microsoft’s intentions, but all the same, I don’t want my O/S to do this kind of thing. And I don’t care if blocking this unwanted communication makes Microsoft’s work more difficult.

Unless Microsoft relents and provides a method for disabling all of this anti-privacy communication, your choices are: a) give up and stop worrying about it; b) avoid Windows 10 completely; or c) use one of the available third-party methods, such as Spybot Anti-Beacon, to block all of this ‘phone home’ behaviour.

Normally, I’d go for option C. But I’m running Windows 10 as part of the Insider Preview program, and blocking all communication to Microsoft would almost certainly result in my being kicked from the program. So it’s option A for me.