Compare from Nothing and Block the Screen: What is the Mysterious White Box on Windows 11
Compare from Nothing and Block the Screen: What is the Mysterious White Box on Windows 11
A growing group of Windows 10 and Windows 11 users has reported the periodic appearance of a blank white window, devoid of content and visible controls, that occupies a significant portion of the screen in the upper left corner. The box appears for a few seconds, typically right after powering on the PC or unlocking from the login screen, and in the meantime prevents interaction with whatever is underneath.
Reports are coming from a wide variety of hardware configurations, which has led the community to quickly rule out a problem related to specific video drivers. Attention has instead shifted to a common element across all affected machines: the presence of Google Chrome installed as the default browser or otherwise active in the background.
The suspect is called RunPlatformExperienceHelperOnUnlock.
Digging into the Windows Task Scheduler, some users have identified a folder called GoogleUserPEH, which contains a task named RunPlatformExperienceHelperOnUnlock. This is a background component related to Chrome, designed to manage the interactions between the browser and external elements like extensions, plugins, and automatic update processes.
The timing coincidence between the execution of this task (triggered exactly at system unlock) and the appearance of the white box has convinced much of the community that the connection is not coincidental, as reported by Neowin. However, this remains a hypothesis based on empirical observations, not on an official technical analysis of the involved code.
The workaround circulating among users is simple to apply, at least on paper. Open the Task Scheduler, navigate to the GoogleUserPEH folder in the task library tree, select RunPlatformExperienceHelperOnUnlock, and choose the Disable option. Several users report that after this modification, the white box ceases to appear.
However, the situation is not without its gray areas. Google has not publicly confirmed that this task is the cause of the defect, and Microsoft has not issued any official notice linking the symptom to Chrome. Disabling a scheduled task related to the browser without a certified technical diagnosis remains a remedy to be approached with caution, more of a temporary patch than a guaranteed solution.
This is not the first time that abnormal behavior in Windows has been traced back to service components installed by Chrome on the operating system. The combination of a poorly documented scheduled task and an intermittent graphic bug, difficult to reproduce on command, makes it plausible that more time is needed before a definitive explanation is available, whether it’s from Google or Microsoft.