Newsletter Archives

• Will Win10 1809 ever be declared “suitable for business”?

  Posted on March 14, 2019 at 14:35 CDT by woody • Comment in the Forums

  It’s been a raging question for months. Win10 version 1809, released in October, has not been declared “Semi-Annual Channel” (the previous “Current Branch for Business”) worthy as yet, although it’s been out for … count ’em … five months.

  A month ago, Microsoft dismantled its whole update framework and threw away the names that we’ve known for so long — names, such as “Semi-Annual Channel (Targeted),” that are baked into the fabric of Windows Update in versions 1803 and 1809.

  @1EarEngineer just pointed me to a post from ‘Softie John Wilcox which, in response to a question about the updating mess, says:

  1809 has been released, there is no second, separate broad release.   For self managed customers, they control and decided when they have reached their deploy decision, and our guidance is they should have started the deployment process now with 1809, following our recommend framework.  This would be in the target phase, which we are in as well for WU.

  For devices we manage, that are connected to WU, we are in targeted phase, which means we are only publishing the update to targeted devices, not all devices.  This is our normal process, and as we get more data and confidence, we add more devise to the target list, until we reach our decision that its good for all, at which time we publish to everyone. That is when it becomes “broad”. That just signals that it is now broadly available ( same release ).

  Its not a time driven thing, but a data driven thing. 1803, it took 2 months, the historical norm was 3-4 months.  1809 will not be 2 months , but more to the norm.

  1809 is already on VLSC, we are now posting at the same time we start on WU, and will continue that going forward

  Which, to my mind anyway, reaches a new low in obfuscation. First of all, Win10 version 1809 is five months old. Second, if MS doesn’t declare it “Semi-Annual Channel” one of these days, all of those Windows Update advanced settings in Win10 version 1803 and 1809 are just so much mealy-mouth mush.

  Am I missing something here?

  Windows Patches/Security Current Branch for Business, Semi-Annual Channel, Win10 1809

• Win10 1809 second February cumulative update, KB 4482887, blamed for “crazy” performance drops in some games

  Posted on March 6, 2019 at 06:21 CST by woody • Comment in the Forums

  Microsoft hasn’t acknowledged the bug yet, but it looks like the second February cumulative update (the “optional, non-security update”) for Win10 version 1809, released on March 1, is clobbering some games.

  Tom Warren at The Verge tweets:

  Anyone having major gaming performance issues in Apex Legends, CoD, or Destiny 2 after installing KB4482887 Windows 10 update?

  — Tom Warren (@tomwarren) March 5, 2019

  In the discussion attached to that tweet, @adamlunn points to two Reddit threads:

  One from jlobue101 says that the “severe performance issues” are with Destiny 2. “The issue is not exclusive to NVIDIA GPUs, as there are now reports of systems with AMD GPUs also being affected.”

  One has a comment from rayw_reddit that says “This patch is causing massive lag spikes in older games, like CoD4 and CoD MW2. Right after installing this update, I launch any of the two aforementioned games, moving the mouse around (yes, mouse movement) causes the game to freeze in 1 second intervals every time. If you don’t move the mouse, game appears fine. Does not affect the modern titles I’ve tested: Battlefield V”

  Is the problem confined to games? Highly unlikely, in my experience. It’s just that gamers notice bugs sooner than most of us.

  Moral of the story: Don’t go clicking Check for updates! That’s the only way you’re gonna get this “optional non-security” cumulative update.

  Man, and I had hoped that the extended 1809 testing rounds would catch this kind of junk.

  UPDATE: Microsoft finally acknowledged the problem on Wednesday:

  After installing KB4482887, users may notice graphics and mouse performance degradation with desktop gaming when playing certain games (eg: Destiny 2).

  Microsoft is working on a resolution and will provide an update in an upcoming release.

  As a short-term resolution, users can uninstall KB4482887 to regain performance.

  Windows Patches/Security KB 4482887, Performance, Win10 1809

• Q: Is it time to install Win10 version 1809?

  Posted on March 4, 2019 at 13:08 CST by woody • Comment in the Forums

  Just got a great question from SC:

  I need clarification. About mid-January 2019, amid all the 1809 version hullaballoo, I followed AskWoody guidance and set my system to “metered connection” in order to not get the automatic updates.

  I understood the guidance said we would be notified when it would be safe/appropriate to turn the “metered connection” off. I have been awaiting that guidance. Its possible I have missed it or did not recognize it when I saw it.

  To say I am just a little savvy to Windows & IT is a serious overstatement, thus I depend on your help more than might make you comfortable!

  The articles on 1809 updates in this newsletter seem somewhat mixed to me as to whether I should now have version 1809 installed .

  So, I ask, should I now turn off the metered connection or wait? And if/when I turn metering off will all updates/versions needed be automatically installed or do need to take other action, such as implied in this newsletter?

  I have Windows 10, Home Edition, Version 1803 (OS Build 17134.590)

  Many thanks for all you do!

  You’ll see that there are many voices on the forum, and in the newsletter, with different advice. Right now, I still say it’s best to wait until Microsoft gives the go-ahead on Win10 version 1809. But — as Susan notes in this week’s AskWoody Plus Newsletter — we aren’t quite sure how Microsoft is going to announce when 1809 is “ready for business.” The terminology has changed once again (is that the sixth time in the past three years?) and it’s still up in the air. In that same Newsletter, Fred Langa gives directions for upgrading to 1809, specifically so you can use the new feature that shows power usage for each app. As Fred notes, Microsoft screwed up the 1803-to-1809 migration so badly that patching may never be the same.

  We can only hope.

  There are lots of people on the forums who have upgraded to 1809 with no ill effect. It’s certainly in much better shape than it was just a couple of months ago.

  For now, I say sit tight, unless you have a compelling reason to pick up one of the new features (such as the power usage list). I’m gonna wait until Microsoft gives 1809 a clean bill of health (CBOH channel?), and then wait a little while longer, before giving the go-ahead.

  As we get larger, you’re going to see that more and more. Different people — different savvy people — will have varying opinions. If you want to keep up on individual patches, watch Susan’s Patch Watch List and @PKCano’s updating details. But if you’re working on your own machine, and don’t want to turn into a patching guru (trademark pending), keep an eye on the MS-DEFCON number. It’s simple. Maybe even simplistic. But it’s a good way to know which way the wind blows.

  Windows Patches/Security Win10 1809

• Patch Watch: Recent updates to the Master Patch List; Win10 1809 still not ready; MS Security Intelligence Report

  Posted on March 4, 2019 at 04:13 CST by woody • Comment in the Forums

  It’s a busy week for Patch Lady Susan Bradley:

  • Win10 version 1809 still isn’t “ready for business” — but it’s hard to define the term
  • Cleanup changes with the Win10 1809 update installer
  • Microsoft’s just-released Security Intelligence Report
  • And a full update to Susan’s legendary Master Patch List

  If you’re in charge of patching a bunch of computers, this is your go-to central source of information.

  (For everyday PC users, wait for the MS-DEFCON level to change.)

  Out this morning to all AskWoody Plus members, in AskWoody Plus Newsletter 16.7.0.

  Windows Patches/Security AskWoody Plus Newsletter, Master Patch List, Patch Lady Posts, Security Intelligence Report, Win10 1809

• Keizer: Win10 version 1809 rollout fiasco may hinder Enterprise migrations from Win7

  Posted on January 25, 2019 at 10:14 CST by woody • Comment in the Forums

  In the once burned, twice shy department (or should I say 100th time burned, 101 times shy?) Gregg Keizer has an interesting analysis of the Win10 1809 rollout debacle — and why it may convince Microsoft’s big customers to stick with Win7.

  In a nutshell:

  This year’s [version] 1903 [a.k.a. 19H1] would be a mistake because even for Windows 10 Enterprise customers, it will get only 18 months of support. That means holding out for 1909, which will receive 30 months of support. Trouble is, the company won’t have much of an upgrade cushion from 1803 to 1909; the upgrade will have to begin as soon as the latter is declared enterprise-ready and even then, the cushion will be a short four months.

  Gregg has a very convincing argument — Microsoft’s dropping the ball on 1809 puts Enterprises in a tough place. It’s all in the calendar, and the fact that 19H1 will only receive 18 months of support whereas 19H2 will (MS has promised) receive 30 months.

  I wonder if/when Microsoft will jump off this insane 6-month upgrade cycle.

  Windows News Win10 1809

• A new KB 4023814 — More evidence that the forced push to 1809 is upon us

  Posted on December 26, 2018 at 20:08 CST by woody • Comment in the Forums

  On Dec. 24, while you were all snug in your bed with visions of sugarplums delivering forced upgrades in your head….

  Microsoft updated a KB article, KB 4023814, which should add to your general forced-upgrade paranoia. The KB article describes a scenario where Windows Update shows this dialog box

  

  and presumably politely waits for a reply, before installing Win10 1809. That isn’t what the sample dialog box says, but it is what the KB article says.

  If you’re currently running Windows 10 version 1507, version 1511, version 1607, version 1703 or version 1709, your computer detects the Windows 10 Update Assistant automatically. Then, you can expect to receive a notification that states that your device must have the latest security updates installed and then initiates an attempt to update your device.

  Of course, the update would be to version 1809.

  How does it work, exactly? Microsoft hasn’t told us, although the KB article includes a detailed multi-step procedure for avoiding the prompt.

  @abbodi86 played Grinch with his observation:

  This process would bypass Windows Update settings and install 1809 without having to “Check for updates.” Not sure if it will always show a prompt or not.

  Microsoft’s timing couldn’t be better. Forced 1809 upgrades over Christmas — possibly with no warning.

  Unless you want to be pushed to 1809 on Microsoft’s schedule, block it. Block it good.

  Windows Patches/Security forced upgrades, KB 4023814, Win10 1809

• It’s official: Microsoft is pushing Win10 1809 on non-seeker machines

  Posted on December 22, 2018 at 06:55 CST by woody • Comment in the Forums

  

  In the no good deed goes unpunished department…

  I’ve now seen several reports that Microsoft has started pushing Win10 1809 on normal Win10 PCs, even without the “Check for updates” requirement. The forced update march is here.

  I repeat: If you don’t want 1809 just yet, block it. Or you can sit and wait for Win10 to reboot.

  If it does.

  Windows Patches/Security Win10 1809

• It’s official: Microsoft now says it’s installing Win10 version 1809 when you “Check for Updates”

  Posted on December 18, 2018 at 06:37 CST by woody • Comment in the Forums

  

  Make sure you’ve set Windows to block version 1809, and don’t click “Check for Updates.” Yeah, I’ve been telling you that for four months, but now it looks like the flood gates have opened.

  Tell your friends. It may be their best holiday present.

  Details in Computerworld Woody on Windows.

  Windows Patches/Security Grinch, Win10 1809
• « Older Entries

  Newer Entries »