chatgpt-windows-web-troubleshooting

Learning Outcomes

By the end of this lesson, you will be able to separate service, account, device, browser, network and feature-availability problems and test one likely cause at a time.

1

Protect Work First

Preserve prompts, unsaved text, filenames, URLs and screenshots before troubleshooting.

2

Identify the Scope

Use a comparison across surfaces, devices, accounts and networks to locate the fault boundary.

3

Apply Safe Fixes

Follow a least-disruptive sequence and confirm the result after every change.

4

Escalate with Evidence

Record the exact error, time, environment and tests so Support or IT can act efficiently.

Important: do not delete while diagnosing

Do not delete a conversation, project, file, browser profile or app data as an early troubleshooting step. OpenAI states that deleted chats cannot be recovered. Archive is different from delete, and clearing browser data can sign you out or remove local site preferences.

The ITIAN Safe Troubleshooting Ladder

Move down the ladder only when the previous check does not resolve or explain the problem.

Preserve the evidence

Copy unsent text, note the conversation URL or title, record the exact message, take a privacy-safe screenshot and write down the local time.

Check OpenAI Status

If there is a current incident, avoid repeated account changes. Record the incident and retry after the service update.

Define the scope

Ask: one conversation or all; app or web; one device or several; one network or several; one user or a whole workspace?

Confirm identity and destination

Check the account email, original sign-in method, selected workspace, project, conversation and intended file location.

Retry once

Wait briefly, stop a stuck response if possible, retry, or open a new privacy-safe test chat. Refresh the webpage or restart the app.

Update the affected surface

Install current browser or app updates and restart the affected program. Do not assume menus and features are identical across builds.

Isolate local interference

Test a private browser window, another supported browser, another device or another network. Temporarily test without extensions, VPN, proxy or secure DNS only when permitted.

Use targeted recovery

Check archives, permissions, storage locations and file expiry before sign-out, site-data clearing, repair, reset or reinstall.

Escalate with a clean record

Give Support or IT the error, timestamp and time zone, account/workspace, surface version, network type, reproduction steps and completed tests—never a password or one-time code.

Interactive Diagnostic Planner

Choose what is happening. The planner creates a controlled first-response sequence; it does not change your settings.

Main symptom Affected surface Observed scope OpenAI Status checked?

Symptom-to-Test Reference

A good diagnostic test changes one variable and has a clear result.

Symptom	Likely boundary	First safe comparison	Do not assume
Web works; Windows app does not	App build, app session, Windows policy or local network handling	Restart and update the app; compare the same privacy-safe prompt in the browser	The account or service is down
App works; one browser does not	Browser profile, cookie, extension or cached site data	Private window, then a different current browser	Reinstalling the app will fix the browser
Neither app nor web works on one network	VPN, proxy, DNS, firewall, certificate or filtering	Check status, then compare an authorised alternative network	Security controls should be disabled permanently
One conversation stalls	Long/complex thread, attachment or transient conversation issue	Preserve the URL and try a short privacy-safe test in a new chat	The original chat must be deleted
One person lacks a feature	Plan, workspace, admin policy, rollout, region, surface or app version	Compare account/workspace and official availability guidance	Every account receives every feature simultaneously
Generated download says file not found	Expired or stale generated-file link	Return to the source task and regenerate a fresh file	The local Downloads folder caused the expiry

Guided Recovery by Problem

Select a topic for its ordered checks. Complete only the steps relevant to your situation.

When conversations appear missing

Confirm the correct OpenAI account, email or social sign-in method and workspace.
Use chat search and inspect the expected project.
Open Settings → Data controls → Archived Chats; an archived chat is hidden from the normal list, not deleted.
Check whether the conversation was created as a Temporary Chat or under different history settings.
Refresh or restart, then sign out and back in only after recording the correct account and workspace.
Check OpenAI Status for a history incident.
If needed, request a data export to confirm which stored conversations are present. An export is evidence, not an automatic sidebar restore.

Deleted means unrecoverable

OpenAI states deleted chats cannot be restored through the interface, API or Support. Do not use Delete or Delete all chats while diagnosing.

When sign-in or a workspace is wrong

Use the same method used at registration: email/password, Google, Microsoft, Apple or organisation SSO.
Check the actual signed-in email and selected workspace; similar addresses can represent different accounts.
Try a private browser window to isolate cookies and extensions.
For verification loops, test without a VPN/proxy and ensure JavaScript and required cookies are allowed, subject to workplace policy.
If a workspace requires SSO, use its SSO option. Ask the workspace administrator about membership or policy before creating another account.

Never share: passwords, one-time codes, recovery codes, private keys or full authentication cookies.

When the app or page freezes

Wait 30–60 seconds and preserve unsent text.
Stop and retry the response if controls remain available.
Test a new short conversation.
Refresh the page or restart the Windows app.
Check status and install current updates.
On web, compare a private window with extensions disabled, then another browser.
Compare another permitted network or device to identify whether the cause follows the account, device or network.
Clear site data, repair, reset or reinstall only after the comparison tests point to local state and you understand what will be removed.

When uploads or downloads fail

Confirm the file is supported, within current limits and not password-protected or corrupted.
Use a simple filename and test one smaller, privacy-safe file.
Refresh and retry once; test a private browser window.
Check whether VPN, proxy, extension, firewall or organisational filtering blocks file domains.
Generated-file links can expire. Regenerate a fresh output from the source task rather than repeatedly using an old link.
Confirm where the output should live: browser Downloads, ChatGPT Library, an authorised local folder or another destination.

Privacy check

Do not upload confidential material merely to test a fault. Create a harmless sample file with similar size and format.

When a feature is missing

Confirm you are in the intended account and workspace.
Check whether the feature belongs to Chat, Work, Codex, a project, the built-in browser or the Classic app.
Update and restart the surface, then check web and desktop separately.
Verify plan, region, workspace type, administrator controls and official availability notes.
Allow for staged release differences; another user’s screenshot is not proof that your account should have the control.
If still unexpected, record the surface, version, plan/workspace and screenshot before contacting Support.

Safe Escalation Record

Prepare this information before contacting OpenAI Support, a workplace administrator or network team.

What happened

Exact error message
Expected versus actual result
Reproduction steps
Screenshot with secrets removed

When and where

Date, time and time zone
Conversation URL or ID if safe
Windows and app/browser version
Home, mobile or managed network

Account boundary

Account email and sign-in method
Workspace name or ID
Plan and admin restrictions
One or multiple affected users

Tests completed

Status result
App versus web
Private browser test
Alternative device/network result

HAR files require care

Support may request a browser HAR file for interface problems. HAR files can contain sensitive data. Follow the current official instructions, use a sanitised export where available, review it before sharing, and never post it publicly. The Windows desktop app does not provide browser developer tools for HAR capture.

Future Media and Demonstrations

Future Video: The Nine-Step Diagnostic Ladder

Screen recording placeholder for a safe app-versus-web comparison.

Future Screenshot Set: Missing Chat Recovery

Placeholder for account, workspace, search and Archived Chats screens.

Future Download: Troubleshooting Record

Printable worksheet placeholder for symptoms, tests, results and escalation evidence.

Official sources and review links

Last content review: July 2026. Product controls, plan availability and support procedures can change; verify the current official article before updating screenshots or performing a reset.

Next: Your Complete Windows & Web Workflow

Lesson 5.8 brings the module together: choose the right surface, organise the task, use shortcuts, preserve files, verify results and close the session cleanly.

Continue to Lesson 5.8 Return to Module 5