bootable media

Winsage
April 16, 2025
The NTFS file system has been the default for Windows operating systems for decades, but Microsoft is developing the Resilient File System (ReFS), which has been in use primarily in Windows Server environments since its introduction in 2012. ReFS is designed to enhance system and data resilience, featuring error detection and correction capabilities, a data integrity scanner, and the ability to repair detected corruption using another volume. It supports file and volume sizes up to 35 petabytes and includes advanced features like Block Clone and Sparse VDL, which improve performance in specific scenarios. However, ReFS is not a full replacement for NTFS, as it lacks several critical features such as file system compression, encryption, bootable media support, and support for removable media. Its current limitations make it unsuitable for typical home PC use, and while it may eventually replace NTFS, this transition is not expected to happen soon. ReFS is primarily designed for specialized applications involving large data sets and environments with multiple drives.
Winsage
February 6, 2025
Microsoft has released a PowerShell script to help users and administrators update bootable media, integrating the "Windows UEFI CA 2023" certificate. This update is in response to the BlackLotus UEFI bootkit, which can bypass Secure Boot and disable Windows security features. Microsoft has issued prior updates in March 2023 and plans additional measures for July 2024, addressing a Secure Boot bypass vulnerability (CVE-2023-24932). The fix will be rolled out in phases before full enforcement anticipated by 2026. The update will include the "Windows UEFI CA 2023" certificate in the UEFI Secure Boot Signature Database and revoke the "Windows Production CA 2011" certificate for older boot managers. Administrators are advised to update bootable media to use the new certificate to avoid booting issues. The PowerShell script is compatible with various media formats and requires the Windows ADK for functionality. Microsoft recommends thorough testing before the enforcement phase, which will begin by the end of 2026, with a six-month notice prior to implementation.
Search