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

Monthly Archives: July 2019

  • Windows Defender becomes “Microsoft Defender”

    Posted on July 19th, 2019 at 12:04 woody Comment on the AskWoody Lounge

    Effective with Win10 version 20H1 (gawd, I hope they don’t call it version 2003), Windows Defender will get the new name “Microsoft Defender.”

    I first read about that in a Tero Alhonen tweet, but Martin Brinkmann has a thorough explanation in this ghacks.net post.

    One question has not been answered yet: why is Microsoft making the change? A likely explanation, and our colleagues over at聽Deskmodder聽seem to agree, is that Microsoft wants to use the Microsoft name for services and tools that are available on multiple platforms, and the Windows name if a service or tool is only available on Windows.

  • Patch Lady – what things about patching annoy you?

    Posted on July 19th, 2019 at 01:21 Susan Bradley Comment on the AskWoody Lounge

    What annoys me is

    1. Windows will grab the focus with some message that I don’t realize until it’s too late
    2. Windows will not see that uploading a video to a file sharing site it not active use of a system and thus will reboot right as I’m trying to upload a video (can you tell I hit this tonight?)
    3. If you do want to uninstall an update, how on Windows 10 the security updates are just called cumulative updates and the servicing stack update is called a security update. (Huh?聽 yes I know that’s confusing).
    4. If I want to uninstall an Office 2016 msi update it’s hard to tell what recently was installed as the way Office installs updates, they stamp all other Office updates with the same date.聽 So you have to find the exact Office KB to uninstall what you need.
    5. If you need to uninstall a click to run patch it’s a cumbersome process of reinstalling the prior bundle.

    I love Windows 10 until we get to these feature updates and then they just feel and act like unplanned service packs.

    So what annoys you about patching the most?

  • Are you being pushed from Win10 1803 to 1903? Tell me about it.

    Posted on July 18th, 2019 at 03:41 woody Comment on the AskWoody Lounge

    Microsoft officially started pushing Win10 1803 machines onto version 1903 two days ago. Apparently the push doesn’t respect your Pro settings to “defer feature updates.” At least, that’s what’s been promised.

    I have a honeypot machine that hasn’t been pushed as yet.

    If you get the nudge, I’d be very interested in hearing how it arrived — in particular, are you given a link to “Download and install now” or do you just reboot and BAM! 1903 comes along?

    I think it’s rude of Microsoft to push 1903 on machines that don’t hit end of life until November 12, but that’s just me.

    P.S. For those of you who have asked, no, I don’t think 1903 is ready for prime time. Microsoft hasn’t given the go-ahead for broad deployment of version 1903 among paying customers — and it isn’t clear how that go-ahead will be communicated. There are many acknowledged problems, and a background noise level that’s still disconcerting to me. That said, many people are using 1903 with no problems, but the Nervous Nelly in me still thinks you’re better off with 1803 or 1809.

    Overview now available in Computerworld Woody on Windows.

  • Kevin Beaumont: Still no sign of BlueKeep in the wild

    Posted on July 18th, 2019 at 03:24 woody Comment on the AskWoody Lounge

    In case you were wondering, Kevin Beaumont hasn’t yet detected any BlueKeep infections:

    Good news for you and I – and yet another reminder to install the May Win7 (and XP and Vista) patch!

     

  • Official history of cumulative updates for .NET in Win10 1809 and 1903

    Posted on July 18th, 2019 at 03:17 woody Comment on the AskWoody Lounge

    Two important links for anyone wrangling with .NET updates:

    History of Cumulative Updates for .NET Framework for Windows 10, version 1809

    History of Cumulative Updates for .NET Framework for Windows 10, version 1903

    There aren’t any entries in the latter list, so far.

    Thx, @abbodi86

  • Warning: Some July Office patches make it impossible to save DOC, XLS files on network shares

    Posted on July 17th, 2019 at 12:53 woody Comment on the AskWoody Lounge

    An emergency report:

    It appears that Microsoft closed off write access to the older file extensions when they are located on a network share when some of the July Office patches are installed.

    We鈥檝e positively identified two patches that when removed we know fixes this issue:

    路 KB4475513 (for Excel 2016)

    路 KB4475514 (for Word 2016)

    By also analyzing their associated CVE鈥檚 and also hearing of issues with and Office 2013 as well, we鈥檝e broadened the list to include some of their neighbors:

    路 KB4464565 (for Excel 2013)

    路 KB4464572 (for Office 2016)

    路 KB4464558 (for Office 2013)

    Will keep you posted.

    UPDATE: Many of you have reported that you can’t reproduce this bug. Which is great! But when you post a report, could you include the version of the Server that you’re using? That may be a key difference.

  • Second monthly cumulative updates out for Win10 version 1803, 1709, 1703 – but 1809 and 1903 are missing at the moment

    Posted on July 17th, 2019 at 01:55 woody Comment on the AskWoody Lounge

    Microsoft released the usual “optional” second monthly Cumulative Updates for older versions of Win10, but hasn’t (as of this writing) released fixes for Win10 1809 or 1903. They’re “optional” in the sense that you have to click Check for updates in order to get them – or download and install them manually. Which, of course, you aren’t going to do.

    Win10 1803 gets KB 4507466 — which only lists four bugs fixes:

    Updates an issue that prevents a device from recognizing a Microsoft account until you sign out and sign in again.
    Updates an issue that affects applications that manage files, folders, and device settings.
    Improves compatibility with the Window-Eyes screen reader application.
    Updates an issue to keep your App permissions settings when resetting your device.

    Win7 and 8.1 also received Previews of next month’s Monthly Rollup, which seem to be particularly dull unless you’re concerned about time zones in Brazil.

  • Microsoft: Mumble mumble just ignore Windows Defender mumble mumble

    Posted on July 16th, 2019 at 15:00 woody Comment on the AskWoody Lounge

    Remember the sfc /scannow stupidity – where scanning a perfectly good Windows installation triggered errors such as, “Windows Resource Protection found corrupt files…” ? Susan wrote about it a week ago.

    @EP just posted a link to an official Microsoft explanation, KB 4513240, that sounds similar:

    The System File Checker (SFC) tool flags files in %windir%\System32\WindowsPowerShell\v1.0\Modules\Defender as corrupted or damaged. You see error messages such as the following:

    Hashes for file member do not match.

    This is a known issue in Windows 10, version 1607 and later versions, and Windows Defender version 4.18.1906.3 and later versions…. Future releases of Windows will use the updated files in the Windows image. After that, SFC will no longer flag the files.

    At least, I think it’s the same problem.

    So if you run sfc /scannow with any version of Win10 prior to 1909, you just need to know — by osmosis, no doubt — that you should ignore the error message.

    Meshuggeneh.