Windows 11 search function slow to display results on initial boot.
The problem: When trying to search for an app for the first time since boot-up, the results are blank and takes around 20 seconds to be displayed. But the function has actually found the app I am searching for and its only the displaying part that is lagging because I can see the app's name being auto-completed and the app actually launches if I press enter at this stage. I remember this issue starting only recently, as in around 3-4 months ago if I am remembering it correct. I figured its the usual bug which will be fixed in the upcoming or the update after that but this has persisted for long enough for me to make a post in this forum. A video of what I am talking about can be found https://imgur.com/a/Zc6Q85X I am on build 26100.7462 for reference.
Windows 11 24H2/25H2 System Freeze After January 2026 Updates – Lenovo ThinkPad G2
Dear Microsoft Support Team, We would like to raise a high-priority technical support case regarding a stability issue observed after installing the January 2026 cumulative updates on our Windows 11 devices. Environment Details: Device Model: Lenovo ThinkPad G2 (multiple units) OS Versions: Windows 11 24H2 and 25H2 Update Installed: January 2026 Patch Tuesday cumulative update (KB number can be provided) Deployment Method: WSUS / Intune / Windows Update (specify accordingly) BIOS Version: (Installed Latest available from Lenovo) Issue Description: After installing the January 2026 cumulative updates, devices intermittently experience a complete system freeze. The system becomes fully unresponsive: Mouse and keyboard input stop responding No BSOD is displayed Task Manager cannot be opened System recovery is only possible via hard reboot (power button) Frequency: The issue occurs randomly, both during active use and idle state. Multiple users across our environment are impacted. Troubleshooting Performed: Reinstalled OEM-certified Lenovo display drivers Disabled Fast Startup Ran SFC and DISM health checks (no integrity violations) Updated BIOS to latest version Setting power idle mode, then work normally Request: - Please confirm whether this is a known global issue under investigation. - Advise if any hotfix, Known Issue Rollback (KIR), or registry-based mitigation is available. - Provide guidance on additional diagnostic logging required at kernel or driver level. - Confirm whether crash dump analysis is recommended for this scenario. We are prepared to provide additional diagnostic logs, memory dumps, or reproduction steps upon request. Kindly treat this as a priority case due to multi-user impact in a production environment. Thank you for your support. #Windows11, #Windows 11 24H2, Windows Update, Cumulative Update, System Freeze, Lenovo ThinkPad, Display Driver, Enterprise
Windows Hello Interrupts Live Presentations and Demos — A Clear Case for Presentation Mode
I rely on my Windows device during my two‑hour classes to deliver presentations, demos, and instruction, and it’s essential that the screen remain awake and unlocked throughout. Despite configuring all relevant power and presence settings, Windows Hello still disrupts the class by forcing the device to the lock screen — and the setting that should prevent this is greyed out and unavailable. Context I teach two‑hour classes and use my Windows 11 laptop to present materials, run demos, and guide discussions. During class, the device must remain: awake unlocked connected to the projector responsive However, the laptop repeatedly reverted to the lock screen mid‑lecture, interrupting the presentation and forcing re‑authentication in front of students. What I Tried I addressed every obvious cause: Power Plans I created custom power plans for the classroom and office, switched via script, and disabled: display timeout sleep lid‑close actions Modern Standby transitions Presence Sensing I permanently disabled Presence Sensing, which was turning off the display when I stepped away from the lectern. These changes solved most issues — except Windows Hello. The Remaining Problem Even with all power settings configured, Windows Hello still timed out and returned to the lock screen. The setting “If you’ve been away, when should Windows require you to sign in again?” was permanently greyed outand set to Every time. This meant Windows Hello was overriding all power plan behavior. Root Cause After extensive troubleshooting, I discovered that: enabling Windows Hello combined with using a Microsoft account, OneDrive, Teams, or Office 365 causes Windows to silently provision Windows Hello for Business (WHfB) even on personal devices. Once WHfB is active: idle‑lock becomes mandatory, the timeout setting is disabled, and the UI no longer reflects the system's true state. This occurs even when: the device is not Azure AD joined, the device is not Intune‑managed, all work accounts are disconnected, and Hello is used only for convenience, not for enterprise identity. In short, the OS presents idle‑timeout as a user preference, but silently removes that choice as soon as Windows Hello is active. Impact on Teaching and Presenting Teaching and presenting require the device to: stay unlocked, keep the display active, avoid interruptions, ignore Presence Sensing, and maintain stable external display output. Before Modern Standby and WHfB, Windows supported this through Presentation Mode, which temporarily suspended lock and sleep behavior. Modern Windows removed Presentation Mode; there is no equivalent system‑level override. The result is: screens locking mid‑lecture, forced PIN/biometric prompts, display dropouts, Presence Sensing interruptions, and disrupted instruction. This is not a security improvement — it’s a workflow regression. The Architectural Gap There is currently no supported way to: use Windows Hello, and use Microsoft cloud services, and control idle‑lock behavior. The OS assumes that anyone using Hello must want enterprise‑grade identity protection, even on personal devices and even in teaching, presenting, or demonstrating scenarios. Why a System‑Level Mode Would Improve Security Right now, users must attempt to manage: power plans display timeouts sleep settings Presence Sensing Windows Hello behavior Modern Standby quirks This patchwork approach is error‑prone and often leads users to disable security features permanently. A system‑level mode would: make the behavior explicit, make it temporary, ensure the device returns to secure defaults afterward, reduce accidental misconfiguration, and provide predictable, intentional control. This strengthens security by replacing ad‑hoc workarounds with a single, reversible, auditable mode. Proposed Solution: A Modern Presentation Mode Windows needs a system‑level Presentation Mode — ideally a Quick Settings toggle (like Airplane Mode) — that: temporarily suspends WHfB idle‑lock, temporarily suspends Presence Sensing, temporarily suspends Modern Standby, prevents display‑off and lockscreen activation, maintains stable external display output, and restores all prior settings when turned off. This would support teaching, presenting, training, and demo workflows that Windows has historically handled well. Conclusion Windows Hello for Business assumes it can automatically determine a device's security context and defaults to an enterprise‑first posture. But many real‑world scenarios — including teaching, presenting, and live demonstrations — do not fit that model. In these cases, WHfB’s assumptions break down. Without a system‑level override, users have no way to signal that the device must remain awake and unlocked for a limited, intentional period. A modern Presentation Mode would provide that missing signal. It would honor WHfB’s security objectives while giving users a deliberate, temporary way to suspend idle‑lock and related behaviors during time‑bounded workflows. Just as importantly, it would ensure the device returns to its standard security posture afterward, reducing the need for ad‑hoc workarounds or permanent configuration changes. I welcome feedback from Microsoft PMs or MVPs on whether a modern Presentation Mode could be considered for future Windows releases.I have taken notice that my taskbar manager is not responding correctly.
Its been a month now that I have noticed many things within my computer system. The task manager is one of them. The apps that I have assigned to it are not acting correctly. Ive tried to look into it but I keep on getting no luck. Im thinking of just using the Desktop solely. Can anyone give me assistance on fixing my task manager?
reverse performance while charging and not charging
when i play games with charging my laptop, normally it would boost my performance a lot, but idk why this time it got reversed, so i got a problem in my laptop performance in a few games and im randomly check with turn off my charger to see the result, and my fps just drastically flew high until 100's. and when got charged again, it dropped to 60 ish, like the fps got capped when charged, and not capped when not charged.
After updating to the new Windows 11 25H2 version, disk performance has decreased.
After installing these two updates, SSD sequential write speed dropped from 6000 MB/s to 4000 MB/s, and 4K random read/write speeds also decreased significantly. Is this a widespread issue? How can it be mitigated or rolled back?Computer reboot after waking up from sleep mode
Please help me out, I recently got this computer and the only problem I've had with it is that upon waking up from Sleep mode, it will force restart after about 10-15 seconds. This only occurs after the computer wakes up from Sleep mode. Hibernate mode does not have this issue. AMD Ryzen 7 7700 8-Core Processor 32GB RAM NVIDIA GeForce RTX 5070 I have tried changing various things in my settings, including the virtual memory size (which i changed back to the automatic settings after it didn't make a difference). The Reliability Monitor shows this as a "critical event" but all the description says is "The previous system shutdown at 2:30:41 PM on 2/5/2026 was unexpected." The 'shutdown' is just the time the computer entered Sleep mode. I am at a total loss as to what I should do, and am trying to see if I can fix whatever the problem is myself before bringing it in. (Which I'll do if it comes to that)