Woody Leonhard's no-bull news, tips and help for Windows, Office and more… Please disable your ad blocker – our (polite!) ads help keep AskWoody going!
Home icon Home icon Home icon Email icon RSS icon
  • Will Win10 1803 be called (yuck!) Spring Creators Update (/yuck!)?

    Posted on March 8th, 2018 at 07:41 woody Comment on the AskWoody Lounge

    WalkingCat (@h0x0d) asked someone with a copy of the next-next version of Win10 (the Skip Ahead build 17618, presumably leading to version 1809) to run a PowerShell command that lists VMHost supported versions.

    The result isn’t going to make any Windows fans happy.

    The last listed version is “Microsoft Windows 10 Spring Creators Update/Server 1803.”

    Pardon me while I try to keep my breakfast down.

  • Keizer: Windows 10 shows sign of enterprise upgrading

    Posted on March 2nd, 2018 at 20:15 woody Comment on the AskWoody Lounge

    Keizer’s Computerworld take relies on the numbers reported by Net Applications:

    Windows 10 actually slipped two-tenths of a percentage point in user share… during February, ending the month powering 34.1% of the world’s PC…

    Using the 12-month average of Windows 7’s user share decline, Computerworld forecasts that the aging OS will still account for about 35% of all active Windows editions in January 2020

    It’s clear which way the wind is blowing — but I wonder how many will abandon Win7 in 23 months?

  • Keizer: Microsoft’s browsers are dying

    Posted on March 2nd, 2018 at 11:24 woody Comment on the AskWoody Lounge

    Er, dieing. Sorry.

    Gregg Keizer has a good look at the rapid decline of the IE (+ Edge) hegemony.

    Even though IE showed an uptick in usage last month, per Net Applications, the prognosis for Microsoft browsers is dismal:

    By the time Microsoft retires Windows 7, and for effective purposes, IE as well, Windows 10 should have reached a user share (of all Windows) of around 63.6%, assuming its climb continues on the past year’s trend line. If Edge hasn’t, well, edged up as a share of all Windows 10 by that time – and all evidence is that it will not – then Microsoft’s active browser share will be in the single digits, perhaps as low as 6%.

    Hard to imagine IE + Edge at 6%, but then again Windows Phone took a hard, fast fall, too.

  • Keizer: Looks like the next Windows 10, version 1803, will arrive April 3 or 10

    Posted on February 16th, 2018 at 12:06 woody Comment on the AskWoody Lounge

    That matches with what I’ve heard – and have been hearing for quite some time.

    Good overview of Insider and Skip Ahead, Gregg Keizer at Computerworld.

    P.S. There’s still no official name for the version, far as I know. “Windows 10 Spring Creators Update” doesn’t work, because version 1703 was in the North American Spring, and it was a “Creators Update.” I still say “Win10 Spring forward after Fall back Creators Update” would work. What do you think?

  • Thurrott: Stop the relentless release of new Windows versions

    Posted on February 12th, 2018 at 10:23 woody Comment on the AskWoody Lounge

    Another great post in (paywalled) Thurrott.com premium:

    Apple will slow down the addition of new features to iOS in order to focus on quality. This is exactly the strategy that Microsoft needs to adopt. In fact, it’s years overdue.

    Amen, bro.

    One little observation. Paul says that Microsoft will soon be forced into a three-year support cycle and “at that point, we’re pretty much back to where we started.” Which is correct, but there’s a subtlety: When Windows as a Service gets out to three years of support, there will be six (or more!) versions of Win10 being supported.

    We’re already on two years with 1511, 1607, 1703 and 1709.

    Version Released End of service Days
    Home/Pro Ent/ Ed  for Ent
    Win10 1709 17-Oct-17 9-Apr-19 8-Oct-19 721
    Win10 1703 5-Apr-17 9-Oct-18 9-Apr-19 734
    Win10 1607 2-Aug-16 10-Apr-18 9-Oct-18 798
    Win10 1511 10-Nov-15 10-Oct-17 10-Apr-18 882
    Win10 1507 9-Jul-15 9-May-17 670

    Microsoft’s digging itself into a support nightmare even worse than the one we have today.

  • Microsoft sends cease and desist warnings to Store software publishers with “Windows” in their names

    Posted on February 12th, 2018 at 10:00 woody Comment on the AskWoody Lounge

    I saw this over the weekend from Günter Born. He lists two specific apps that received “infringing app” notices, and many others apparently have been hit.

    One in particular stands out: Martin Geuß, who has been selling his Dr. Windows app for as long as Windows has had a store, got a notice. In case you don’t know, Martin Geuß is a Microsoft MVP of long standing, and one of the most helpful people on the internet.

    Even more stupid (that’s one of BillG’s favorite terms): The notice was received on Saturday, with the recipients expected to comply by Sunday.

    There’s one piece of wiggle room. Apparently the notification came from AppDetex, which “is authorized by Microsoft Corporation to facilitate the submission of and correspondence regarding complaints.” The complaint says the Dr. Windows app:

    uses the trademarks of Microsoft Corporation without authorization. In this instance, the app uses “Windows” in the title.

    I’ve long wondered at the way Microsoft has been granted a trademark for a common industry term. but I’m aghast at how it’s strong-arming even its most ardent supporters.

    I got bit by this same bit of stupidity almost three decades ago, when a Microsoft developer warned me that the MS legal folks were casting a malicious eye at the name “Word POWER Pack.” But that’s another story, for a different time.

  • New, improved privacy in Win10 1803 may not be what you think

    Posted on January 31st, 2018 at 05:32 woody Comment on the AskWoody Lounge

    I’ve been reading the wave of mainstream articles that followed Marisa Rogers’s publication last week of an official Microsoft notice about new privacy features in the next version of Windows.

    Being the skeptic that I am, the articles sounded to me like Microsoft Press Releases bouncing around the blogosphere — long on accolades, short on real-world experience. Sadly, we’re seeing a whole lot of “reporting” like that these days.

    So it heartens me to see a hard-boiled look at the new feature, from my old friend Preston Gralla. In his Computerworld opinion piece Don’t believe Microsoft’s latest privacy hype, Gralla hit it right on the nose:

    Microsoft got plenty of kudos for the new tool. For the company, that was mission accomplished. But it was anything but that for users. The Diagnostic Data Viewer is a tool that only a programmer could love — or understand. Mere mortals, and even plenty of programmers, will be baffled by it, and they won’t gain the slightest understanding of what data Microsoft gathers about them.

    His conclusion:

    Microsoft should change this. It should release a simple-to-use tool that shows in granular detail and in plain English exactly what diagnostic information is being sent to Microsoft. People should then be allowed to opt in or out for every type of diagnostic information that is sent. And everyone should be able to do that, not just those who have a specific version of Windows 10.

    With the EU apparently poised to do some real privacy protection — I’m not talking about the glossy installation switches in Win10 1703 and later, which are all hat and no cattle — the topic’s going to get heated in the next few months.

    If you want to know the real, nitty-gritty story on Win10 privacy — which settings do what, and how it all fits together — take a look at Martin Brinkmann’s The Complete Windows 10 Privacy Guide: Windows 10 Fall Creators Update version. I have a link to it over on the right side of this page.

    That’s the meat. Don’t settle for the sizzle.

  • Barb Bowman: Where is the Surface Pro LTE recovery image?

    Posted on January 25th, 2018 at 13:04 woody Comment on the AskWoody Lounge

    If you need a recovery image for your spankin’ new Surface Pro LTE, there’s a leeetle trick.

    Barb Bowman has the details on her Digitalmediaphile page.