COPILOT Send Button Grayed Out After Update

Kbore 0 Reputation points
2026-11-14T03:52:01.1733333+00:00

Is there a known bug in the newest update Copilot APP version 157.0.4341.60? The 157.0.4341.60 version will not submit queries on my WIN11 Home laptop- the UI is fully functional except for the "send" function, including "Send Feedback". Details, including versions below:

COPILOT DESKTOP APP FAILURE SUMMARY Date: November 13, 2026

SYSTEM

  • Windows 11 Version 10.0.26300 Build 26300
  • Microsoft account successfully signed in
  • Edge Copilot functions normally
  • Problem began immediately after recent Copilot desktop application update

SYMPTOMS

Copilot desktop application launches normally.

The following features do NOT work:

  • Send message
  • New Chat
  • Feedback submission

The following features DO work:

  • Sign-in recognition
  • Account management access
  • Chat history synchronization
  • Display of existing conversations
  • Text entry in prompt box
  • Formatting toolbar
  • Source selection menu

OBSERVATIONS

  1. User can type normally in the chat input field.
  2. Text can be selected with Ctrl+A.
  3. Input field correctly detects empty/non-empty state:
    • Empty field shows microphone icon.
      • Non-empty field shows Send arrow.
      1. Send arrow appears but remains permanently gray (disabled).
      2. Clicking New Chat produces no response.
      3. Clicking Feedback also fails to transmit.
      4. Existing conversations created in Edge Copilot appear in the desktop Copilot application's chat list, proving synchronization is functioning.

ACCOUNT TESTS

  • User account is recognized.
  • View Account works.
  • Microsoft Account page opens successfully.
  • Account page displays correct user information.
  • Microsoft identifies account as SIGNED IN.
  • No authentication errors observed.

APPLICATION IDENTIFICATION

Executable location:

C:\Program Files (x86)\Microsoft\Copilot\Application\copilotapp.exe

PowerShell:

Get-Process copilotapp | Select-Object -First 1 Path

Result:

C:\Program Files (x86)\Microsoft\Copilot\Application\copilotapp.exe

VERSION INFORMATION

Application Version: 157.0.4341.60

Service Version: bizchat.20261111.23.2

Environment: Production

PowerShell verification:

(Get-Item "C:\Program Files (x86)\Microsoft\Copilot\Application\copilotapp.exe").VersionInfo | Select ProductVersion,FileVersion

Result:

ProductVersion 157.0.4341.60 FileVersion 157.0.4341.60

PROCESS VERIFICATION

PowerShell:

Get-Process | Where-Object {$_.ProcessName -match "Copilot|Office|WebView|msedge"} | Select ProcessName

Observed:

  • Multiple copilotapp processes
  • copilotapphost process
  • Multiple msedgewebview2 processes

This indicates that the Copilot application and WebView2 runtime are running.

APPX INVESTIGATION

PowerShell:

Get-AppxPackage Microsoft.Copilot | Select Name, PackageFullName

Result: No results returned.

Further investigation showed the desktop Copilot application is not installed as a traditional AppX package on this system.

WORKING THEORY

The application appears capable of:

  • Reading/synchronizing conversation data
  • Displaying existing chat history
  • Recognizing user identity

The application appears unable to:

  • Create new conversations
  • Send messages
  • Submit feedback

Evidence suggests a failure in the desktop Copilot client's write/create functionality rather than:

  • Internet connectivity
  • Microsoft account authentication
  • Text input handling
  • Keyboard operation
  • WebView2 installation
  • General Windows functionality

STATUS

Problem remains unresolved.

Most likely causes:

  1. Regression/bug introduced in Copilot version 157.0.4341.60
  2. Corrupted local Copilot application state
  3. Client-side Copilot application defect specific to this installation/profile

Edge Copilot remains fully functional while desktop Copilot cannot create or send content.

 

COPILOT DESKTOP APP FAILURE SUMMARY Date: November 13, 2026

SYSTEM

  • Windows 11
  • Microsoft account successfully signed in
  • Edge Copilot functions normally
  • Problem began immediately after recent Copilot desktop application update

SYMPTOMS

Copilot desktop application launches normally.

The following features do NOT work:

  • Send message
  • New Chat
  • Feedback submission

The following features DO work:

  • Sign-in recognition
  • Account management access
  • Chat history synchronization
  • Display of existing conversations
  • Text entry in prompt box
  • Formatting toolbar
  • Source selection menu

OBSERVATIONS

  1. User can type normally in the chat input field.
  2. Text can be selected with Ctrl+A.
  3. Input field correctly detects empty/non-empty state:
    • Empty field shows microphone icon.
      • Non-empty field shows Send arrow.
      1. Send arrow appears but remains permanently gray (disabled).
      2. Clicking New Chat produces no response.
      3. Clicking Feedback also fails to transmit.
      4. Existing conversations created in Edge Copilot appear in the desktop Copilot application's chat list, proving synchronization is functioning.

ACCOUNT TESTS

  • User account is recognized.
  • View Account works.
  • Microsoft Account page opens successfully.
  • Account page displays correct user information.
  • Microsoft identifies account as SIGNED IN.
  • No authentication errors observed.

APPLICATION IDENTIFICATION

Executable location:

C:\Program Files (x86)\Microsoft\Copilot\Application\copilotapp.exe

PowerShell:

Get-Process copilotapp | Select-Object -First 1 Path

Result:

C:\Program Files (x86)\Microsoft\Copilot\Application\copilotapp.exe

VERSION INFORMATION

Application Version: 157.0.4341.60

Service Version: bizchat.20261111.23.2

Environment: Production

PowerShell verification:

(Get-Item "C:\Program Files (x86)\Microsoft\Copilot\Application\copilotapp.exe").VersionInfo | Select ProductVersion,FileVersion

Result:

ProductVersion 157.0.4341.60 FileVersion 157.0.4341.60

PROCESS VERIFICATION

PowerShell:

Get-Process | Where-Object {$_.ProcessName -match "Copilot|Office|WebView|msedge"} | Select ProcessName

Observed:

  • Multiple copilotapp processes
  • copilotapphost process
  • Multiple msedgewebview2 processes

This indicates that the Copilot application and WebView2 runtime are running.

APPX INVESTIGATION

PowerShell:

Get-AppxPackage Microsoft.Copilot | Select Name, PackageFullName

Result: No results returned.

Further investigation showed the desktop Copilot application is not installed as a traditional AppX package on this system.

WORKING THEORY

The application appears capable of:

  • Reading/synchronizing conversation data
  • Displaying existing chat history
  • Recognizing user identity

The application appears unable to:

  • Create new conversations
  • Send messages
  • Submit feedback

Evidence suggests a failure in the desktop Copilot client's write/create functionality rather than:

  • Internet connectivity
  • Microsoft account authentication
  • Text input handling
  • Keyboard operation
  • WebView2 installation
  • General Windows functionality

STATUS

Problem remains unresolved.

Most likely causes:

  1. Regression/bug introduced in Copilot version 157.0.4341.60
  2. Corrupted local Copilot application state
  3. Client-side Copilot application defect specific to this installation/profile

Edge Copilot remains fully functional while desktop Copilot cannot send content.

 

Microsoft Copilot | Windows Copilot | App
0 comments

2 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Kbore 0 Reputation points
    2026-11-14T03:56:25.0066667+00:00

    I should add that REPAIR, RESET, UNINSTALL, and reinstall of the Copilot APP have been done several times, and the problem persists

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-11-14T03:53:01.1433333+00:00

    There is no public Microsoft advisory confirming Copilot version 157.0.4341.60 as a known gray-Send-button issue, so the most appropriate next action is to repair or reset its local state and, if that fails, perform a clean uninstall and reinstall.

    Similar Copilot send/UI failures have been reported after updates, but the reports do not match your exact build and symptoms closely enough to establish a version-wide regression.^1^

    1. Repair or reset Copilot if those options are available

    Your Get-AppxPackage result is expected to be unhelpful for an EXE-installed application; use Installed apps instead.

    1. Close Copilot completely, including its notification-area instance if present.
    2. Open Settings → Apps → Installed apps.
    3. Find Microsoft Copilot or Copilot and select … → Advanced options.
    4. If Repair is available, select it and test Copilot.
    5. If Repair does not resolve it, select Reset, reopen Copilot, and sign in again.

    Windows only displays Repair, Reset, or Advanced options when the application’s installer supports them.^2^

    Reset warning: Reset removes local application settings and cached state. Your server-synchronized chat history should reappear after sign-in, but preserve any unsynchronized local material first.

    If Advanced options, Repair, or Reset is absent, proceed directly to reinstalling.

    2. Uninstall and reinstall the supported Copilot app

    1. Go to Settings → Apps → Installed apps.
    2. Find Copilot, select … → Uninstall, and complete removal.
    3. Restart Windows. This ensures the existing copilotapp, copilotapphost, and WebView2 child processes are no longer holding files or cached state.
    4. Reinstall Copilot from the Microsoft Store.
    5. Sign in with the same personal Microsoft account.
    6. Before changing any settings, test these three operations:
      • Create New Chat.
      • Enter a plain-text prompt and select Send.
      • Open the profile menu and try Send feedback.

    Microsoft documents this uninstall path and Microsoft Store reinstall method specifically for Copilot on Windows.^3^

    After reinstalling, verify that the executable version changed—or that the same version now works with newly created local state:

    $process = Get-Process copilotapp -ErrorAction Stop |
    Select-Object -First 1

$path = $process.Path
(Get-Item $path).VersionInfo |
    Select-Object ProductVersion, FileVersion

    3. If a clean reinstall still fails

    That result would favor an application-build or service/client compatibility defect over corrupted local state, particularly because Edge Copilot works with the same account.

    Report it through Feedback Hub, rather than Copilot’s nonfunctional feedback control:

    1. Reproduce the disabled Send button.
    2. Press Windows key + F.
    3. Use a title such as:
      Copilot 157.0.4341.60: Send, New Chat, and Feedback disabled
    4. Include:
      • Copilot application and service versions
      • Windows full build from winver
      • Executable path
      • Confirmation that Edge Copilot works with the same account
      • Confirmation that repair/reset or clean reinstall did not resolve it
    5. Select Recreate my problem, start recording, reproduce New Chat and disabled Send, then stop recording and submit.
    6. If matching feedback already exists, link to or upvote it instead of creating a duplicate.

    Feedback Hub supports screenshots, diagnostic recordings, attachments, similar-report matching, and marking a problem as blocking.^4^

    Your current evidence does not establish an authentication, keyboard, or missing-WebView2 problem, so repeating those checks is unlikely to discriminate further. Continue using Edge Copilot as the temporary workaround while the desktop report is investigated.

    References

    1. keyboard enter key for "submit message" action stopped working in copilot
    2. [Windows 11](https://support.microsoft.com/windows/apps/repair-apps-and-programs-in-windows#summary)
    3. Welcome to Copilot on Windows
    4. Send feedback to Microsoft with the Feedback Hub app | Microsoft Support
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.