We value your privacy

We use cookies to enhance your browsing experience, serve personalized ads or content, and analyze our traffic. By clicking "Accept All", you consent to our use of cookies.

Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

NewApp Digest
search bot

error message

Microsoft solves dual-boot problems with Windows and Linux
Winsage
May 16, 2025

Microsoft solves dual-boot problems with Windows and Linux

Microsoft addressed issues with dual-boot installations involving Linux that were caused by updates released in August, which disrupted many configurations and Linux boot media. The updates aimed to enhance security by blocking outdated boot managers but resulted in error messages indicating a security policy violation. To resolve these issues, Microsoft created the Secure Boot Advanced Targeting (SBAT) update to prevent installation on dual-boot systems, but the detection mechanism was often ineffective. The SBAT update was paused in September, and Microsoft announced that the problem was resolved with security updates released in May. Affected Windows versions include Windows Server editions from 2012 to 2022, Windows 11 (versions 23H2, 22H2, and 21H2), and Windows 10 (versions 22H2, 21H2, and Enterprise 2015 LTSB). Microsoft also provided guidance for users to prevent the SBAT update and steps to restore dual-boot systems.
Announcing Windows 11 Insider Preview Build 27858 (Canary Channel)
Winsage
May 16, 2025

Announcing Windows 11 Insider Preview Build 27858 (Canary Channel)

Windows 11 Insider Preview Build 27858 has been released to the Canary Channel. A new system tray icon for the emoji and more panel has been introduced, allowing users to access emojis, GIFs, and Kaomojis, with customization options available. Several fixes have been implemented, including resolving black screen issues during upgrades, enhancing accessibility in File Explorer, updating desktop icon logic, fixing voice typing initiation issues, resolving explorer.exe crashes related to snap layouts, addressing taskbar icon resizing problems in tablet mode, fixing night light functionality, and resolving MIDI device recognition issues. Known issues include potential problems with Windows Hello PIN and biometrics on new Copilot+ PCs and unresponsive pen input on certain devices. Insiders are reminded that builds in the Canary Channel are early development versions and may change. A clean installation is required to exit the Canary Channel, and a desktop watermark will be present in pre-release builds.
Microsoft fixes Linux boot issues on dual-boot Windows systems
Winsage
May 14, 2025

Microsoft fixes Linux boot issues on dual-boot Windows systems

Microsoft addressed a boot issue affecting dual-boot systems running Linux alongside Windows after the August 2024 Windows security updates, which caused Linux systems to fail to boot due to a Secure Boot Advanced Targeting (SBAT) update. This issue impacted various Windows operating systems, including Windows 10, Windows 11, and Windows Server 2012 and later. The problem arose from a detection mechanism that failed to recognize some customized dual-boot setups, leading to error messages such as "Something has gone seriously wrong: SBAT self-check failed: Security Policy Violation." Microsoft confirmed that the boot issues would be resolved with the May 2025 Patch Tuesday security updates and provided a temporary workaround in late August, advising users to delete the SBAT update. On September 19, Microsoft stopped the automatic application of the problematic SBAT update and recommended a command to prevent future SBAT updates. The issue was specific to the August 2024 security and preview updates, and subsequent updates starting with September 2024 did not contain the problematic settings.
Microsoft is testing a new 'Advanced Settings' page in Windows
Winsage
May 12, 2025

Microsoft is testing a new ‘Advanced Settings’ page in Windows

Microsoft is testing a revamped "Advanced Settings" page for its Windows Server operating system, which will replace the previous "For Developers" page. This new page aims to improve user accessibility by including features beneficial to a wider audience, such as the "End Task" option. It introduces a "long path" setting that removes the 260-character limitation on file paths, helping users avoid the "Path too long" error. The changes are currently exclusive to Windows Server but may extend to Windows 11 within the calendar year.
How to upgrade your 'incompatible' Windows 10 PC to Windows 11
Winsage
May 9, 2025

How to upgrade your ‘incompatible’ Windows 10 PC to Windows 11

On October 14, 2025, Microsoft will stop providing security updates for Windows 10 unless users enroll in the Extended Security Updates program. Upgrading to Windows 11 may be difficult for PCs older than five or six years due to strict compatibility requirements, including a CPU on the approved list and a Trusted Platform Module (TPM) version 2.0. Users may encounter error messages if their hardware does not meet these criteria. There are workarounds for some users, particularly those with PCs designed for Windows 10, but older devices, especially with AMD processors, may face significant challenges. To upgrade, users must ensure their PC is configured to start with UEFI, supports Secure Boot, and has an enabled TPM. A registry edit can allow bypassing CPU checks and accepting older TPM versions. Alternatively, a clean installation of Windows 11 can be performed using installation media, which bypasses CPU compatibility checks but still requires TPM and Secure Boot support. Microsoft has introduced new restrictions with the Windows 11 version 24H2 update, requiring CPUs to support specific instructions (SSE4.2 and PopCnt). For those opting to use the Rufus utility to create installation media, it is essential to use version 4.6 or later to bypass compatibility checks. Users must download the Windows 11 ISO, prepare a USB drive, and follow specific steps to initiate the upgrade process.
Windows 11 24H2 now 'broadly available' – with a new problem
Winsage
May 6, 2025

Windows 11 24H2 now ‘broadly available’ – with a new problem

Microsoft has released Windows 11 24H2, but users are facing a known issue with Azure Virtual Desktop (AVD) applications, specifically related to the "App attach" feature. This feature allows applications to be dynamically attached to user sessions within AVD, operating within containers rather than being installed locally. Users may encounter an error message stating, "Element not found" when launching App attach applications. Microsoft recommends using VHDX images instead of CimFS images for packaging files, as the issue has not been reported in earlier versions of the operating system. A fix for the current version is expected by June 2025. The update for Windows 11 24H2 will be automatically received by devices running Windows 11 22H2 and 23H2, with users able to select the restart time or postpone the update.
Microsoft fixes bug causing incorrect 0x80070643 WinRE errors
Winsage
April 24, 2025

Microsoft fixes bug causing incorrect 0x80070643 WinRE errors

Microsoft has resolved a known issue causing 0x80070643 installation failure errors during the deployment of the April 2025 Windows Recovery Environment (WinRE) updates. This issue affected the KB5057588 update for Windows Server 2022 and the KB5057589 update for Windows 10, versions 22H2 and 21H2. The error message was misleading, as it did not reflect the actual status of the update or the device's performance. The error typically occurred when a device attempted to install the WinRE update while another update was pending a reboot. Microsoft confirmed that users will no longer see the incorrect error message after installing the affected updates. Additionally, in August of the previous year, Microsoft retired the January 2024 Windows security updates that also triggered 0x80070643 errors during WinRE updates. During that time, fraudulent IT support websites promoted malicious PowerShell "fixes" for these errors, leading to malware infections among users.
Starship blooper: Windows 10 update gets weirdest bug yet
Winsage
April 16, 2025

Starship blooper: Windows 10 update gets weirdest bug yet

Windows 10 has released a patch (KB5057589) for the Recovery Environment (WinRE) for versions 21H2 and 22H2. Some users are encountering a misleading error message indicating that the patch installation has failed, despite the update being successfully applied. Microsoft has stated that this error does not affect the update's functionality or the device. The misleading 'failed' status may remain until the next update check, at which point it should clear. The issue is primarily the erroneous error message, and Microsoft is working to resolve it.
Search