UPDATE June 13, 2015This issue has been fixed by Microsoft via KB3058515. For most people, this will be installed automatically via Windows Updates. If you don't have Automatic Updates enabled in Windows, I highly recommend doing so.
If you are still experiencing this issue, look at your Installed Updates (Control Panel -> Programs and Features -> Installed Updates) and see if KB3058515 is installed.
If not, see if you can force it to install by following the instructions below:
Windows 71) Open "Windows Update" by clicking the Windows Start button and typing Windows Update, then clicking "Windows Update" in the results. This will open the Windows Update control panel applet.
2) On the left, click "Check for updates". After the check has completed, click the link that says "N important updates are available" (where N is some number of updates).
3) In the "Important" section, look for update KB3058515. Hopefully it will be there, queued up for install.
4) Press the OK button, then press the "Install updates" button.
Windows 81) Press Windows Key + W to open the "Setting Search" screen. Type Windows Update in the search box and click on "View Installed Updates" in the search results.
2) On the left, click "Check for updates". After the check has completed, click the link that says "N important updates are available" (where N is some number of updates).
3) In the "Important" section, look for update KB3058515. Hopefully it will be there, queued up for install.
4) Press the OK button, then press the "Install updates" button.
If you don't find KB3058515 in the list of updates to be installed, install whatever updates ARE ready to be installed. After installing them, reboot and repeat this process. Sometimes a new set of updates are waiting for the previous updates to be installed before becoming available.
Here is a link to information about KB3058515 :
https://support.microsoft.com/en-us/kb/3058515KB3058515 is a cumulative update, and contains several other updates. Specific to this issue, it contains KB3066267:
https://support.microsoft.com/en-us/kb/3066267Original post - April 28, 2015A recent Windows Update appears to be causing issues again with the Tournament Director application. Specifically, rendering large tables of data can take a long time. Something that previously took less than a second can now take 30 seconds, 1 minute, or several minutes, depending on the size of the table and the hardware in your computer.
The cause of this issue appears to be KB3038314, delivered via Windows Update. This was first reported here (
http://www.thetournamentdirector.net/forums/index.php?topic=5013.0) on April 17.
SYMPTOMSDialogs or
Settings window pages displaying many players becomes very slow when rendering (drawing) the page. For example, the
Add Players to Tournament dialog, which typically displays your entire player database. Or the
Database tab of the
Settings window, if you have the option to display all players on a single page enabled (pagination is off). The slow nature of the rendering seems to become obvious when displaying 100 to 200 players. If your database has fewer players than this, you may not see a problem.
CAUSEAt this time,
KB3038314, delivered via Windows Update, appears to be the cause. KB3038314 was first delivered Apr 14, 2015.
Update: On May 12, 2015, Microsoft released
KB3049563 which also included
KB3038314.
HOW TO FIXUninstalling KB3038314 and KB3049563 has consistently resolved the issue.
Windows 71) Open "Installed Updates" by clicking the Windows Start button, clicking "Control Panel", clicking "Programs", and then, under "Programs and Features", clicking "View installed updates".
2) Click the update that you want to remove, and then click Uninstall. You can quickly find the update by entering "KB3038314" in the search field at the top of the window. Repeat for KB3049563.
Windows 81) Press Windows Key + W to open the "Setting Search" screen. Type Windows Update in the search box and click on "View Installed Updates" in the search results.
2) Click the update that you want to remove, and then click Uninstall. You can quickly find the update by entering "KB3038314" in the search field at the top of the window. Repeat for KB3049563.
After uninstalling, you will likely be required to restart your PC.
Unfortunately, uninstalling will not prevent Windows from installing the patch again in the future. To prevent this, follow these steps:
Windows 71) Open "Windows Update" by clicking the Windows Start button and typing Windows Update, then clicking "Windows Update" in the results. This will open the Windows Update control panel applet.
2) On the left, click "Check for updates". After the check has completed, click the link that says "N important updates are available" (where N is some number of updates).
3) In the "Important" section, look for update KB3038314. Right-click on this update and select "Hide update". Repeat for KB3049563.
Windows 81) Press Windows Key + W to open the "Setting Search" screen. Type Windows Update in the search box and click on "View Installed Updates" in the search results.
2) On the left, click "Check for updates". After the check has completed, click the link that says "N important updates are available" (where N is some number of updates).
3) In the "Important" section, look for update KB3038314. Right-click on this update and select "Hide update". Repeat for KB3049563.
RISKSKB3038314 is a security fix for Internet Explorer, so uninstalling it means potentially leaving a security issue unpatched. KB3049563 is more of a bug fix, but since it contains KB3038314 the risk of removing it is the same.
ADDITIONAL INFOHopefully Microsoft will resolve this issue in a future Windows Update. There are additional problems with KB3038314 (a quick Google search will turn up a few), but thus far Microsoft has not provided a fix for any of those issues.
The slowdown seems to only occur for pages/applications that utilize IE compatibility mode. If IE is in IE10 or "Edge" mode, the problem does not occur. Unfortunately the TD is "stuck" in compatibility mode, since Microsoft has not updated IE dialogs to move beyond compatibility mode (the TD makes
extensive use of modal dialogs). So, bad news for the TD, and even worse news since this makes it a little less likely Microsoft will fix it. On the plus side, it appears to be specifically table related. If I can rewrite the TD's tables to use a different implementation, we may be able to work around this issue completely.