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

Daily Archives: March 14, 2019

  • Proof of concept code published for one of this month’s Win7 zero-days

    Posted on March 14th, 2019 at 15:10 woody Comment on the AskWoody Lounge

    Catalin Cimpanu reports on ZDNet that the Chinese giant Qihoo 360 Core has published proof of concept code for the Win7 zero day identified as CVE-2019-0808. That’s the zero-day that prompted Google to patch Chrome last week, with a dire warning that you needed to get Chrome caught up on patches.

    That isn’t good news for Win7 users.

    I’ll be watching closely to see if the new proof of concept code makes its way into a credible threat for you Win7 customers.

    Stay tuned.

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

    Posted on March 14th, 2019 at 14:35 woody Comment on the AskWoody Lounge

    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?

  • Resolve Win10 upgrade errors

    Posted on March 14th, 2019 at 11:51 woody Comment on the AskWoody Lounge

    @joep517 bumped into an interesting document that you should stick in your bag of tricks.

    Officially, it’s a Windows IT Pro Center blog entry. Unofficially, it has a lot of useful information for when something Win10 goes bump in the night. With a mass migration to Win1o 1809 under way, and another to 1903 expected shortly, you might want to give it a gander and bookmark it for reference, for when your machine dies. (Better bookmark it on  your tablet or phone, eh?)

    It’s called Resolve Windows 10 upgrade errors : Technical information for IT Pros but don’t let that put you off. The information there works for everybody. It’s just that you may need to strap on your hip waders if you try to go in deep.

    The “quick fixes” section contains general troubleshooting advice that we seem to repeat here over and over:

    • Unplug external hardware
    • Turn off your antivirus
    • Check your c: drive
    • Run the Windows Update troubleshooter

    and so on. From there, the going gets tough.

    Check it out. From Microsoft, so it has to be right, right?

  • Pi day deals

    Posted on March 14th, 2019 at 10:18 woody Comment on the AskWoody Lounge

    Silly me. I thought Pi day was July 22….