Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Error message: Unable to open the summary file for Inbox on cfogelman@gmail.com. Perhaps there was an error on disk, or the full path is too long.

  • 4 răspunsuri
  • 0 au această problemă
  • 1 vizualizare
  • Ultimul răspuns de CFogelman

more options

I got this error message and don't know what to do with it. All the other subs under gmail (sent, all mail, etc) are fine. No current inbound gmail displays under "inbox," though it does in "all mail." While checking by using gmail app, everything seems fine. How can I reopen or repopulate my inbox? Thanks.

I got this error message and don't know what to do with it. All the other subs under gmail (sent, all mail, etc) are fine. No current inbound gmail displays under "inbox," though it does in "all mail." While checking by using gmail app, everything seems fine. How can I reopen or repopulate my inbox? Thanks.

Toate răspunsurile (4)

more options

If IMAP, just delete the inbox from within windows file explorer and it will repopulate.

more options

Thanks. Tried that, but the delete program (which was going for everything in the gmail folder, not just inbox) halted, messaging that the file was in use by another program, which seems implausible. I'd closed TB first, of course. Any ideas? I guess I got just delete the whole account and reinstall, but since I have a lot of marked and sorted gmail I'd rather not.

more options

I could delete, not I got just delete, in above message.

more options

Well, here's a bizarre followup. I had rebooted once, to no effect. I just rebooted again, and everything returned to normal, including the gmail inbox. So the problem, at least for now, has sorted itself. ("Go Figure", we used to say in the Bronx). Thanks for your help. Perhaps I'll be back again with the same problem or a variant, but for now at least it's solved.