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

    https://support.microsoft.com/en-us/help/4464619

    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 24.20.100.6344, 24.20.100.6345) 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 09.21.00.3755) 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.

  • Patch Lady – now we’re talkin’ 1809 transparency

    Posted on November 16th, 2018 at 22:13 Susan Bradley Comment on the AskWoody Lounge

    https://support.microsoft.com/en-us/help/4464619

    Updating the master patch list tonight and look at the new known issues:

    Apple has identified an incompatibility with iCloud for Windows (version 7.7.0.27) where users may experience issues updating synching Shared Albums after updating to Windows 10, version 1809.

    After updating to Window 10 version 1809, F5 VPN clients may lose network connectivity when the VPN service is in a split tunnel configuration.

    And the issue with mapped drives now showcases it will be fixed by the end of November:

    Next Steps: Microsoft is working on a resolution and estimates a solution will be available by end of November 2018.

  • The folks running Win10 1809 seem to know what they’re doing

    Posted on November 16th, 2018 at 10:33 woody Comment on the AskWoody Lounge

    I know it’s a controversial observation, especially around here, but I’m starting to hope that the current regime (whomever they may be) are using the tools they have to roll out Win10 1809 in a much more sane way.

    My most recent cause for hope: The “C week” or “D week” non-security cumulative update for Win10 version 1809, KB 4469342, is going out to the Insider Release Preview ring, for testing before broad deployment.

    That’s exactly what the Release Preview ring was made for. And it’s never been used correctly. Until today.

    Details in Computerworld Woody on Windows.

  • Patch Lady – a bit of transparancy for 1809

    Posted on November 15th, 2018 at 10:51 Susan Bradley Comment on the AskWoody Lounge

    https://support.microsoft.com/en-us/help/4464619/windows-10-update-history

    Holy cow, we have a bit of transparency.  We have a new section in the update history page that lists current blocking items and eta of a resolution.

    Including my lovely one of the mapped drives issue which they indicate they are working on for 2019.

    Click on that link, scroll down for the section called Current status and just have a moment of zen and transparency:

    Current status of Windows, version 1809, Windows Server 2019, and Windows Server, version 1809

    Oh and as a reminder, if you do want to install 1809 early and be a beta tester, watch your antivirus as clearly a/v partners aren’t quite ready.

  • Windows management taking one on the jaw. Or two.

    Posted on November 13th, 2018 at 16:39 woody Comment on the AskWoody Lounge

    You folks are accustomed to my rants. I’ve been kvetching about Windows rollouts and fixes for… just about forever.

    Take a look at these other rants, this time about 1809.

    Paul Thurrott: “You can’t trust anything these people tell you. They literally have no idea what they’re doing… They’re going to say ‘there’s nothing to see here.'”

    Watch Paul and Brad on First Ring Daily.

    Chris Hoffman at HowToGeek:

    We want Microsoft to understand the problem, take it seriously, and make some real changes. But Microsoft seems disconnected from users. Microsoft is saying it already does a lot of work to ensure Windows 10’s quality, as if Windows users would be happier if only we knew about all Microsoft’s hard work.

    No. We’d be happier if Microsoft would stop breaking things.

    Bravo and huzzah.

    Somebody tell me… how much money has Microsoft made from Windows? And we keep getting kicked in the teeth like this?