Replies

Rarely. Thunderbird sometimes flags a message “this might be spam” or “this looks like spam” and puts it in a junk folder. Those messages have always been from familiar sources, I click “not spam”, and they are returned to the inbox.

Win 10 Pro, 64-bit, 22H2, Firefox, Thunderbird, Duckduckgo, Office 2007 Enterprise (working fine so far, no reason to change yet, only use Word, Publisher, occasionally Excel).

1 user thanked author for this post.

NaNoNyMouse

I’m still using Word 2007 on a desktop system. I’ve got photo phobia and that bright white screen is painful, even though the monitor is turned way down. I avoid it when I can. In Word Options/Popular, I choose Color scheme Silver. Same setting in Excel. That stops the squinting. It only causes problems when I want to use shading. In Display/formatting I’m also sure to “Show all formatting marks”. When something blows all over the place, I want to SEE what is causing it.

Every time I backup my data files, I also backup all my Thunderbird email messages. It’s a long path, but once you do it a few times you will have it memorized. Go to File Explorer and choose:

Local Disk C:\Users\[Your User Name]\AppData\Roaming\Thunderbird\Profiles\[Your Profile]\Mail\Local Folders (or whatever you named your mail folder)

When you get to Local Folders, RIGHT CLICK on it and choose Send to. Choose the location where you save your backups. In my case, an external hard drive.

You can still get all the original Win7 games for Win 10 from Winaero.com. I couldn’t attach any of their files, they are too big or not allowed. I unwind with Spider Solitaire every day!

Thanks Paul for your response. I don’t have an external disk, but I did do an image about a year ago. It took 7 DVDs.

Actually, I kept at it and the issue is fixed. I followed an old thread on the MS blog, a couple IS Admin types yelling at MS for not providing a fix for the “at risk” message. Way down in the thread a guy said “…this worked for me”, download/install the enormous full 737 MG version of KB4093112 dated April 07. So I did and it failed the install, but it gave me a new error message, 0x800870bc2. I put that into Google and found this on answers.microsoft.com . Whatever those commands are unstuck all the KBs that downloaded but failed since January. One after another they installed, the “at risk” message is gone, and things seem to be moving again. So far so good.

Thanks again for giving me an option.

Kris