Pages: 1
RSS
I am unable to open The Bat.
 
I am unable to open The Bat.

It worked yesterday, before a system change was made to the latest Window 11 update (see below). I believe that this was my first usage of The Bat after the system change

All I get is the logo screen and the Connection Center screen. The logo screen disappears and nothing happens. The icon remains on the Task bar. Clicking on the icon I see a blank screen showing up on the icon.

I'm running
Windows 11 with the latest update  
Cumulative Update Preview for Windows 11 Version 22H2 for x64-based Systems (KB5034204)
The Bat 11.0.3.2

I've tried
"/nologo" on the commmand line
Reinstalling The Bat
Running in Administrative mode

Richard
 
If you haven't already done so, please report this to Ritlabs' technical support staff (see Support menu at the top of this page). If it was caused by the Windows update, they may have to find a workaround and release a new version of The Bat.
I volunteer as a moderator to help keep the forum tidy. I do not work for Ritlabs SRL.
 
If I remember correctly, there are reports on this forum about TB 11 and Windows 11 not always getting along.

I don't use Windows 11 so I don't know if this is still a thing, but you could try running TB in compatibility mode for Windows 10 (go to properties of the executable).
 
I'm in contact with the technical support staff. So far they have asked me to rename a bunch of files in the Mail directory. The files were recreated when I launched The Bat. The problem persisted.

However one file was missing in the mail directory: userdef.xml This file seems to have something to do with the user settings.

I'm now waiting for a 2nd answer from them

I looked in the file ex_log.txt. When I try and launch the Bat it's full of lines:

        v11.0.3.2 64-bit / 26-Jan-24 11:35:07.364 GUIDEF:Item [meQuick] is linked to unknown property [Quick]

Compatibility mode doesn't differentiate between Win10 & Win 11.

Any thoughts,

Richard in Paris
 
I don't have the file userdef.xml anywhere and TB 11 works nicely in Windows 10.

EDIT: it is a user interface layout configuration file, introduced in v9 instead of tbuser.def: https://www.mail-archive.com/tbbeta@thebat.dutaint.com/msg112073.html I have tbuser.def in my mail directory, recently updated.

Have you tried compatibility mode for Windows 8? CEF may not work, but it is still better than nothing working.
Edited: Miloš Radovanović - 26 January 2024 13:20:26
 
II have tried Win 8 compatibility mode. Same problem wouldn't launch.

There were error messages that appeared very briefly at launch, to fast for me to read them. Is there some sort of log file some place where they would be captured



Richard in Paris

.
 
In the mail directory there is thebat64_Exceptions.log which records access violations, in addition to ex_log.txt.

To see the error messages you could try recording the screen using OBS or something similar and watching the video frame by frame.
 
Have you tried to reboot Windows in "Safe Mode with Networking" and then run The Bat?
I volunteer as a moderator to help keep the forum tidy. I do not work for Ritlabs SRL.
 
Have you tried to reboot Windows in "Safe Mode with Networking" and then run The Bat?

I tried rebooting without network. Still doesn't work
 
Quote
Daniel van Rooijen wrote:
Have you tried to reboot Windows in "Safe Mode with Networking" and then run The Bat?
When I go into "Safe Mode with Networking", the networking is not configured. I heard about this. It could be the PC/laptop manufacturer did not include this?
 
Two more ideas from me:

1. Disabling CEF: run TB with the command-line option /ForceNoCEF

2. Disabling SQLite indexing: open Registry Editor and navigate to Computer\HKEY_CURRENT_USER\SOFTWARE\RIT\The Bat!. Set key DisableSQLIndexer to value 1.
 
Quote
Miloš Radovanović wrote:
Two more ideas from me:

1. Disabling CEF: run TB with the command-line option /ForceNoCEF

2. Disabling SQLite indexing: open Registry Editor and navigate to Computer\HKEY_CURRENT_USER\SOFTWARE\RIT\The Bat!. Set key DisableSQLIndexer to value 1.
This is for 11.x users?
 
Quote
Frederick Smith wrote:
This is for 11.x users?
1. Disabling CEF is possible since v10.5.1
2. Disabling the SQLite indexer is possible since v11.0.3.1
 
[I had to look it up] CEF
 
Did this non starting get resolved? Sane issue here with Windows 10. Worked one ay, not the next day. It was suggested I rename those files but no joy.

Does re-installing help?

G
 
Quote
Graham Rendell wrote:
Did this non starting get resolved? Sane issue here with Windows 10. Worked one ay, not the next day. It was suggested I rename those files but no joy.

Does re-installing help?

G
It could be a number of things. What version of TB are you using?
 
Hi
V 10.5.3.3 64bit

If I do have to reload which would you recommend?

G
 
A couple of things to try (back up your message base first):

1. Reinstall v10.5.3.3
2. Upd ate to v10.5.4
3. Start TB with the command-line option /ForceNoCEF
4. Start TB with the command-line option /reg:newprofile

The last one starts TB with a "blank slate" - fresh default se t of registry values and settings. You need to point TB to your account data (Account -> New...).
 
Thanks for getting back to me. Will both the above options keep all my email data?

g
 
Quote
Graham Rendell wrote:
Thanks for getting back to me. Will both the above options keep all my email data?

g
Yes, but back it up just in case. Simply copy the appropriate data folder to an external drive.

Reinstallations and updates preserve the data.

/ForceNoCEF simply disables the use of Chromium for viewing HTML messages. The alternative that is used is not too bad actually. Also, the new address book interface and calendar will not be available.

Using the /reg option will feel like a clean installation of TB, so many settings will probably need to be adjusted. But the old ones are not forgotten, running TB without the /reg option will bring them back.
Pages: 1