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: 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?

  • 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.

  • Report: Windows 10 Fall Creators Update has hit RTM

    Posted on October 3rd, 2017 at 07:36 woody Comment on the AskWoody Lounge

    Yeah, it’s full of bugs. But according to a report from Zac Bowden at Windows Central (who has an uncanny reputation for getting this stuff right), the build of Win10 version 1709 that Microsoft released yesterday – 16299.15 – is “the” build that manufacturers will put on new PCs.

    In traditional parlance, it hit RTM.

    The version that’ll be released on October 17 – the official release date – will be quite different from 16299.15. As we’ve seen in the past, MS will issue one or two or three more cumulative updates for 16299.15 before the official release date. Thus, the version folks outside the beta program will see will be 16299.something, where something > 15.

    In the next few weeks, those of you beta testing (in the Windows Insider program) will given instructions for either jumping out of the beta cycle with version 1709, or continuing to the “Skip Ahead” (gawd, what a lousy name) beta builds of Redstone 4, version 1803.

    At least, it’ll be known as 1803, assuming Microsoft continues both its release pace and its naming scheme.