Windows users began noticing an odd glitch in early July 2026 — a large, blank white rectangle appearing for a few seconds near the top-left corner of the desktop after logging in or unlocking their PCs. The issue affects both Windows 10 and Windows 11, and reports quickly piled up on Reddit, Microsoft community forums, and tech outlets like Neowin. The culprit, according to multiple user investigations, is a Google Chrome scheduled task that launches a hidden browser instance with a malformed window, leaving users baffled and searching for a fix.

What Actually Happened

The phantom window is not a sign of malware or a system corruption. It's a side effect of a Chrome update — specifically, Chrome version 138.0.6998.89 and its beta/dev channel equivalents — that altered how the browser handles background tasks. The affected component is ChromeElevationService, a legitimate scheduled task that runs after user logon to check for browser updates or manage Chrome-related services. Normally, this task runs silently, but a bug introduced in the July 7–10 update cycle causes a blank chrome.exe window to be drawn on screen with no content.

Users describe the box as roughly 400×600 pixels, always in the upper-left corner, appearing for 1–3 seconds before vanishing. It does not accept clicks, and it disappears on its own. The issue is strictly cosmetic — no data loss, no performance hit — but unsettling enough to trigger support calls and IT tickets in enterprise environments.

Microsoft has not issued an official statement, but internal telemetry confirms the spike in reports starting July 8, 2026. The company is said to be working with Google on a patch, but in the interim, the community has reverse-engineered the cause and produced reliable workarounds.

What It Means for You

For most home users, the blank box is an annoyance at worst. If you unlock your computer a few times a day, you'll see it briefly — like a ghost window that comes and goes. It doesn't indicate your system is compromised, and it doesn't interfere with any open applications. However, the sudden appearance of an uninvited window can feel intrusive, especially in a security-conscious environment.

For IT administrators, the impact is greater. In managed fleets, users might panic and file helpdesk tickets, wasting time. Worse, in locked-down virtual desktop or kiosk scenarios, the flash of a blank window could violate the seamless experience expected. Some admins have reported that the window briefly steals focus, which could disrupt workflows that rely on focus-sensitive automations or touch-based input.

Developers and power users who run multiple browsers or custom launchers may also be affected indirectly. The scheduled task runs regardless of whether Chrome is set as the default browser, so even Edge or Firefox loyalists will see the box if Chrome is installed. That makes it a system-wide annoyance, not just a Chrome quirk.

How We Got Here

Google's Chrome browser has long used scheduled tasks for background updates and maintenance. On Windows, the Task Scheduler manages these — you'll find several Google tasks in the Task Scheduler Library under both Google and GoogleSystem paths. The ChromeElevationService task was introduced in Chrome 134 to handle secure elevation requests for things like password manager integration and online payment authentication. It runs at every user logon by default.

In the July 2026 stable release (version 138.0.6998.89), Google modified the task to use a new command-line flag: --background-service-window. This flag was intended to create a hidden window necessary for Chrome's background service process management — a common Windows API technique. But a missing --silent-launch or incorrect window style attribute causes the window to briefly render as a visible, blank rectangle before the task destroys it.

The bug made its way through Chrome's dev and beta channels in late June, but with the rapid rollout of the stable update — pushed to over 60% of Windows users within the first week — it became a widespread issue overnight. Reddit threads like r/Windows11 and r/sysadmin lit up with users sharing screenshots and suspecting anything from a dying GPU to a rootkit.

Interestingly, this isn't the first time Chrome's task scheduler entries have caused visible oddities. In 2023, a similar scheduled task left a command prompt window flashing on login, which was quickly fixed by a subsequent update. Google's reliance on low-level Windows integrations has occasionally brushed against user-facing side effects, and this is the latest example.

What to Do Now

The good news: you can stop the blank box immediately, without waiting for an official patch. Here are three methods, from simplest to most comprehensive.

Option 1: Disable the Offending Scheduled Task (Home Users)

This ends the ghost window without affecting Chrome's core update mechanism. Other tasks will still keep Chrome updated.

  1. Press Win + R, type taskschd.msc, and press Enter to open Task Scheduler.
  2. In the left pane, expand Task Scheduler Library > GoogleSystem.
  3. In the middle pane, right-click ChromeElevationService and select Disable.
    - If you don't see it, look under the plain Google folder or Google-Browser-Scheduled-Tasks path.
  4. Close Task Scheduler. The blank box will no longer appear on next login.

For multiple user accounts on a single PC, you may need to disable the task for each user who sees the issue. The task runs under the logged-in user's context, so if you have fast user switching, each account will need the fix applied while logged into that account.

Option 2: Update Chrome to a Patched Version (When Available)

Google is working on a fix. Once a new Chrome version is released (expected in the 138.0.7000.x range), the issue should resolve automatically after updating. To force an update:

  1. Open Chrome.
  2. Click the three-dot menu > Help > About Google Chrome.
  3. Chrome will check for updates and install any available version.
  4. Relaunch the browser.

Check the Chrome release blog or Neowin's coverage for confirmation that the blank-box bug is fixed before you re-enable the scheduled task.

Option 3: Modify the Task Command (Advanced Users)

For users comfortable with editing scheduled tasks, you can fix the window without disabling updates:

  1. Find the ChromeElevationService task in Task Scheduler (same path as Option 1).
  2. Right-click and choose Properties.
  3. Go to the Actions tab, select the action that launches chrome.exe, and click Edit.
  4. In the Add arguments field, append a space and --silent-launch immediately after the existing arguments.
    - Example: If the current arguments are --background-service-window --some-flag, change it to --background-service-window --silent-launch --some-flag.
  5. Click OK, then OK again. You may need administrator privileges to save.

This tells Chrome to launch the window fully hidden, which mimics the intended behavior without the visual flash. Test by locking and unlocking your PC.

For IT Administrators

Deploy a fix across your fleet using Group Policy Preferences or your RMM tool. The PowerShell snippet below disables the task for the current user; you can wrap it in a logon script or configuration manager baseline.

Disable-ScheduledTask -TaskName "ChromeElevationService" -TaskPath "\GoogleSystem\"

If the task is located elsewhere, adjust the -TaskPath parameter. Test on a pilot group first. Note that this only disables the task for the user running the script; for shared devices, you might need to loop through user profiles or run in the user context.

Outlook

Google is expected to release a Chrome stable channel update within days, likely bumping the version to 138.0.7001.x. Microsoft may also issue a Known Issue Rollback (KIR) for the affected Windows 10 22H2 and Windows 11 23H2/24H2 builds, but a Chrome-side fix is more probable since the root cause is in the Chrome executable, not the Windows compositor.

In the long run, this event highlights how tightly integrated browsers have become with the operating system — and how a tiny bug in a background task can ripple across millions of desktops. For now, the community-driven workarounds are safe and effective, letting you reclaim your clean logon experience without waiting for a patch cycle.