A stubborn blank white rectangle has been appearing on Windows desktops after sign-in or unlock, and it’s traced directly to a scheduled task that Google Chrome plants on your system. If you’ve seen a large, empty white box materialize near the upper-left corner of your screen for a few seconds — or linger indefinitely — you’re not alone. The glitch has been lighting up Reddit and tech forums for weeks, and the fix is simpler than you’d think.
The blank box, unmasked
The phantom window typically measures a few hundred pixels wide and tall, showing nothing but a white surface with a standard title-bar area. It fades after a moment for some users, but for others it refuses to close without killing a specific background process. The timing is consistent: it pops up right after you log into Windows 10 or Windows 11, or when waking a locked machine. Task Manager reveals that the culprit belongs to Google Chrome, even if you don’t have a Chrome window open.
Microsoft’s own support forums and independent testing confirm that the window originates from the GoogleUpdateTaskMachine or GoogleUpdateTaskMachineUA jobs that Chrome’s installer sets up in Windows Task Scheduler. These tasks launch a background updater with a command-line flag (--check-for-update-interval) that, under certain conditions, attempts to draw a hidden confirmation dialog. A race condition or a display-layer bug then leaves that dialog visible as a stark white rectangle.
The issue isn’t brand new — sporadic reports date back to Chrome 109 in early 2023 — but it has surged in recent months as more systems receive Chrome’s automatic updates through the enterprise channel. Both 64-bit and 32-bit installations are affected, and it doesn’t discriminate between Windows editions: Home, Pro, Enterprise, and Education all see it.
Why it happens and who’s at risk
Chrome’s updater normally stays politely in the background. When you log in, Windows fires the scheduled task, and Chrome briefly shows a UI window to request elevation if an update needs admin rights. That window should either disappear or transition into an actual prompt. Instead, the rendering pipeline draws only the container — no text, no buttons — so you get a ghostly blank box.
The glitch does not mean your machine is compromised. No data is leaked, and no malware is involved. It’s purely a cosmetic nuisance, though it can obstruct essential desktop shortcuts or just look alarming.
Who’s most affected?
- Everyday home users who installed Chrome normally and keep automatic updates on. If you rarely sign out or reboot, you might see the box only occasionally.
- Power users and IT admins with machines that join domains or use roaming profiles, because the scheduled task triggers for every user context.
- Developers running multiple Chrome channels (Canary, Dev, Beta) may see the issue compounded, as each channel can install its own updater task.
A quick timeline of the blank-box saga
- Early 2023: Isolated Reddit threads describe a “mystery white box” after reboots. Users initially blame Windows Update or graphics drivers.
- Mid-2023: The finger-pointing shifts to Chrome. A community member digs into Task Scheduler and finds that disabling the GoogleUpdate tasks makes the box vanish.
- Late 2023 – early 2024: Google acknowledges internal reports but doesn’t publish a formal fix. The workaround spreads through word-of-mouth on forums like WindowsForum, Microsoft Community, and r/Windows10.
- Present: The issue persists in Chrome stable 122 and 123, though some users report that a clean reinstall of Chrome or a manual update to the latest build reduces its frequency. Microsoft hasn’t issued a KB article specifically addressing the box, but its support moderators recommend the Task Scheduler workaround in scattered forum replies.
How to kill the blank box — step by step
The most reliable fix is to disable the problematic scheduled task. This won’t break Chrome’s ability to update, because Chrome itself has a separate update mechanism that runs within the browser. Here’s how to stop the phantom rectangle.
Method 1: Disable the task via Task Scheduler (recommended)
- Press Windows Key + R, type
taskschd.msc, and press Enter. - In the left pane, expand Task Scheduler Library, then click on the Google folder (if you don’t see a Google folder, skip to Method 2).
- Look for a task named GoogleUpdateTaskMachineUA or GoogleUpdateTaskMachine (you may have both, or just the first).
- Right-click each one and select Disable.
- Reboot or just sign out and back in — the white box should be gone.
Method 2: If you can’t find the Google folder
Some installations tuck the tasks elsewhere. In the same Task Scheduler Library, scroll through the list of tasks in the top-center pane rather than relying on the folder tree. Look for any tasks whose names start with “GoogleUpdate.” Right-click and disable them.
Method 3: Command-line power move
If you’re comfortable with the terminal, run the following commands in an elevated PowerShell or Command Prompt:
schtasks /Change /TN "Google\GoogleUpdateTaskMachineUA" /Disable
schtasks /Change /TN "Google\GoogleUpdateTaskMachine" /Disable
If the task names differ, run schtasks /query /fo LIST and search for GoogleUpdate to get the exact names.
Method 4: Nuke the tasks entirely (not recommended for most users)
Deleting the tasks instead of disabling them prevents any future re-enablement, but if Chrome’s updater recreates them during a reinstall or repair, you’ll have to repeat the process. To delete:
- In Task Scheduler, right-click the task and choose Delete, or use schtasks /Delete /TN "TaskName" /F.
Method 5: Reinstall Chrome with different settings
Some users report that installing Chrome in a non-default directory (e.g., C:\Users\Public\Desktop\Chrome) makes the updater skip the machine-wide task and use a per-user mechanism, sidestepping the bug. This is a niche option but worth trying if you want a set-it-and-forget-it solution.
What if the box refuses to die?
If the white rectangle still appears after disabling the tasks, double-check through Task Manager that a rogue GoogleUpdate.exe isn’t already running. Hit Ctrl+Shift+Esc, switch to the Details tab, and sort by name. Kill any process named GoogleUpdate.exe or GoogleUpdateSetup.exe. That should clear the box immediately. Then verify the tasks are actually disabled — sometimes a pending system restart for Windows Update or a group policy refresh can re-enable them.
For enterprise environments, a Group Policy Object (GPO) that pushes the task disablement to all workstations is the cleanest way to squash the issue at scale. IT admins can also manage Chrome updates through Group Policy templates so that the scheduled task never becomes necessary.
Beyond the fix: Preventing future nonsense
Google is aware of the cosmetic bug, but there’s no official timeline for a permanent patch. In the meantime, you can keep Chrome’s own update channel robust:
- Open Chrome, click the three-dot menu › Help › About Google Chrome. Force a manual check and install any pending updates. When Chrome updates itself from within the browser, it often replaces the scheduled task with a corrected version.
- If you installed Chrome via an MSI package provided by your IT department, ask them to push the latest MSI. Google’s enterprise installer sometimes doesn’t refresh the scheduled tasks after the initial deployment.
The bottom line
The blank white box is a quirky intersection of Windows’ Task Scheduler and Chrome’s silent updater. It’s not dangerous, but it’s annoying enough to warrant a five-minute fix. Disabling the GoogleUpdate tasks is a surgical solution that leaves everything else working exactly as before. Until Google ships a bulletproof updater that doesn’t accidentally paint empty windows on your desktop, this task-scheduler tweak is the best guard against the ghost box.