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 30, 2019

  • Patch Lady – Build numbers are not feature numbers

    Posted on October 30th, 2019 at 19:29 Susan Bradley Comment on the AskWoody Lounge

    So a couple of people have asked how we went from Windows 10 1903 to Windows 10 19013 .  Is it a typo?  Did we really jump from 1903 to 19013?  And the answer is… well one is a feature release name and the other is a build number.

    Currently if you have Windows 10 1903 and have installed the updates as of October 24th https://support.microsoft.com/en-us/help/4522355 you will be on build 18362.449.

    There used to be a site called buildfeed.net that kept track of all the builds but external pressures (probably trying to keep up with the build numbers) made them shift their focus.

    Bottom line Microsoft uses build numbers to track everything.  Us normal folks don’t.  We just call it Windows 10 and then go … uh…what changed?  And why?

    Lifewire has a page with the version numbers to help keep up to date as well.

  • Another patch-induced conflict: Transport Layer Security fails with error 0x8009030f

    Posted on October 30th, 2019 at 11:08 woody Comment on the AskWoody Lounge

    Microsoft has acknowledged a problem with the latest patches for Win7, 8.1, Server 2008,  2008 R2, 2012, 2012 R2 and Server 2016 – Monthly Rollups, Security-only or (apparently) Previews of Monthly Rollups.

    When attempting to connect, Transport Layer Security (TLS) and Secure Sockets Layer (SSL) might intermittently fail or timeout.  You might also recieve one or more of the with the following errors:

    • “The request was aborted: Could not create SSL/TLS secure Channel”
    •  error 0x8009030f
    • An error logged in the System Event Log for SCHANNEL event 36887 with alert code 20 and the description, “A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 20.​”

    If TLS is failing on your up-to-date Win7, 8.1 or related Server based machines, now you know why. There’s a fix, documented in the KB article, but it’s messy.

    Thx @abbodi86

  • Another dumb block: MS induced “VMware Workstation Pro can’t run on Windows”

    Posted on October 30th, 2019 at 08:06 woody Comment on the AskWoody Lounge

    I just heard about this from Office Watch, but checking around, it’s also described on Tenforums and on the VMWare blog.

    When you install any of the recent cumulative updates for Win10 1903 (the third cumulative update for September, or any of the three cumulative updates in October, including the most recent one), Windows starts blocking older versions of VMWare.

    The reason? MS removed VMWare from the Windows Application Compatibility database.

    Apparently VMWare version 15.5 — the latest version — gets around the block. But if you aren’t willing to pay for the latest version, you’re up the ol’ creek.

    The solution is so utterly trivial it boggles even my pre-boggled mind. You rename the program that runs VMWare, C:\Program Files (x86)\VMware\VMware Workstation\vmware.exe. The renamed file passes the Application Compatibility block, and you’re free to use the old version. Stupid.

    Does anybody know if there’s a reason why VMWare versions prior to 15.5 are prohibited from running on post-September-updated versions of Win10 1903?

  • Dedoimedo: Straight talk about Windows 7

    Posted on October 30th, 2019 at 06:41 woody Comment on the AskWoody Lounge

    I don’t agree with everything in the article, but @EP just pointed me to a remarkably well-written and, in my opinion, highly accurate guide to the end of Windows 7. Igor Ljubuncic, on his Dedoimedo blog, doesn’t mince any words:

    If you have a Windows 7 machine, you can continue using it past the operating system EOL date. I’ve laid down the recipe for good security, the hardware will work as long as it lasts, and the software won’t just vanish. You will have time to adjust, and this should coincide with hardware replacement. Once that happens, you should definitely leave Windows 7 behind, and get a modern up-to-date operating system to match the capabilities of your new machine.

    If you’re going to stick with Win7, he has a number of common-sense recommendations (and observations!) that ring true with me.

    I disagree with him on some nit-picking points:

    • I don’t like EMET because it borks too many programs that otherwise work just fine. You can try it, using his recommended method, but if you get too frustrated, don’t be afraid to turn it off.
    • Igor’s fond of Microsoft Office (or at least tolerates it). By and large, I’ve kicked my Office habit – moved to the free Google apps. Like Igor, I also have editors who need Word DOCXs, and I use Office for those, but I’d likely be just as happy using the free online version of Word. Books are a different story altogether, of course — it’s Word all the way with those. Not my choice.
    • He talks about Linux, but doesn’t touch on the most important Linux implementation for Win7 users — ChromeOS. You’ve heard me say it before, but for most people who aren’t overly concerned about snooping, a Chromebook should be your #1 candidate for a replacement computer. (And if you are concerned about snooping, you have a very long row to hoe with Win7.)

    As Igor says, this advice is for home users — if you’re running a 100-machine network, the considerations are quite different. But I still recommend the Chromebook. 🙂

    You’re going to hear a lot of fearmongering, tales of impending hell fire and damnation, from the mainstream press. Many of the people offering the sermons will have the best intentions. But they don’t know your situation, what you need, what you can afford (time and money)… and, ultimately, what’s best for you.

    Win7’s, uh, transition to EOL is not The End of the Universe as We Know It.