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: November 22, 2019

  • Gahan Wilson, R.I.P.

    Posted on November 22nd, 2019 at 16:01 woody Comment on the AskWoody Lounge

  • Another key Win10 security feature bites the dust: Say goodbye to Windows Defender Exploit Guard

    Posted on November 22nd, 2019 at 08:08 woody Comment on the AskWoody Lounge

    There’s a reason why I’m skeptical about the fancy new security features touted for Win10 versions. In many cases, at least for me, they don’t work. Enterprises have a different school of fish to fry, but the benefits of some of the new features just eludes me.

    Take, if you will, the Windows Defender Exploit Guard. When Win10 version 1709 hit the street, it was billed as a major new security feature that the whole world needs. Although on the surface it seemed like something I could understand — keep rogue programs out of key pieces of Windows — I never got it to work right. Here’s how MS described it back during the 1709 release:

    Implementing Attack Surface Reduction rules within Windows Defender Exploit Guard. Exploit Guard is a new feature of v1709 that helps prevent a variety of actions often used by malware. You can read more about Exploit Guard here: Reduce attack surfaces with Windows Defender Exploit Guard. Note that we have enabled “block” mode for all of these settings. We are continuing to watch the “Block office applications from injecting into other process” setting; if it creates compatibility problems then we might change the baseline recommendation to “audit” mode for that setting. Please let us know what you observe.

    That seems like a worthy goal, and I dutifully reported on it. But I never got it to work.

    Now comes word that Microsoft’s recommending everybody disable it in Win10 1909. From the newly published Security Baseline for 1909:

    Exploit Protection 

    Because of reported compatibility issues with the Exploit Protection settings that we began incorporating with the Windows 10 v1709 baselines, we have elected to remove the settings from the baseline and to provide a script for removing the settings from machines that have had those settings applied. (See Remove-EPBaselineSettings.ps1 in the download package’s Scripts folder.)

    So this once-highly-touted security feature has not only bitten the dust, there’s a handy program included in the Security Baselines toolbox that makes it easy to ensure that the %$#@! thing has been turned off everywhere.

    There’s a reason to be skeptical of new security “features” that you don’t understand….

  • A swarm of iOS 13 bugs lead Apple to change the way it’s testing iOS 14. Will it work?

    Posted on November 22nd, 2019 at 06:39 woody Comment on the AskWoody Lounge

    I bet it doesn’t.

    Paul Thurrot has a succinct tweet:

    If anything, the iOS 13 buggy patch saga is worse than Microsoft’s — a development I would’ve thought impossible just a couple of years ago.

    Mark Gurman at Bloomberg published an article yesterday that explains how Federighi is going to make iOS 14 development better.  How?

    The new approach calls for Apple’s development teams to ensure that test versions, known as “daily builds,” of future software updates disable unfinished or buggy features by default. Testers will then have the option to selectively enable those features, via a new internal process and settings menu dubbed Flags, allowing them to isolate the impact of each individual addition on the system.

    Pshaw. I’d be willing to bet that this approach will create even more confusion – and fewer results – than Microsoft’s much-maligned “Insider” marketing beta approach.

    What ever happened to dedicated testing, by a well-funded team of professionals?

  • Google shutting down Cloud Print late next year

    Posted on November 22nd, 2019 at 06:05 woody Comment on the AskWoody Lounge

    Don’t know about you, but I use Google Cloud Print every day. In fact it’s the only way I print these days. Google’s killing it at the end of next year.

    Here’s what Google says:

    Beginning January 1, 2021, devices across all operating systems will no longer be able to print using Google Cloud Print. We recommend that over the next year, you identify an alternative solution and execute a migration strategy.

    I’ll probably change to Epson’s cloud-based printing service, but what a pain!

    (Technical note: I have an Epson ET-4750 which connects to my office WiFi system. Works great. I could print directly from every other device on my WiFi network, but it’s a bear setting up direct printing from my LAN-attached main computer, unless I go through the cloud.)

    Martin Brinkmann has more details on Ghacks.net.