bug affecting

Winsage
July 18, 2026
Microsoft held its OEM Secure Boot Office Hours event on July 15, where engineers collaborated with OEM representatives from companies like Acer, Asus, Cisco, Dell, and HP. IT administrators were able to ask live questions about the Secure Boot 2023 rollout. The discussion thread became a detailed technical record, especially following the expiration of the first certificates three weeks prior. Concerns raised by IT admins included BitLocker recovery loops, stuck confidence ratings, and unhelpful Intune error codes. Key facts include: - Devices offline for long periods will still receive the 2023 certificates upon reconnecting to Windows Update. - Devices with existing 2023 certificates in firmware will switch to the new boot manager after the latest Windows patches are installed. - A new script, Detect-SecureBootCertUpdateStatus.ps1, is available in Windows for checking certificate status. - BIOS updates may reset a device’s confidence rating to unrated, which is normal and does not indicate certificate failure. - Admins should edit the AvailableUpdates registry key, not the AvailableUpdatesPolicy, which is managed by Intune and Group Policy. - A licensing bug affecting AvailableUpdatesPolicy on devices upgraded from Pro to Enterprise was resolved by Microsoft in 2026. - BitLocker recovery is not typically linked to the certificate update process but may relate to firmware or PCR issues. - Dell and HP provided guidance on which BIOS versions include the 2023 certificates for their newer models. - Older HP EliteBook 840 G5 units require a manual update package for the new certificates. - Eligible devices can still receive the 2023 certificates in the future, and Surface devices released from 2024 onward come pre-equipped with them. - Microsoft confirmed that devices running 2011 certificates will not lose the ability to receive the 2023 chain. - The Microsoft Corporation KEK CA 2011 and Microsoft UEFI CA 2011 certificates have expired, with the Microsoft Windows Production PCA 2011 set to expire on October 19, 2026.
AppWizard
July 7, 2026
Players can find abandoned camps in the Pale Garden and Flower Forest biomes, which include a one-time use Straw Bed crafted from three hay bales. Cushions, available in 16 colors and crafted from three wool slabs, allow players to sit comfortably but are not currently spawning in abandoned camps. Various gameplay and graphical improvements have been made, including fixes for crafting recipes, ambient sounds, and rendering issues. Additionally, there are updates to the user interface, technical features, and stability enhancements, such as improved server self-repair capabilities and bug fixes related to commands and entity behavior.
Winsage
July 1, 2026
Microsoft has restored GIF functionality in the Emoji Panel for Windows 11 users after the retirement of the Tenor GIF search engine's API, which caused disruptions starting June 30. The company has transitioned to GIPHY as the new GIF provider, implemented in the preview cumulative update KB5095093 released on June 23 for Windows 11 versions 24H2, 25H2, and 26H1. Users are advised to install the latest updates to restore GIF functionality. Microsoft is also working on a solution for users on Windows 11 23H2 and Windows Server 2025. The KB5095093 update includes the Point-in-Time Restore feature and addresses various bugs and known issues.
AppWizard
June 19, 2026
Foldable smartphones have introduced a new gaming feature, but some Pixel users are experiencing a bug that prevents certain applications from recognizing Wi-Fi connections, forcing them to use mobile data. This issue particularly affects Google apps and TikTok. While Google has not provided an official solution, some users have found workarounds, such as enabling IPv6 connections in their router settings, though results vary. The bug has emerged alongside the beta release of Android 17, leading to user frustration and the suggestion to submit bug reports to the Google Issue Tracker for resolution.
Winsage
June 19, 2026
Microsoft has confirmed a bug affecting the Recycle Bin across all supported versions of Windows following its June 2026 Patch Tuesday update. The glitch causes the confirmation dialog to display an "internal" filename instead of the user-friendly filename when deleting files, although the actual file and its deletion process remain unaffected. The issue affects various Windows client and server versions, including Windows 11 (versions 26H1, 25H2, 24H2, 23H2), Windows 10 (versions 22H2, Enterprise LTSC 2021, Enterprise LTSC 2019, Enterprise LTSB 2016), and Windows Server (2025, 2022, 2019, 2016, 2012 R2, 2012). Microsoft is developing a permanent solution, but it is unclear when it will be released. Commercial customers can contact Microsoft Support for Business for a workaround.
AppWizard
June 19, 2026
Users of Android 17 have reported that home screen widgets are disappearing after the latest stable update, specifically on devices with a work profile. Google is aware of the issue and is working on a fix, which may be included in the next month's security update. Currently, there is no effective workaround other than removing the work profile, which allows users to restore their widgets by restarting the device and re-adding them.
Winsage
June 18, 2026
Microsoft resolved an installation issue affecting the June 2026 security updates (KB5094122) on Windows Server 2016 systems that had not previously installed the KB5087537 update, which was a prerequisite. Users had encountered 0x80070002 or FILENOTFOUND errors. Microsoft acknowledged the problem and confirmed that affected devices should no longer experience installation failures for the June 2026 update. Additionally, Microsoft fixed a similar issue with the May 2026 Windows 11 security update (KB5089549) that resulted in 0x800f0922 errors due to insufficient space on the EFI System Partition. They also warned users about potential installation issues with error codes 0x80073712 or 0x800f0993 on devices upgraded to Windows 11 24H2 or 25H2. Furthermore, Microsoft addressed a boot issue for Windows Server 2025 devices after the April 2026 update and a bug affecting installation failures for updates since May 2025 using the Windows Update Standalone Installer (WUSA). Lastly, they are investigating a separate issue preventing third-party applications from launching essential Office programs after the June 2026 updates.
Winsage
May 28, 2026
Microsoft released a mandatory patch (KB5087537) for Windows Server 2016 to enhance cryptographic layers and address critical vulnerabilities. This update is essential for organizations using legacy workloads, as mainstream support ended in January 2022, but extended support continues until January 12, 2027. The patch aims to prepare systems for the expiration of Windows Secure Boot certificates in June 2026, which, if not updated, could compromise security and expose systems to malware. The update uses a phased deployment model and includes a new SecureBoot folder to assist IT professionals in managing certificate status. It also addresses various quality-of-life issues, including bugs affecting Remote Desktop Connection and authentication errors with Microsoft services. However, a significant issue arises when the host server name is exactly 15 characters long, causing failures in the domain controller discovery process and obstructing critical operations. This bug is linked to the historical 15-character limit of NetBIOS, which affects the Active Directory lookup mechanism. Microsoft has acknowledged the issue but has not provided a timeline for a fix, leaving administrators to either rename servers or uninstall the update. As the Secure Boot deadline approaches, IT departments must carefully assess their environments to avoid disruptions while ensuring security compliance.
Winsage
May 26, 2026
Microsoft has acknowledged an issue affecting Windows Server 2016 systems related to domain controller lookups after the installation of the KB5087537 security update released in May 2026. The problem occurs specifically for devices with hostnames that are exactly 15 characters long, causing domain controller discovery to fail and resulting in an ERRORINVALIDPARAMETER during DCLocator calls. This issue may disrupt administrative operations that depend on domain controller lookups, such as DFS Namespace management. Microsoft is investigating the issue but has not provided a timeline for resolution.
Search