malfunction Archives

AppWizard

March 6, 2026

Research company claims spyware posing as Israel’s Red Alert Android app targeting users

Acronis Threat Research Unit (TRU) has uncovered a cyber espionage campaign targeting Israeli civilians through a fake version of the Red Alert app. The attack begins with a deceptive text message claiming to be from Israel's Home Front Command, urging users to download an updated app due to a malfunction. The fraudulent app closely resembles the legitimate Red Alert app but contains malware that collects sensitive personal information, including messages, contacts, location data, and device account details. This data is stored locally and then transmitted to a remote server controlled by the attackers. The hackers use certificate spoofing and other techniques to bypass Android's security measures, making the malicious app appear legitimate. Cybersecurity experts recommend that Israeli users take precautions to protect their personal information.

Winsage

March 6, 2026

Windows 10 has been open to a severe recovery bug without this update

On October 14, 2025, Microsoft ended support for Windows 10 and encouraged users to switch to Windows 11, using full-screen pop-up ads. The company introduced the Extended Security Updates (ESU) program to facilitate this transition. However, issues arose with the Windows Recovery Environment (WinRE), which faced significant problems around the same time Windows 10 was phased out, affecting Windows 11 users as well. Microsoft acknowledged these issues in February and released an emergency patch to fix them. On March 3, 2026, a recovery update for Windows 10 versions 21H2 and 22H2 was rolled out to address the WinRE malfunction. Following the end of support for Windows 10, Windows 11's market share increased to 72.78%. Microsoft plans to improve Windows 11 in 2026 based on user feedback, but Windows 12 is not expected to be released this year.

Winsage

March 5, 2026

Windows 10: WinRE Update KB5075039 fixes issue from Oct. 2025

On March 3, 2026, Microsoft re-released update KB5075039 to restore functionality to the Windows Recovery Environment (WinRE) for Windows 10, which officially fell out of support in October 2025. This update followed a bug caused by dynamic security update KB5067039, released in October 2025, which introduced a problematic USBHUB3.SYS driver version that disabled USB keyboards and mice in WinRE. Microsoft acknowledged this issue on October 17, 2025. In mid-January 2026, Microsoft released recovery updates for Windows 10 and Windows 11, including KB5075039 on January 15, 2026, targeting Windows 10 versions 21H2 and 22H2, but it did not resolve the issue. The re-release of update KB5073933 on March 3, 2026, addressed a critical bug preventing WinRE from starting when the previous update KB5068164 was installed. The installation of KB5073933 is recommended for Windows 10 22H2 users with ESU support to ensure a functional recovery environment.

AppWizard

March 3, 2026

Another Nvidia GPU driver has issues, causing up to 16% drops in performance

Nvidia's driver version 595.71 has introduced performance issues, limiting core clock speeds, voltage levels, and power outputs, resulting in performance drops of up to 16%. The update, released on March 2, aimed to fix problems from the previous version 595.59 but has negatively impacted overclocked graphics cards. For example, an RTX 5090 that previously achieved clock speeds over 3,100MHz now struggles to maintain speeds above 3,000MHz. Benchmark tests showed the older driver (591.74) achieving 171fps compared to 144fps with the new driver. Users are advised to revert to an earlier driver version from the 591 series to restore performance.

Winsage

February 1, 2026

Microsoft confirms that a stack of bad Windows updates is causing boot issues

Windows 11 is facing significant issues following the January Patch Tuesday, particularly with boot failures on commercial devices. These problems are linked to both the January update and a flawed December update, leading to a "UNMOUNTABLEBOOTVOLUME" Blue Screen of Death (BSOD) error. Microsoft has indicated that devices that did not successfully install the December security update are left in an improper state, which can prevent booting when subsequent updates are attempted. While Microsoft is working on a partial solution to prevent further installations that could cause boot failures, this fix will not resolve issues for devices already affected. The company is investigating the causes of these update failures and their consequences.

Winsage

January 21, 2026

Windows 11 update is breaking sleep mode on some PCs — but there’s one trick that might help

Windows 11's January update, KB5074109, has caused a bug affecting sleep mode on certain older PCs, leading to system crashes that require hard reboots. Users have reported that the issue appears only when the update is installed and resolves upon its removal. This problem primarily affects older machines using the S3 sleep state, while newer devices with modern standby features are less impacted. A suggested workaround involves unplugging USB webcams. Additional issues reported include freezing with the Outlook app for POP accounts, shutdown failures for enterprise users, and problems with keyboard and mouse functionality. Microsoft has acknowledged some of these issues and has deployed emergency fixes for certain problems.

Winsage

January 19, 2026

Windows 11 shutdown bug forces Microsoft into out-of-band damage control

Microsoft released an out-of-band update for Windows 11, designated as KB5077797, on January 17 for version 23H2 to address a critical malfunction that prevented some systems from shutting down, restarting, or hibernating after the January Patch Tuesday update. This issue primarily affected systems with System Guard Secure Launch enabled by default. The update also resolves a separate authentication problem with Remote Desktop that caused credential prompts to fail or loop indefinitely. Additionally, Microsoft acknowledged a bug affecting classic Outlook POP account profiles, which has not yet been fixed. Users are urged to install KB5077797 to resolve these issues.

Winsage

January 18, 2026

Windows 11 KB5074109 issues: black screen, freezes Outlook POP, breaks Azure Virtual Desktop, LocalizedResourceName (desktop.ini)

Windows 11 KB5074109 has caused several issues for users, particularly those with Nvidia GPUs, including black screens, Outlook freezing with POP accounts, and problems with File Explorer's desktop.ini settings. Users have reported random black screens and desktop freezes after installing the update, with some finding temporary relief by changing their monitor's DisplayPort mode. Outlook Classic has been problematic, remaining active in the background and freezing shortly after opening, prompting users to terminate the process in Task Manager or uninstall the update. Additionally, the update disrupts Azure Virtual Desktop functionality, leading to sign-in failures and connection issues. Microsoft has acknowledged these problems and is investigating solutions, including a Known Issue Rollback for AVD. The update also breaks the LocalizedResourceName directive in File Explorer, preventing folder name customization. Users can uninstall the update through Settings, but this may expose them to security vulnerabilities.

Winsage

January 14, 2026

Windows 2000 rusts in peace by the sea

A ticket machine at Comboios de Portugal is malfunctioning, running on Windows 2000, which has caused the system to freeze and made card payments unavailable. The issue appears to be related to the software rather than hardware failures. Despite the machine's wear and tear, there is currently no Blue Screen of Death. The situation highlights a decline in rail travel in Portugal as travelers increasingly prefer express bus services.

Winsage

December 17, 2025

Microsoft security updates breaks MSMQ on older Win systems

Microsoft has acknowledged that Message Queuing (MSMQ) may fail on certain Windows 10 devices and older Windows Server versions after the December 2025 Security update. Reported issues include MSMQ queues becoming inactive, IIS sites generating "Insufficient resources to perform operation" errors, and applications failing to write to queues. System logs may show misleading messages about insufficient disk space or memory due to folder permissions and MSMQ's write access requirements. The root cause is linked to changes in the MSMQ security model and NTFS permissions for the C:WindowsSystem32MSMQstorage folder, which now requires write access typically restricted to administrators. This issue primarily affects Windows 10 versions 22H2 and earlier, as well as Windows Server versions 2012 to 2019, with minimal impact on Windows Home or Pro editions. Microsoft recommends contacting support for workarounds, and some users have resolved the issue by uninstalling the update, though this would remove security enhancements. The problems are confined to older operating systems often used by enterprises delaying upgrades.