Skip to content

Windows Computer Use detects Volume as running but exposes no targetable window #55651

Open

Description

@chwtn2014

Problem

Volume by Watermark Technologies is open, signed in and visible, but Windows Computer Use detects it as running with an empty window list. Other desktop applications, including Outlook, Chrome and Teams, expose windows.

Environment recorded on 16 October 2026

  • Desktop app package: OpenAI.Codex 26.1013.3656.0
  • Windows 10 Home 22H2, build 19045.7807
  • Volume file version: 5.6.5.1121
  • Executable: volumeFINANCE.exe
  • Window title: volumeRemote by Watermark Technologies
  • Both ChatGPT.exe and volumeFINANCE.exe: Elevated = No
  • Both apps on the same monitor; 100% scaling; 1920 x 1080 resolution
  • Extended displays configured
  • Both processes observed in the same Windows session
  • Settings > Computer Use > Any App enabled

Steps to reproduce

  1. Open Volume and sign in.
  2. Keep its main window visible and maximised.
  3. Ask Computer Use to find and inspect Volume.
  4. Volume appears as running, but no targetable window is returned.
  5. Launching Volume through Computer Use by its executable path also fails.

Actual result

launched app did not expose a targetable window: Microsoft.AutoGenerated.{E58D6E08-52A5-D93C-16A8-E65D236362F7}

Earlier launch attempt:

computer-use request timed out: launch_app

Restarting both apps, bringing Volume to the foreground and maximising it did not resolve detection.

Expected result

The visible Volume window is available for inspection and interaction.

Diagnostics

In-app feedback session ID: 01a143c1-2ab2-7e51-ab9e-ef78117a9fa0

No-targetable-window error timestamp: 2026-10-16T09:14:20.030Z.
Earlier launch timeout timestamp: 2026-10-16T09:03:27.885Z.

Please advise whether this is a known compatibility issue and which further diagnostics would help. Client documents, email contents, browser links and the full session transcript are omitted.

Activity

  1. added
    bugSomething isn't working
    appIssues related to the Codex desktop app
    windows-osIssues related to Codex on Windows systems
    on Oct 20, 2026
  2. github-actions commented on Oct 20, 2026

    @github-actions
    Contributor

    Potential duplicates detected. Please review them and close your issue if it is a duplicate.

    Powered by Codex Action

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingcomputer-usewindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions