reopening

Winsage
January 18, 2026
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.
AppWizard
December 1, 2025
YouTube users are experiencing issues with an advertisement for the "AR Drawing" app by Hypernova Limited, which fails to load and forces viewers to exit and restart their videos. Complaints have surged, particularly on Reddit, with users reporting the ad reappearing frequently and buffering indefinitely. This problem primarily affects Android users and is not indicative of a broader issue with YouTube's ad system. Users have tried clearing their cache and restarting devices without success, and YouTube has not yet acknowledged the problem. The app is still in development and promotes early access for feedback.
AppWizard
December 1, 2025
In late November 2025, Google Pixel users reported a "ghost app" issue where apps reopen without user intervention, affecting multiple models from Pixel 9 to Pixel 10. This problem has been linked to recent software updates and has been described as a systemic glitch. Users also reported "ghost touches" on older models like the Pixel 7, where screens register inputs without contact. Complaints include apps struggling to stay closed, overheating, and inconsistent performance, with theories suggesting bugs in Android 16 and issues with the Pixel's Tensor chips. A botched privacy update may have exacerbated the problem by throttling background processes. The ongoing reliability challenges have led to a significant erosion of user trust in the Pixel brand.
AppWizard
November 29, 2025
Google Pixel users are experiencing a glitch where closed apps, such as Instagram, unexpectedly reopen when switching to another application. This issue has persisted for six months and affects devices like the Pixel 8 and Pixel 10 Pro XL. Users have noted that it disrupts app-switching, and a suggested workaround is to pause briefly before selecting another app. Additionally, Pixel 10 users have reported significant Wi-Fi connectivity problems following an AirDrop-Quick Share update, with a temporary solution being to uninstall the Quick Share extension or use Bluetooth for file transfers. Furthermore, Pixel 10 users are facing issues with unresponsive or lagging speakerphone functionality in the Phone app, which has been ongoing since May and also affects earlier Pixel 9 models. Google has deemed this speakerphone issue as "won't fix (Infeasible)."
Winsage
November 13, 2025
Microsoft has released the Windows 11 November 2025 Update (Build 26200.7171/26100.7171 or newer), which fixes an issue where the Task Manager did not close properly when the Close (X) button was clicked. This problem, first observed after the October optional update (KB5067036), caused multiple invisible instances of the Task Manager to accumulate, consuming 20-25 MB of RAM and 0 to 1.5% of CPU resources, leading to performance degradation. Microsoft confirmed that the October update inadvertently caused this issue while attempting to fix a grouping problem within the Task Manager. The November update (KB5068861) resolves the bug, restoring the expected functionality of the Task Manager. Users can check for lingering instances by opening the Task Manager and observing if multiple instances appear after closing and reopening it.
Winsage
November 3, 2025
Microsoft has acknowledged an issue affecting Windows 11 users after installing the optional October 2025 update (KB5067036), where the Task Manager does not fully close when the "Close" button is used, resulting in multiple instances of taskmgr.exe running in the background. This can lead to performance degradation, including system stuttering and CPU hangs. A temporary workaround involves manually terminating each Task Manager process or using the Command Prompt with the command: taskkill.exe /im taskmgr.exe /f. The KB5067036 update also introduced enhancements like an updated Start Menu and restored functionality to the Windows 11 Media Creation Tool, while addressing specific update errors.
Winsage
October 31, 2025
Microsoft's latest Windows 11 update (KB5067036) has caused a glitch resulting in multiple instances of Task Manager being spawned, consuming system resources. Users experience this issue when they close and reopen Task Manager, leading to an increasing number of active processes. The cause of the glitch is unclear, but it may relate to a fix intended to improve Task Manager's functionality. Microsoft has not acknowledged this issue, stating they are unaware of any problems with the update. Dave Plummer, the original architect of Task Manager, commented on the situation humorously, noting the persistence of older code. It is unlikely that Microsoft will release an immediate fix as the issue affects only a subset of users.
Winsage
October 31, 2025
The latest preview update for Windows 11 has introduced a glitch in Task Manager, preventing it from closing properly and resulting in multiple background instances that consume system resources. This issue arose after the October 2025 optional update (Build 26200.7019 / 26100.7019), causing Task Manager to remain active in the background and launch additional instances upon reopening. While not affecting every user, many have reported encountering this bug. Users are advised to avoid using the “X” button to close Task Manager and instead use alternative methods such as ending the task from within Task Manager, restarting Windows Explorer, or using Command Prompt or PowerShell to force-close Task Manager instances. Microsoft is expected to address this issue in a future update. Users may also consider uninstalling the October 2025 update if the problem significantly impacts performance.
Search