Posted on September 28th, 2016 at 13:37 8 comments
Don’t be too surprised if it’s problematic. See the release notes.
Known issues for PC
- Optional components may not work after upgrading to this build. To get it working again, go to “Turn Windows features on or off”, scroll down and check the right optional component and click ok. After a reboot, the optional component will be enabled again.
- Tencent apps and games will cause your PC to bugcheck (bluescreen).
- Running sfc /scannow in an elevated command prompt will fail at 20% with the error “could not perform the requested operation.”
Posted on September 28th, 2016 at 10:54 32 comments
This from poster bee:
got a important MSE client update today on win 7
kb3143414 new mse version being 4.10.205
of course, absolutly no information about the kb or the client version anywhere
I don’t see any info either. Anybody out there know anything?
Posted on September 28th, 2016 at 08:14 8 comments
A list of my pet peeves. Any suggestions?
InfoWorld Woody on Windows
Posted on September 26th, 2016 at 15:55 55 comments
Thanks to poster Jonathan Seymour:
MS just released a new out of band non-security patch for Internet Explorer 11, responding to a bug in MS16-104, which breaks installation of Active X controls — specifically, the ActiveX Installer Service.
Details about the problem in KB 3192665.
The instructions are enormously hard to follow. Here’s my guess as to what it was supposed to say:
If you have the original “RTM” Windows 10 build “1507,” you need to manually download and install KB 3193519.
If you have the Fall Update, Win10 version 1511, you need to manually download and install KB 3193517.
There is no indication I can see about your choices if you have the Anniversary Update, version 1607.
It’s also worth noting that both of those KBs are up to revision 3.0. Something’s screwed up.
For those of you running IE 11 on Win7 or 8.1, you need to download KB 3192665 from the Windows Update Catalog. Use this link:
Or download directly:
Of course, if you don’t use AXIS to install ActiveX controls, you have nothing to worry about.
Posted on September 26th, 2016 at 09:24 27 comments
Just announced at Ignite.
On July 15, the number was 350 million.
In between we saw the end of the free upgrade offer. Paul Thurrott will no doubt note that Microsoft’s continuing its years-long claim of increasing use on its latest platform by 20 million per month. Paul’s been saying that since the Windows 7 days, and he’s right.
UPDATE: As expected. Except it’s closer to 17 million/month, according to Paul’s reckoning.
ANOTHER UPDATE: Good graph and analysis from Gregg Keizer at Computerworld.
Posted on September 25th, 2016 at 07:35 29 comments
Message from JO:I have two .NET Framework updates pending on my Windows 7 Service Pack 1 64-bit computer. KB3102433 – “Microsoft .NET Framework 4.6.1 for Windows 7 for x64” published 2/9/2016 is a recommended update. Being offered this update is understandable because the latest version of .NET Framework installed on my computer is 4.5.2, at least that is what is shown under programs on the control panel. KB3179930 – “Reliability Rollup for Microsoft .NET Framework 4.5.2, 4.6, and 4.6.1 on Windows 7 and Server 2008 R2 for x64” published 9/22/2016 is an optional update. The information that Microsoft provides under the “More information” link references a different KB number (3179949) and makes no mention of .NET Framework 4.5.2. In fact, the prerequisite is that .NET Framework 4.6 or 4.6.1 must be installed.I am in no hurry to install any of these. Nevertheless, I am wondering whether KB3179930 is actually an update that is designed for .NET Framework 4.5.2 as advertised in the title of this update.
Anybody know for sure?
Posted on September 23rd, 2016 at 15:59 5 comments
An excellent overview of the Simplo battery case.
Ed Bott’s Windows Insider column for Redmond Magazine.
Now let’s see what happens with the LG battery problem.
Posted on September 23rd, 2016 at 13:08 94 comments
Win7/8.1 customers take note.
InfoWorld Woody on Windows
UPDATE: Fixed the link. Sorry about that.