Share via

GitHub Copilot Authentication Bug: "Continue with undefined" in VS Code 1.108.1

Gupta, Shubham 5 Reputation points
2026-02-28T09:58:01.1533333+00:00

Hi Team,

I am experiencing a persistent authentication failure in VS Code where the login interface displays "undefined" instead of the provider names (GitHub, Google, etc.).

The Issue:

When clicking the "Sign in to use AI Features" button, all authentication options appear as "Continue with undefined". Attempting to proceed triggers a pop-up stating: "Failed to sign in to undefined. Would you like to try again?".

Screenshots:

Image

(Shows the "undefined" buttons)

Image

(Shows the "Failed to sign in to undefined" error)

Environment:

  • VS Code Version: 1.108.1
  • GitHub Copilot Version: 1.388.0
  • OS: Windows 11

Steps Taken (That Failed to Resolve):

  • Full reinstall of VS Code (including deleting %AppData%\Code and %LocalAppData%\Programs\Microsoft VS Code).
  • Manually deleting the %AppData%\Code\User\globalStorage\vscode.github-authentication folder.
  • Manually deleting the .github-copilot folder in the User profile.
  • Forcing the provider in settings.json via "github.copilot.advanced": { "authProvider": "github" }.
  • Disabling and re-enabling the built-in GitHub Authentication extension.

It appears the extension is failing to resolve the provider name from the authentication service. Any guidance on how to force the "GitHub" provider would be appreciated.

Developer technologies | Visual Studio | Extensions

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Gupta, Shubham 5 Reputation points
    2026-03-02T16:29:00.6233333+00:00

    Thanks, but the troubleshoot didn't help. I followed all steps.

    One thing is I don't have "Microsoft Edge WebView2 Runtime" installed on my system.

    1 person found this answer helpful.
  2. Gupta, Shubham 5 Reputation points
    2026-03-09T09:08:53.16+00:00

    Resolution: The issue was caused by using the version available in the Corporate Software Center. After uninstalling it and installing the latest version directly from the vendor website, the issue was resolved.

    0 comments
  3. Susmitha T (INFOSYS LIMITED) 2,610 Reputation points Microsoft External Staff
    2026-03-02T09:01:21.2833333+00:00

    Thank you for reaching out!

    This "Continue with undefined" login screen normally means the authentication WebView cannot load the provider metadata - so GitHub copilot cannot resolve the sign-in providers exposed by GitHub Authentication.

    Since you already tried the common cleanup steps, this is almost always caused by corrupted WebView/token storage, not copilot itself.

     
    Below is the working reset procedure:

    1.Completely reset VS Code WebView cache: Close all instances of Visual Studio Code.
    Delete these folders:

    1. %APPDATA%\Code\CachedData
    2. %APPDATA%\Code\Cache
    3. %APPDATA%\Code\GPUCache
    4. %APPDATA%\Code\Service Worker
    5. %APPDATA%\Code\User\workspaceStorage

    The service worker folder is usually the root cause of "undefined" providers.

    2.Remove stored authentication tokens (Windows Credential Manager):

    1.Open Credential Manager

    2.Go to Windows Credentials

    3.Delete entries containing:

    • vscode
    • github
    • microsoft
    • copilot

    This clears broken keytar tokens stored by VS Code.

    3.Repair WebView runtime: VS Code authentication UI runs inside:

    Repair it:

    1.Settings-> Apps-> Installed Apps

    2.Find Microsoft Edge WebView2 Runtime

    3.Modify-> Repair

    If missing -> reinstall WebView2 runtime form Microsoft.

    4.Start VS Code without extensions (Verification step):

    • Run: </> Bash

    code --disable-extensions

    • Then try: </> Code

    Accounts -> Sign in with GitHub

    If the login works -> another extension is overriding authentication UI.

    5.Reinstall Only authentication components:

    Inside Extensions:

    1.Disable:

    • GitHub Copilot
    • GitHub Authentication

    2.Reload VS Code

    3.Enable GitHub Authentication First

    4.Restart VS Code

    5.Enable copilot again

    Order matters because Copilot depends on the auth provider registration.

    6.Force clean profile launch:

    Run: </>Bash

    code --user-data-dir %TEMP%\vscode-clear

    If sign-in works here: Your main VS code profile is corrupted.

    You can migrate settings afterward.

    7. If still failing (Known 1.108.x issue):

    There are authentication regressions reported in VS Code 1.108.x

    Try temporarily:

    • Install VS Code Insiders, or
    • Downgrade to 1.107

    Copilot authentication immediately restores in most cases.

     

    Let me know if you need any further help with this. I will be happy to assist.
    If you find this helpful, Kindly mark the provided solution as "Accept Answer", so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

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.