BrianFagioli shares a report from NERDS.xyz: NordVPN has open sourced its Linux GUI on GitHub, giving the community full access to the code behind its graphical client. The move follows a 70 percent surge in daily active Linux users since the GUI's debut earlier this year, showing clear demand for a user friendly VPN experience on the platform. Alongside the previously open sourced command line tool, the GUI codebase is now available for anyone to audit, modify, and contribute to. While NordVPN's core backend infrastructure remains proprietary, the company says the open source release reflects its commitment to transparency and collaboration with the Linux community. The GUI can also now be installed with a single command using Snap, simplifying setup and ensuring automatic updates across distributions.

Read more of this story at Slashdot.

It's time to retire NTLM - but how? Richard chats with Steve Syfuhs about the need and challenge of retiring an ubiquitous authentication protocol first used in the 1990s. While guidance to move away from NTLM has been available since 2010, it has only become feasible in the past couple of years, and Microsoft is now providing tooling to make the transition easier. Steve discusses enabling auditing of NTLM usage - recent improvements will allow you to view which services rely on NTLM. Sometimes, a configuration change can resolve the problem, and now there is Microsoft Negotiate to help as an intermediary in determining which protocol to use. Retiring NTLM won't happen overnight, but it will happen, and you can start preparing for it today. And if you need help or advice, email ntlm@microsoft.com!

Links

• NTLM Blocking and You
• Deprecating NTLM is Easy and Other Lies
• Microsoft Negotiate
• Remote Desktop Gateway Role
• Kerberos on Windows Server
• The Evolution of Windows Authentication

Recorded September 25, 2025

Download audio: https://cdn.simplecast.com/audio/c2165e35-09c6-4ae8-b29e-2d26dad5aece/episodes/f97e51b3-0618-431b-a4fd-fb2b976f0a8f/audio/ecd81839-0b9a-4f9a-8ffb-c54ba7375c90/default_tc.mp3?aid=rss_feed&feed=cRTTfxcT

---

Florian Gilcher, co-founder of Ferrous Systems and the Rust Foundation, speaks with host Giovanni Asproni about the application of Rust in mission- and safety-critical systems. The discussion starts with a brief overview of such systems, and an introduction to Rust, emphasizing aspects that make it well-suited for critical environments.

Florian and Giovanni then discuss how Rust compares to C and C++ — two widely used languages in this sector. They proceed to outline important factors that companies should consider when assessing whether to move from C or other languages to Rust. The episode also touches on Ferrocene, an open-source Rust toolchain qualified for safety- and mission-critical systems, which was developed and supported by Ferrous Systems. The conversation ends with some reflections on the future of Rust for mission- and safety-critical applications.

Brought to you by IEEE Computer Society and IEEE Software magazine.

Download audio: https://traffic.libsyn.com/secure/seradio/690-florian-gilcher-rust-safety-critical-systems.mp3?dest-id=23379

---

Windows 10 reaches end of support on October 14, 2025. A great place to learn about all the Windows 10 Extended Security Updates (ESU) options is in our blog post, When to use Windows 10 Extended Security Updates.

In this article, I will provide more detail on the Windows 10 lifecycle for Windows 365 across the following scenarios:

• Existing Cloud PCs running Windows 10

• Creating new and reprovisioned Cloud PCs with Windows 10

• How to create a Windows 10 custom image with Extended Security Updates

• ESUs for physical PCs that connect to Windows 365

• Microsoft 365 Apps support for Windows 10

• Windows 10 ESU support

Existing Cloud PCs running Windows 10

On existing Cloud PCs running Windows 10 22H2 in Azure, ESUs are available at no additional cost—read about the Extended Security Updates (ESU) program for Windows 10 for more information. The ESU program enables PCs to continue to receive critical and important security updates. ESUs will be offered on Cloud PCs running 22H2 when Windows Update or Autopatch is run without requiring any admin action. Updates will be installed based on Windows Update configurations of each Cloud PC and are applied automatically after deployment.

Creating new and reprovisioned Cloud PCs with Windows 10

Starting October 14, 2025 the Windows 10 gallery images have been removed and are no longer available to create new provisioning policies. If you still need to create Windows 10-based provisioning policies, please follow the process to create a custom image based on the Azure Marketplace Images that are available until April 14, 2026.

Windows 365 provisioning policies that use Windows 10 22H2 gallery images (with or without Microsoft 365 Apps) will continue to work until April 14, 2026. After that date, these images will be retired and no longer available. For any provisioning policies that still reference these images, the image status will change to “out of support” and new provisioning attempts will fail. To learn more, please read Lifecycle policies and end of support for Cloud PC operating systems.

The final monthly update to the Windows 365 Windows 10 gallery images will be the Windows 10 October 2025 update. Between October 2025 and April 2026, Cloud PCs created will need to install ESUs to be current. Microsoft recommends switching to Windows 11 for a more secure Windows experience.

A Windows 10 22H2 image that contains the October 2025 update will remain published in the Azure Marketplace. This is the same version as published in Volume Licensing and Visual Studio downloads. It does not contain any Windows 365 or Microsoft 365 app customizations.

How to create a Windows 10 custom image with Extended Security Updates

After April 2026, customers that want to create a Windows 10 image will need to create a custom image and import it into Windows 365. Here’s how:

1. Create an Azure Virtual Machine using Windows 10 22H2 from Azure Marketplace.
   1.  Note: the last Windows 10 image available is October 2025.
2. Perform a Windows Update to ensure the latest ESUs are installed. Multiple reboots may be required.
3. Review support details before installing Microsoft 365 apps.
4. Follow all instructions for creating and importing custom images into Windows 365.

ESUs for physical PCs that connect to Windows 365

If users are connecting to Cloud PCs from Windows 10 physical PCs that are Intune-managed, each physical PC is automatically entitled to receive Windows 10 ESUs. This benefit’s purpose is to extend the life of Windows 10 PCs that do not meet Windows 11 hardware requirements.

Note: Physical devices connecting to Windows 365 Frontline Shared and Windows 365 Reserve Cloud PCs are not eligible for free ESUs.

Learn more about enabling Extended Security Updates (ESU).

Microsoft 365 Apps support for Windows 10

Visit Windows 10 end of support and Microsoft 365 Apps to learn more.

Windows 10 ESU support

We will determine if the issue pertains to Windows 365 or with Windows 10. If the issue is determined to be with Windows 365, we will support as expected and work towards a resolution to your reported issue. If the issue is determined to pertain to the operating system, we will request/require an attempt to reproduce the same issue on a currently supported version of Windows 11. If that issue is able to reproduce on Windows 11, we will work that issue as it is supported. Once resolved, and if applicable, we can attempt to apply that same solution to the originally reported Windows 10 system. If the Windows 11 solution does not resolve the issue on Windows 10, we would recommend upgrading to Windows 11 as Windows 10 is no longer supported.

---

Continue the conversation. Find best practices. Bookmark the Windows Tech Community, then follow us @MSWindowsITPro on X and on LinkedIn. Looking for support? Visit Windows on Microsoft Q&A.