• Intel’s troubles

    FROM THE FORUMS

    Talk Bubbles

    Will Fastie’s article last week, of the same name, drew quite a few readers to its forum. Contributors homed in on the manufacturing-quality problem with 13th- and 14th-generation Intel processors. In addition to the forum posts, Will received a fair number of emails on the topic.

    As mentioned in the article, Intel has not been transparent about the chip problems, adjusting its story and response several times. It is thus important to follow this matter because these two generations of chips make up the bulk of current PC sales.

    Read the full story in our Plus Newsletter (21.34.0, 2024-08-19).
    This story also appears in our public Newsletter.

  • Crypto rip-offs are truly horrifying

    PUBLIC DEFENDER

    Brian Livingston

    By Brian Livingston

    I’ve been spending my time lately reading a new book that describes cryptocurrency nightmares. It was like sitting in a movie theater, watching a horror film that makes audience members scream at the lead actress, “Don’t open that door!”

    The female star, of course, opens the door, no matter how loudly the audience yells. But instead of sitting in a darkened theater, you can read my favorite new book in a well-lighted room. You’ll still find yourself terrified by the scams and rip-offs that crypto promoters perpetrate on innocent altcoin buyers.

    Read the full story in our Plus Newsletter (21.34.0, 2024-08-19).

  • Can Office and Windows play nice on ARM computers?

    MICROSOFT 365

    Peter Deegan

    By Peter Deegan

    ARM-based computers are about to move from a nerd niche to a mainstream product with the arrival of Copilot+ PCs and the increasing popularity of Mac computers.

    What are the compatibility issues for running Windows apps, especially Microsoft Office, on this very different hardware?

    Though Windows and Office look the same on both ARM and Intel computers, their CPUs are fundamentally different. Under the hood, there are big differences in the software layers between the hardware and what you see on the screen. It’s a bit like the difference between a petrol and an electric car — both look and are driven the same, but they have hugely different engines and mechanics.

    Read the full story in our Plus Newsletter (21.34.0, 2024-08-19).

  • Home-networking primer, part 2

    NETWORKING

    Ed Tittel

    By Ed Tittel

    It’s time to revisit home-networking tools and technologies, especially on the wireless side of things.

    In this, the second of a two-part series about the basics of Windows networking at home, we progress into the boundary devices used to connect your local-area network to the provider’s network and on to the Internet. We’ll touch on device economics, mesh networks, and the enduring value and appeal of wired Ethernet in our ever-more-wireless world.

    Read the full story in our Plus Newsletter (21.34.0, 2024-08-19).

  • MS-DEFCON 3: Blocking a potential wormable event

    alert banner

    ISSUE 21.33.1 • 2024-08-16

    MS-DEFCON 3

    By Susan Bradley

    It’s been a long time since we’ve had a Microsoft worm event.

    Last week’s patches contained a fix for the Windows TCP/IP Remote Code Execution Vulnerability identified as CVE-2024-38063. This one affects all supported Windows versions and extends back to Windows 7 and Windows 8, including older servers.

    This CVE has a very high danger rating. Because of that, I am lowering the MS-DEFCON level earlier than I normally would, setting it to 3. That sounds backward, but this advisory is conditional, based upon the type of user you are and how you decide to deal with the update.

    Although the danger is real, I believe the risk is somewhat less. In this alert, I’ll explain why.

    Anyone can read the full MS-DEFCON Alert (21.33.1, 2024-08-16).

  • Patch List for August 13, 2024

    Once again I don’t recommend installing updates at this time.  I’ve updated the master patch list here.

    In my early consumer testing I’m personally not seeing anything but it’s way too early to be calling it at this point. There is a replaced update for KB5034440/KB5034441 updates, but be aware it’s only offered up IF you have enough free space.  Thus I don’t consider KB5042321 a true replacement for those updates. If you had size issues before, this update will not be offered up to you.

    As always, thank you all for supporting the cause! Remember we use the “name your price” model where you can choose how much you will pay for  a membership . Plus membership gives you access and if you donate $50 or more you’ll get a special code to enable text messages sent to your phone each time the Master Patch List gets updated and when I change the MS-DEFCON level.

    More details about these updates in Monday’s newsletter.  You are missing out if you don’t sign up. All content is human made with our own blood, sweat, tears, fingers and brain power and 100% AI free.  Therefore, if I’ve fat fingered any KB numbers or if you have any questions, as always post in the forums and I’ll follow up!

  • Here comes August 2024 updates

    Ready or not, here we go for the August updates.

    First up Windows 11 23H2/22H2 KB5041585

    Microsoft indicates it will be addressing the following issues:

    • [BitLocker (known issue)] A BitLocker recovery screen shows when you start up your device. This occurs after you install the July 9, 2024, update. This issue is more likely to occur if device encryption is on. Go to Settings > Privacy & Security > Device encryption. To unlock your drive, Windows might ask you to enter the recovery key from your Microsoft account.
    • [Lock screen] This update addresses CVE-2024-38143. Because of this, the “Use my windows user account” check box is not available on the lock screen to connect to Wi-Fi.
    • [NetJoinLegacyAccountReuse] This update removes this registry key. For more information refer to KB5020276—Netjoin: Domain join hardening changes.
    • [Secure Boot Advanced Targeting (SBAT) and Linux Extensible Firmware Interface (EFI)] This update applies SBAT to systems that run Windows. This stops vulnerable Linux EFI (Shim bootloaders) from running. This SBAT update will not apply to systems that dual-boot Windows and Linux. After the SBAT update is applied, older Linux ISO images might not boot. If this occurs, work with your Linux vendor to get an updated ISO image.

    Windows 10 22H2 KB5041580 

    Interestingly enough ALSO refers to those same issues being addressed…but only linked under the Windows 10 LTSC releases……I’ll be asking around as to what that means.

    As usual this is the time for us battle tested veterans to test and see how the waters are. For the rest of the Askwoody readership, put yourself on pause, ensure your backups are working and wait as I see what shakes out.

    More in Monday’s newsletter. Don’t forget to join so all the details can be sent to your inbox.

     

  • Intel’s troubles

    newsletter banner

    ISSUE 21.33 • 2024-08-12

    INTEL

    Will Fastie

    By Will Fastie

    In the nearly 50 years I’ve been following Intel, I’ve never seen the company in such disarray. Things are bad.

    On August 1, Intel released its financial results for its second fiscal quarter ending July 31. Although there was a tiny bright spot in its Client Computing Group (up 9% year over year), net revenue was down 1% and the company recorded a quarterly loss of USD $1.6 billion, nearly $3 billion lower year over year.

    Intel’s stock dropped by over 25% in the two following days. And that’s just one of Intel’s problems.

    Read the full story in our Plus Newsletter (21.33.0, 2024-08-12).
    This story also appears in our public Newsletter.