Problem with x64-v4.18.2

[Diogo37]

Anyone else having problems after the update x64-v4.18.2?
in the previous version everything was normal, I updated yesterday and I couldn't even open it anymore.

[Flag_Hippo]

I've seen some reports of PokerTracker 4 not responding after updating but I've not seen a report of it not opening at all. Whatever the case is here then please restart your computer and send us a log file as described below so we can investigate and follow up with you:

1. Start PokerTracker 4 with logging enabled - see this guide (see method #2, #1 will not work unless you already have enabled logging previously).

2. If PokerTracker 4 is not starting or opens and is unresponsive then wait for a few minutes and if it remains unopened/unresponsive grab your log file and attach that to a Support Ticket.

3. To access the log file open File Explorer in Windows and enter the following in the address bar:

%localappdata%\PokerTracker 4\Logs

The file we need will be the text file called 'PokerTracker4' or 'PokerTracker4.log' that is in that folder.

You can then safely revert to the previous version of PokerTracker which can be downloaded from here.

[dupong22]

Hi,yes i cant open up pokertracker after the latest update aswell.
it just a white screen.

[Flag_Hippo]

Hi,yes i cant open up pokertracker after the latest update aswell.
it just a white screen.

Then please follow the instructions from my previous reply. Thank you.

[Jaimo89]

I'm getting the same issue, says it is not responding. I will also follow instructions I guess....

[WhiteRider]

The latest version updates the cache functions at start-up on the first run. This only needs to be done once for each database (when a database is first made Active).
Unless your database is massive it shouldn't take more than a few minutes so please just let it run.
If you continue to have problems after that please follow the directions from Flag_Hippo.

[ElHive]

Maybe you should implement a heads up message that cache updating is necessary at first start after install? That would clear up any confusion from the get go.

[WhiteRider]

That has been added for the next release. We agree it would have been better to do it for this change but for most databases the update is barely noticeable and the delay in larger databases was unfortunately overlooked before release.