ChatGPT Classic Sign-In Fails on Windows: What to Check
ChatGPT Classic not working on Windows can mean that the application opens but the browser-based authentication handoff fails. If sign-in returns to an openai-sidetron callback with a NextAuth GET error, check the browser session before assuming the installed app needs to be reinstalled.
The available reports describe a focused ChatGPT Classic sign-in problem, not a confirmed general ChatGPT outage. The checks below separate browser authentication from installed-app failures and keep reversible actions first.
Evidence note: The callback sequence and Windows checks are described in this GitHub report. The cookie result and authentication-provider observation come from this OpenAI Community report. Both are user reports, not confirmed root-cause analyses.
Identify the ChatGPT Classic Sign-In Failure
In the GitHub report, ChatGPT Classic opened, the user authenticated in a browser, and the process failed at an openai-sidetron callback with a message that an HTTP GET action is not supported by NextAuth.js.
A callback is the return step that sends the browser back to an application after authentication. The error points toward the sign-in handoff, but it does not prove that the ChatGPT Classic interface or installed files are damaged.
This differs from an application that will not launch, closes immediately, or is marked damaged by Windows. It also differs from a problem affecting the new ChatGPT application or Codex. If the new ChatGPT app and Codex work normally while ChatGPT Classic alone cannot complete sign-in, that narrows the scope, but it does not identify whether the Classic app or the authentication flow is responsible. The Classic authentication path, browser session, or interaction between the installed app and browser flow may still need investigation.
ChatGPT Classic Not Working on Windows: Quick Diagnosis Table
Use the least destructive check that matches the exact failure point.
| Symptom | Least destructive first check | What the evidence may indicate |
|---|---|---|
| ChatGPT Classic opens, but sign-in ends at an openai-sidetron callback or NextAuth GET error | Retry the browser login, verify the default browser, then inspect ChatGPT or OpenAI cookies and site data | Browser session or account authentication flow |
| ChatGPT Classic will not launch | End any remaining ChatGPT Classic process and check Microsoft Store updates | Installed Windows app |
| The app launches but behaves incorrectly before sign-in | Use Windows Settings app Repair before clearing data or reinstalling | Installed app files or local app state |
| Browser sign-in fails in the normal profile but works in a private window | Compare the normal profile with the private-window result and inspect stored site data | Browser session or profile state |
| Sign-in fails across multiple browsers, devices, or OpenAI applications | Compare the scope and record which combinations fail before changing local data | May indicate a wider authentication or service issue, but the listed evidence does not establish that scope by itself |
This is a decision aid, not root-cause analysis. A single successful workaround, or failures seen by other accounts, does not by itself establish why the problem occurred or confirm a wider service issue.
Run the Basic Windows Checks Before Clearing Data
Start with reversible actions: end ChatGPT Classic processes, check Microsoft Store updates, use Windows app Repair, verify the default browser, and retry the browser login. The exact Microsoft Store update wording and the Windows Settings path for installed-app Repair can vary by Windows version, so look for the equivalent controls while keeping this order.
- End ChatGPT Classic processes. Close the visible window, then use Windows Task Manager to check for remaining ChatGPT Classic processes. End only the relevant process before launching the app again.
- Check Microsoft Store updates. Open Microsoft Store, visit its library or updates area, and check whether ChatGPT Classic has an available update. The label or location of this control can vary by Windows version.
- Use Windows app Repair. In Windows Settings, open the installed-app controls for ChatGPT Classic and select Repair if that option is available. The path and wording can vary by Windows version.
- Verify the default browser. Confirm that Windows has a working default browser selected and that it can open ChatGPT or OpenAI sign-in pages normally.
- Retry the browser login. Record whether the failure occurs before authentication, after authentication, or specifically at the openai-sidetron callback.
In the cited GitHub report, this sequence did not fix the issue for one reporter. It can still separate common local conditions from the callback problem, but it is not sufficient for every case.
Try the Reported Browser-Cookie Workaround
One GitHub reporter signed in immediately after clearing Firefox cookies and site data associated with ChatGPT or OpenAI. An OpenAI Community report separately says that clearing cookies on chatgpt.com fixed ChatGPT Classic login.
Firefox Route Reported for the Referenced Interface
In Firefox, open Settings > Privacy & Security > Cookies and Site Data > Manage Data. Search for ChatGPT and OpenAI, remove the matching entries, close and reopen Firefox, and retry ChatGPT Classic sign-in. This is the route reported for the referenced Firefox interface; menu labels can vary by version, and matching the route is not evidence of the underlying cause.
Remove only the matching site-data entries rather than all browser history when possible. This may sign you out of ChatGPT or other OpenAI web sessions, so know the sign-in method you normally use before clearing them.
The Community report also observed only the openai provider in one authentication-providers response, while an unsigned-in incognito window showed additional providers including openai-sidetron. That difference supports checking session state, but it does not identify the exact cookie or cause.
Neither report proves that the workaround works for everyone. Treat a successful retry as user-reported evidence about that browser session, not as a confirmed universal fix.
When Reinstalling or Repairing Is Unlikely to Answer the Problem
Reinstalling ChatGPT Classic is less likely to answer a callback-only failure when the application launches and the failure appears immediately after browser authentication. That pattern is more consistent with an authentication-flow or browser-session problem than with an app that cannot start.
Repair remains a reasonable early check because it targets the installed app without immediately removing data. If updates, Repair, a verified default browser, and a clean retry all fail at the same callback, repeating the same app action is unlikely to provide new evidence.
- Callback failure after authentication: investigate browser cookies, site data, the default browser, and the Classic sign-in flow.
- Application will not launch: investigate processes, Microsoft Store updates, Windows app Repair, and installed-app behaviour.
- Application is marked damaged or misbehaves before sign-in: focus on Windows app repair or reinstall considerations rather than assuming the browser caused the problem.
- Other OpenAI applications work while Classic alone fails: the comparison narrows the scope toward the Classic authentication path or app, but it does not identify which of those is responsible or prove a product defect.
If the ordered checks fail, the available reports do not establish whether the remaining issue is in the browser session, authentication flow, installed app, or service. Reinstalling is therefore not a guaranteed next step.
A Practical Decision Checklist for ChatGPT Classic Users
- The app does not open: end any remaining ChatGPT Classic process, check Microsoft Store updates, and use Windows app Repair. Keep investigating the installed app if the launch failure remains.
- The app opens and authentication fails at openai-sidetron: verify the default browser, retry once, then remove only ChatGPT or OpenAI cookies and site data in the browser used for sign-in.
- Private-window sign-in works: return to the normal browser profile and investigate its stored site data instead of immediately reinstalling ChatGPT Classic.
- Cookie clearing restores access: record that result as a browser-session workaround. Do not claim that a particular cookie or confirmed product bug has been identified.
- The same issue appears across browsers, devices, or OpenAI applications: compare the scope before treating it as a local Windows installation problem. A broader pattern may indicate a wider authentication or service issue, but the listed evidence does not establish that scope by itself.
- Nothing changes after the ordered checks: record the exact callback text, browser, completed checks, and whether ChatGPT Classic alone fails. The GitHub and OpenAI Community reports are limited user reports, so they cannot establish prevalence, a definitive cause, or a guaranteed fix.
Frequently asked questions
Why does ChatGPT Classic show an openai-sidetron callback error on Windows?
A reported Windows issue shows ChatGPT Classic failing after browser authentication at an openai-sidetron callback with a NextAuth.js message that an HTTP GET action is not supported. The reports do not establish whether the cause is browser session state, the Classic app, or a server-side authentication issue.
Can clearing Firefox cookies fix ChatGPT Classic sign-in?
Clearing Firefox cookies and site data associated with ChatGPT or OpenAI allowed one GitHub reporter to sign in immediately. A separate OpenAI Community user reported that clearing chatgpt.com cookies worked, but neither report identifies the exact cookie or proves the workaround works for everyone.
Should I repair ChatGPT Classic through Windows settings before clearing cookies?
Windows app Repair is an early check before clearing browser site data or reinstalling the application. Repair did not fix the reported callback problem for one GitHub user, so a failed Repair should lead to browser-session checks rather than repeated repairs. The exact Settings path can vary by Windows version.
What if ChatGPT Classic will not sign in but the new ChatGPT app or Codex works?
That comparison narrows the issue toward the ChatGPT Classic authentication path or installed app, but it does not identify which one is responsible or prove a product defect. Check the browser session, default browser, and exact callback before treating it as an app-only problem.
Does clearing cookies prove that the ChatGPT Classic authentication bug is fixed?
No. Cookie clearing can show that stored browser session data was involved in one successful retry, but it does not identify the exact cause or establish a universal fix. Treat the result as a user-reported workaround.
Last updated: 04 November 2026
