News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • Keizer: Win10 version 1809 rollout fiasco may hinder Enterprise migrations from Win7

    Posted on January 25th, 2019 at 10:14 woody Comment on the AskWoody Lounge

    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.

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

    Posted on December 26th, 2018 at 20:08 woody Comment on the AskWoody Lounge

    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.

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

    Posted on December 22nd, 2018 at 06:55 woody Comment on the AskWoody Lounge

    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.

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

    Posted on December 18th, 2018 at 06:37 woody Comment on the AskWoody Lounge

    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.

  • Heads up! Microsoft finally releases a new build of Win10 version 1809

    Posted on December 5th, 2018 at 19:17 woody Comment on the AskWoody Lounge

    KB 4469342 (its fifth iteration, I believe) just went out the Windows Update chute. It brings Win10 version 1809 up to build 17763.168.

    The main 1809 page lists several fixes, including one for the mapped drive reconnection bug. It also lists active blocks for Win10 1809 machines running Morphisec SDK, some Intel display drivers, F5 VPN, an older Trend Micro OfficeScan version, and AMD Radeon HD2000 and HD4000 GPUs.

    You should assume that you’ll get bumped up to 1809 sooner or later, unless you actively block it. Presumably the rollout push will go with all due deliberation.

    Computerworld Woody on Windows.

  • New Win10 1809 Release Preview beta build 17763.168, and another acknowledged bug

    Posted on December 4th, 2018 at 06:37 woody Comment on the AskWoody Lounge

    Credit: Helar Lukats

    That’s the fourth version of KB 4469342, only available to those in the Windows Insider Release Preview Ring.

    Much to its credit, Microsoft’s waiting until this Win10 1809 is ready.

    Computerworld Woody on Windows.

  • Patch Lady – another 1809 block in place

    Posted on November 21st, 2018 at 18:36 Susan Bradley Comment on the AskWoody Lounge

    Every feature release I have to poke and prod to get my Lenovo laptop that hooks into a display port that hooks into my TV to behave.

    It appears that 1809 would once again nail that sucker.  I need to check tonight and will report back.

    I would not be a happy camper.

    For now it’s blocked:

    November 21, 2018 2:00 PM PT Upgrade block in place
    • Windows 10, version 1809
    • Windows Server 2019
    • Windows Server, version 1809


    Microsoft has identified issues with certain, new Intel display drivers. Intel inadvertently released versions of its display driver (versions, to OEMs that accidentally turned on unsupported features in Windows.

    After updating to Windows 10, version 1809, audio playback from a monitor or television connected to a PC via HDMI, USB-C, or a DisplayPort may not function correctly on devices with these drivers.

    Workaround: To see if your device is affected and, if so, resolve the issue, see this Windows Forum post.

    Next Steps: Microsoft is working with Intel to expire these display drivers, including coordinating with OEMs, and will provide an update on the resolution in an upcoming release.

    Note:  This Intel display driver issue is different from the Intel Smart Sound Technology driver (version audio issue previously documented.

    Edit from Susan:

    I checked my video driver here at home and I do not have that video driver:

    Remember you can check it with the instructions here.

  • Forcing the issue with Win10 v1809

    Posted on November 18th, 2018 at 17:03 PKCano Comment on the AskWoody Lounge

    Always a Guinea Pig – Forcing the issue with Win10 v1809.

    I am running Win10 Pro in VMs, so this was a test situation, not my daily driver. The host system is MacMini, MacOS Mojave using Parallels Desktop 14, Ivy Bridge i7 with HD Graphics 4000 and running TrendMicro – the last two are counts against me from the beginning because 1809 has problems with both the graphics and the AV. But this system is also running an up-to-date Insider Preview, so I thought I’d give it a try.

    I was running v1709. In the Settings, I set SAC (Targeted), delay Feature = 0, delay Quality = 0, no pause. Try what I may, I could not get WU to offer anything but v1803, so I let it upgrade to v1803 in hopes I’d see v1809 on the other side.

    No joy. I finally downloaded the v1809 ISO and burned it to a double layer DVD (the x64 is HUGE). I could have copied the ISO to the VM and mounted it there, but I did not want the extra 5GB in the VM. I accessed the DVD from within the VM and ran setup. After accepting the EULA, I chose to keep my data and programs (an in-place upgrade) and let it install.

    The ISO installed Win10 v1809 Build 17763.107 with no problems. i immediately ran Windows Update and was offered KB4467708 which brought the Build to 17763.134 – according to WU up-to-date. Thanks to Parallels Tools driver emulation, the HD 4000 was not a problem. And the VM is running BitDefender Free, so no conflict there either.

    Although I have not had time to look at it in depth, here are some of the superficial observations:
    + I did not lose any data – because in the test machine there was no data to lose and I had not relocated the User folders to another location other than C:
    + Under Default Programs, all my third-party defaults came through (at least they are on the list) – Thunderbird, Firefox, VLC, Windows Picture Viewer, etc.
    * System Restore was turned off (again)
    * Under Network, sharing had been turned back on – I had it turned off in the VM for testing. I have not checked to see if the VM is visible on the network.
    + I went back through all the Settings App. Anything new is turned on by default, and some of the ole settings were also changed.
    * Task Scheduler – I had to disable the tasks under Application Experience and CEIP (again) as they were turned back on. Some of the other Tasks that I have been disabling I no longer have permission to change the setting.
    * I have blocked Cortana/Bing in Group Policy, along with other things like web search. I have not had time yet to go back over those settings.
    + I did not get Apps like Candy Crush. I did open a few of the UWP Apps just to see if they worked. Geezz, they’re ugly! Dumbed down, flat, ugly! No wonder I use Classic Start and third-party programs.