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

Blog Archives

  • Are we ready for the new Windows 10 1903?

    Posted on June 17th, 2019 at 02:10 Tracey Capen Comment on the AskWoody Lounge

    A Microsoft tweet announced that the company is now offering Win10 Version 1903 — but only to those who specifically seek it.

    Opening Windows Update and selecting Check for updates should trigger the Version 1903 download. If you clicked the button but did not receive the update, you probably have some sort of blocking condition. You’ll just have to wait — and you should.

    Out today in AskWoody Plus Newsletter 16.22.0.

  • The case against knee-jerk installation of Windows patches

    Posted on June 16th, 2019 at 21:12 woody Comment on the AskWoody Lounge

    I finally had a chance to put together a manifesto for a heretical position I’ve taken publicly for more than a decade:

    Windows Automatic update is for chumps

    Yes, you have to get patched sooner or later (although Group W holdouts will disagree), your Sainted Aunt Martha should be on auto updates, and a tiny number of patches have to go in right away. But in the vast majority cases, for the vast majority of people, installing patches as soon as they roll out just doesn’t make sense.

    Unless you have a staff charged with vetting patches, it’s much smarter to crowdsource patch beta testing. Don’t get pushed into blindly taking what comes out the auto update chute.

    Details in Computerworld Woody on Windows.

  • Reports that some update is clobbering LiteTouch.lnk, the restart shortcut for the Microsoft Deployment Toolkit

    Posted on June 16th, 2019 at 20:45 woody Comment on the AskWoody Lounge

    At first I thought this was a one-off, but now I’ve seen confirmation that it’s happening.

    For unknown reason, after installing updates, the LifeTouch.lnk scheduled task is deleted, so MDT doesn’t know to restart itself. From Dan Jackson:

    Ends up he’s working with Win10 1607 LTSC.

    There’s a confirmation tweet from Ray Tiley:

    Ray’s running Win10 1809 LTSC.

    There’s also a post on the TechNet support forum from AdminSN:

    does one of you know the problem that the Bitdefender deletes the shortcut LiteTouch.lnk and classifies it as a Trojan (Trojan:Script/Cloxer.A!cl)?

    Can anybody else out there confirm this problem?

  • Microsoft’s getting better at documenting the most egregious bugs in Windows patches

    Posted on June 13th, 2019 at 05:27 woody Comment on the AskWoody Lounge

    But there’s still a lot of grist to this month’s mill.

    Details in Computerworld Woody on Windows.

  • June 2019 Patch Tuesday is rolling out

    Posted on June 11th, 2019 at 12:27 PKCano Comment on the AskWoody Lounge

    With Bluekeep patching behind us (hopefully), we are waiting for the June 2019 results to come rolling in.

    There are (only) 108 new entries in the Windows Update Catalog.

    The Security Update Guide lists 2,210new individual patches today.

    Martin Brinkman has his usual thorough summary posted on ghacks.

    Microsoft released security updates for all supported versions of the Microsoft Windows operating system on the June 11, 2019 Patch Day.

    • Microsoft released security updates for all supported versions of the Windows operating system in June 2019.
    • All client and server versions have critically rated vulnerabilities patched.
    • Microsoft released security updates for other products such as Internet Explorer, Microsoft Edge, Microsoft Office, Azure, Microsoft Exchange Server, and Skype

    Windows 7: 42 vulnerabilities of which 3 are rated critical and 39 are rated important
    Windows 8.1: 35 vulnerabilities of which 3 are rated critical and 32 are rated important
    Windows 10 version 1703:  41 vulnerabilities of which 4 is critical and 37 are important
    Windows 10 version 1709: 43 vulnerabilities of which 4 is critical and 39 are important
    Windows 10 version 1803: 45 vulnerabilities of which 3 are critical and 43 are important
    Windows 10 version 1809: 47 vulnerabilities of which 3 are critical and 44 are important
    Windows 10 version 1903: 42 vulnerabilities of which 3 are critical and 39 are important

    Internet Explorer 11: 7 vulnerability, 5 critical, 2 important
    Microsoft Edge: 14 vulnerabilities, 12 critical, 2 important

    Dustin Childs has his report of Microsoft released CVEs, 88 of them including an exploit for Windows Task Scheduler, for ZDI.

    Earlier today, Microsoft released a patch to address CVE-2019-1069, an escalation of privilege vulnerability in the Windows Task Scheduler. Bugs of this nature have existed since Windows XP, but this most recent version impacts the latest Windows 10 and Windows Server 2019 versions. Information about the vulnerability was publicly available prior to the patch being released…

    See the full report on ZDI.

    For those of you updating manually, there are new Servicing Stacks for Server 2019, Server 2016,  and Win10 v1809 and v1607.

  • MS-DEFCON 2: Make sure Windows Update is de-fanged. Patch Tuesday’s tomorrow.

    Posted on June 10th, 2019 at 03:13 woody Comment on the AskWoody Lounge

    It’s been an interesting month in Patch City. First the WinXP/Vista/Win7 emergency patch (yes, you need to install the latest patches for all of them), and then the release of Win10 version 1903, which only appears to be going out to suckers, er, seekers. There’s one born every minute.

    I have a full rundown of what to do and how to do it — with special new instructions for those of you running Win10 1903 — in Computerworld Woody on Windows.

  • Are Bluekeep patches causing BSODs with Server 2008 SP2 and Vista?

    Posted on June 7th, 2019 at 17:23 PKCano Comment on the AskWoody Lounge

    There are reports that the Monthly Rollups started causing problems with Server 2008 SP2 beginning in April. It seems the same issues have occurred on Windows Vista  with Microsoft’s advice to patch for Bluekeep using Server 2008 SP2 patches.
    According to the same anonymous poster who reported the issues in April with KB4493471:

    I realize this topic is getting old, but Avast just recently took action to address issues that have existed on Server 2008 SP2 since April updates changed the build number to 6003.[…]. They say “the squeaky wheel gets the oil,” and Windows 7 certainly squeaks louder than Server 2008; but Avast finally heard a different squeak in a recent spiceworks thread titled Windows Bluekeep patches causing Win32k.sys 0x0000008E BSOD. Avast has recently posted new Knowledge Base articles with titles such as BSOD/Failure to Boot after Installing Avast Business Antivirus version 18.8 on Windows Server 2008. The same issues occurred on Windows Vista if Microsoft’s advice to patch BlueKeep by installing KB4499180 was taken.

    Are any of you seeing these issues, particulatly among those patching Vista for Bluekeep with the Server 2008 SP2 Rollups?

    Reference: Spiceworks thread and Avast Knowledge Base article.

    Thx, anonymous

  • Patch Lady – I like 1903

    Posted on June 5th, 2019 at 11:25 Susan Bradley Comment on the AskWoody Lounge

    Just the other day on CSOOnline I showcased the new security features in 1903.  I really like 1903 and (fingers crossed) I’m hopeful it will be the one we all soon settle on.  Notice the word soon.  I’m still not ready to install it on the office computers.  Test computers have it now, production machines, not yet.

    Until then keep an eye on the security enhancements and — newsflash – that sandbox feature only needs Pro to be enabled.