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: October 1, 2019

  • Patch Lady – 31 days of security

    Posted on October 1st, 2019 at 23:59 Susan Bradley Comment on the AskWoody Lounge

    October is the national cyber security awareness month and I’m kicking off the month by linking to another author.  John Opdenakker posts about why everyone should care about online security.

    Are you making any changes to your online security due to what’s going on?  I know that I’m adding more multi-factor authentication to my accounts.  What about you?

     

  • Looks like installing a clean Win10 version 1903 Home forces you to use a Microsoft Account

    Posted on October 1st, 2019 at 16:29 woody Comment on the AskWoody Lounge

    For many years, I’ve recommended that users set up a new Windows 10 machine with a Local account — one that isn’t a Microsoft account, and doesn’t phone home to Ma Microsoft every time you log on. (Microsoft now calls it an “offline account.”) I’ve included the detailed step-by-step method, which varies a bit by version, in all of my Windows All-In-One For Dummies books.

    Now it appears as if installing a clean copy of Win10 version 1903 — yes, the one that’s been out for five or six months — makes you jump through a bizarre hoop in order to set up the computer with a Local account.

    I’ve been expecting some shenanigans with Win10 version 1909. Martin Brinkmann posted a report yesterday that he’s still seeing an option to use an Offline account to set up the machines:

    We installed Home and Pro editions of Windows 10 version 1909 multiple times and the offline account option was presented to us each time. It is quite possible that Microsoft is A-B testing the chance or that the change affects only some regions and not others.

    But I’ve also seen many reports that folks clean installing 1909 didn’t have that option — when you set up a new machine with 1909, you have to use a Microsoft account. I figured I’d wait until I have the final, shipping, bits before kicking the tires and raising the roof.

    Now comes word from Chris Hoffman at How-To Geek that the setup routine forces you to use a Microsoft account on version 1903. It’s astounding how much power Microsoft has over privacy-busting “features,” even on versions of Win10 that have been out for a while.

    If you get stuck with installing a clean copy of 1903 or 1909, unplug your machine from the internet during the installation. The exact steps from that point vary a bit, depending on version, but Chris and Martin can take you through the details.

    Justin Pot at How-To Geek calls this kind of flim-flammery a “dark pattern” — a way that companies trick you into doing what they want, in this case to snoop. Er, harvest your telemetry.

  • October 2019 Office non-Security updates have been released

    Posted on October 1st, 2019 at 14:06 PKCano Comment on the AskWoody Lounge

    The October 2019 non-Security Office updates have been released Tuesday, October 1, 2019. They will not included in any DEFCON approval for the September 2019 patches. Unless you have a specific need to install them, you should wait until Susan Bradley (Patch Lady) approves them and any problems have been reported.

    Remember, Susan’s patching sequence and  recommendations are based on a business environment that has IT support and may have time constraints on the updating process. Consumer patching should be more cautious due to limited technical and mechanical resources. The latter is the reason for the AskWoody DEFCON system.

    Office 2010
    Update for Microsoft Outlook 2010 (KB4475604)

    Office 2013
    Update for Microsoft Outlook 2013 (KB4484096)

    Office 2016
    Update for Microsoft Office 2016 (KB4475585)
    Update for Microsoft Office 2016 (KB4484114)
    Update for Microsoft Office 2016 Language Interface Pack (KB4475582)
    Update for Microsoft Outlook 2016 (KB4484107)
    Update for Microsoft PowerPoint 2016 (KB4475578)
    Update for Microsoft Project 2016 (KB4484116)
    Update for Microsoft Word 2016 (KB4484105)
    Update for Skype for Business 2016 (KB4484102)

    There were no non-security listings for Office 2007 (which is out of support).

    Updates are for the .msi version (persistent). Office 365 and C2R are not included.

    Security updates for all supported versions of Microsoft Office are released on the second Tuesday of the month (Patch Tuesday).

  • MS to give small/medium businesses access to Win7 patches after January

    Posted on October 1st, 2019 at 12:50 woody Comment on the AskWoody Lounge

    Chip, chip, chip.

    Jared Spataro, MS corporate VP for Microsoft 365 (note the title) has just posted a reprieve, of sorts:

    today we are announcing that, through January 2023, we will extend the availability of paid Windows 7 Extended Security Updates (ESU) to businesses of all sizes. (Previously, Windows 7 ESU was only available to Windows 7 Professional and Windows 7 Enterprise customers in Volume Licensing.) The Windows 7 ESU will be sold on a per-device basis with the price increasing each year.

    Starting on December 1, 2019, businesses of any size can purchase ESU through the cloud solution provider (CSP) program. This means that customers can work with their partners to get the security they need while they make their way to Windows 10.

    Mary Jo Foley at ZDNet has pricing:

    The price of the ESUs goes from $25 per device for Windows Enterprise users in year one, to $100 per device for year three. For Pro users, ESU pricing goes from $50 per device in year one up to $200 per device in year three.

    I don’t participate in the Cloud Solution Provider program, so I don’t know the precise details. But I have a feeling we’ll find out soon.

  • Microsoft confirms printing bug in second September cumulative update for Win10 1903

    Posted on October 1st, 2019 at 11:21 woody Comment on the AskWoody Lounge

    The Windows Release Information Status page was updated last night to say:

    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing. Some apps may close or error when the print spooler fails and you may receive a remote procedure call error (RPC error) from some printing utility or printing apps.

    Affected platforms:

    • Client: Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1; Windows 7 SP1
    • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

    Workaround: Retrying to print may allow you to print successfully. If retrying does not allow you to print, you may also need to restart your device. If your device is using a v4 print driver and a v3 driver is available, you can also try installing the v3 driver as a workaround.

    Next steps: We are working on a resolution and will provide an update in an upcoming release.

    The announcement’s a little strange in a couple of respects.

    • The report says the bug appears in 1903, 1809, 1803, 1709, 1703, Win7 and 8.1. But I don’t see anything anywhere else about the bug in versions of Windows other than 1903. Can anybody out there confirm?
    • The “Originating update” column says it appeared in the Sept. 23 cumulative update KB 4522016 – which is the second monthly cumulative update for Win10 1903. Yet the KB article itself doesn’t mention the problem, nor does KB 4517211, the third September cumulative update for 1903, which presumably contains the same bug.

    I also note that the update doesn’t single out HP printers — although the majority of complaints I’ve seen are with HP printers.

  • Win10’s usage share is up — but not by all that much

    Posted on October 1st, 2019 at 07:42 woody Comment on the AskWoody Lounge

    Numbers are out for September usage of the various operating systems. Here’s the Netmarketshare analysis, showing Win7 still holds 35% a little under 30% usage share:

    Of course, my standard disclaimer applies: None of the measuring methods is very good. The only real conclusion you can reach by looking at the numbers is to compare how they change from month to month.

    Still, with four months left to go, Win7 is hanging in there pretty well, eh?