PT 8 is responding agonizingly slowly. Any suggestions?

Question

I am using PT8 on a Core i7 2.7 GHz laptop, 24 GB RAM and SSD drive, that is to say, it is a fast machine. Yet for some operations PT8 performs unbearably slowly.

Some examples:

To switch focus from the translation window to a search window can take as long as four seconds even without any other translations or windows open.
In PT 7.6 the same operation takes maybe 500 ms.

To open a Find window takes 5 seconds.
For the same operation in PT 7.6, perhaps 100ms.

Clicking on an item a list window and then shifting focus to the item in the text window takes up to 7 seconds.
For the same operation in PT 7.6, perhaps 1.5 sec.

I have Scroll scripture with compatible applications is turned off. Highlight current verse is turned off. I am using WIN 10. I was not using the Creators edition and it was like this. I then updated to the Creators edition, but he issue did not change. Currently I am on Insider Preview Build 16232.rs_prerelease.7064-1334, obviously with this same issue.

Is anyone else experiencing this? Any suggestions of what might be the matter?

舊文章 - 以原文顯示

Answer 1

I had hoped to postpone my update to Windows 10 version 1703 Creators Update until the update that Paul Nelson said would come on 17 Oct, which hopefully wouldn’t have the Paratext slowdowns and the FLEx crashes. Unfortunately, in an unguarded moment, I allowed the Creators Update to be downloaded on my computer. I postponed it for a while, but then I was forced to install it because I needed to perform another software installation, and it wouldn’t install with the pending Windows update. So I went ahead and installed version 1703, verified that indeed Paratext was slow and FLEx crashed, then backed out of it, back to version 1607. But the thing that surprised me is that right after I backed it out, I tested Paratext and FLEx, and they both functioned fine, even though I have .NET 4.7 from an update that was installed right before before the Creators Update was installed. I’ve included the report from ASoft .NET Version Detector below to show the version.

So is this a known result? I.e. is there a release version of .NET 4.7 (4.7.2110.0) that can be installed on Windows 10 version 1607 that fixes the Paratext slowdown and the FLEx crashes? If so, it seems like we should let people know about that, including any corresponding KB numbers.

<32Bit>
2.0.50727.8766
->C:\Windows\Microsoft.NET\Framework\v2.0.50727
4.7.2110.0
->C:\Windows\Microsoft.NET\Framework\v4.0.30319

<64Bit>
2.0.50727.8766
->C:\Windows\Microsoft.NET\Framework64\v2.0.50727
4.7.2110.0
->C:\Windows\Microsoft.NET\Framework64\v4.0.30319

< Installed .NET Frameworks >
.NET FW 2.0 SP 2 (CLR:2.0)
.NET FW 3.0 SP 2 (CLR:2.0)
.NET FW 3.5 SP 1 (CLR:2.0)
.NET FW 4.6.2 General release (CLR:4.0)
.NET FW 4.7 General release (CLR:4.0)

< Installed Updates >
Microsoft .NET Framework 4 Client Profile
KB2468871
KB2468871v2
KB2478063
KB2533523
KB2544514
KB2600211
KB2600217
Microsoft .NET Framework 4 Extended
KB2468871
KB2468871v2
KB2478063
KB2533523
KB2544514
KB2600211
KB2600217
KB2468871
KB2468871v2
KB2478063
KB2533523
KB2544514
KB2600211
KB2600217
Microsoft .NET Framework 4 Multi-Targeting Pack
KB2504637 Update for (KB2504637)

舊文章 - 以原文顯示

Answer 2

Do you have .Net 4.7 (PT 7.5 slow moving from window to window)?

EDIT: Nevermind, I assume the times for 7.6 are on the same machine, so it can’t be caused by .Net 4.7.
I have experienced the slowdowns described when using .Net 4.7.0, but it affects both 8.0 and 7.x.

舊文章 - 以原文顯示

Comments

I think I do have 4.7. I found this in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\1033 “Version”=“4.7.02523”

Actually though 7.6 is not as slow, it still feels slower than how it was before. It could affect the versions differently.

舊文章 - 以原文顯示

Answer 3

Maybe try updating to Insider Preview 16241.1001 or later and see if that fixes it?

舊文章 - 以原文顯示

Answer 4

Read the help topic “Why is Paratext slowly?” and see if what it says explains the slowness.

舊文章 - 以原文顯示

Answer 5

All of the operations you describe above are almost instantaneous on my computer with the 16241.1001 Insider Preview.

舊文章 - 以原文顯示

Answer 6

I solved the problem by choosing the Fast updates option in the Windows Insider Program settings. I had set it to the conservative Slow updates option. My machine updated overnight to the latest Preview build 16251.rs3_release.170721-2122. That build did fix the problem with Paratext slowly. My .net version went from [Phone Removed]to [Phone Removed]All operations are now at the expected lightning clip.

舊文章 - 以原文顯示

Comments

We solved this problem with dotNet 4.7 on 2 machines last week, where the Creators Update had been deferred, but 4.7 had installed anyway. Here is roughly how we did it (sorry, I’m not on Windows 10, so can only give it to you roughly):

Under Settings (this PC), there is a place called Windows Updates with two circular arrows.
Click on that.
Inside there is a link to view installed updates or something similar.
Click on that.
If in there it says something about dotNet 4.7, you need to uninstall that update.
So click on uninstall.
It turns out, you need to know the number of the update to uninstall. Here it is: KB3186568
It is just listed as an ordinary MS Windows update and says nothing about the dotNet/.Net.
Once that update was uninstalled, PT on these machines went back to normal speed.

舊文章 - 以原文顯示

---

The fix for Windows 10 has now been pushed to the regular update ring (meaning it will get automatically installed). As a result I’m guessing that it is also either available on your machine as an update or will be soon.

Of course, if NET 4.6 is working fine for you you may not need to upgrade again, but people whose machines have upgraded themselves may no longer need to downgrade.

舊文章 - 以原文顯示

---

Well that would be great news!! Would that mean that people can now happily install Creators Update and expect the .NET 4.7 bug to be fixed by an ordinary update? Just 3 days ago, an ordinary update with .NET 4.7 was still causing seriously slow PT performance. So how do you explain that?

How do you know whether the automatic .NET 4.7 update they send you is the one we got 3 days ago that caused the problem,
or the one you are talking about, which solves the problem?

舊文章 - 以原文顯示

---

The update to Creators caused the problem (by installing NET 4.7). The later update solves the problem. If you’re on Creators Update and still experiencing lag, try update manually. If that doesn’t work download the (large) file that anon291708 linked to in “this post” right above this.

舊文章 - 以原文顯示

---

Got a response from Microsoft (see here):

Update for Windows 7 and all other OSs will be available in the end of August.

舊文章 - 以原文顯示

Answer 7

Microsoft has begun rolling out the fix for the .Net 4.7 bug to the Windows 10 Creators Update (still no word on previous Windows versions). See this comment on this site.

You can also see this post on their bug-tracker for the official Microsoft post.

舊文章 - 以原文顯示

Answer 8

.Net 4.7.2106 and later contains the fixes. OS versions should not matter.

舊文章 - 以原文顯示

Comments

Hi anon291708,

How do you determine the micro version of .NET 4.7, that is, the last four
digits? Windows Update keeps offering me:
“Microsoft .NET Framework 4.7 for Windows 7 and Windows Server 2008 R2 for
x64 (KB3186497)” (published 27/06/2017);
as well as:
“2017-10 Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6,
4.6.1, 4.6.2, 4.7 on Windows 7 and Server 2008 R2 for x64 (KB4043766)”
(published 10/10/2017).

If I look at the stand-alone download page (
https://www.microsoft.com/en-us/download/details.aspx?id=55167&751be11f-ede8-5a0c-058c-2ee190a24fa6=True&40ddd5bd-f9e7-49a6-3526-f86656931a02=True),
all I see is:
Version: 4.7
File Name: NDP47-KB3186497-x86-x64-AllOS-ENU.exe
Date Published: 5/2/2017
File Size: 58.7 MB

The dates for the packages with .NET 4.7 on its own look a bit troubling…
And none of these show anything like “.NET 4.7.2106”. Given the issues
that people have faced, I’d like to know I’m getting the right version.
Thanks,

Paul

舊文章 - 以原文顯示

---

I anon421222’t know how you could see the full version number when downloading it. The only way I know is to install it and then look.

Paul:

The dates for the packages with .NET 4.7 on its own look a bit troubling…

Yes, those dates mean that the install is unlikely to have the fix.

舊文章 - 以原文顯示

---

anon291708:

I anon421222’t know how you could see the full version number when downloading it. The only way I know is to install it and then look.

Look where?

I’ve always wondered what the best way to see both the macro and micro version numbers of installed variants of .NET are. The only way I know is to look at the subfolder names in the folder:

c:\Windows\Microsoft.NET\Framework & Framework64

舊文章 - 以原文顯示

Answer 9

The Windows 10 Fall Creators Update (version 1709) solves all these issues. If you want to get it now, go to https://www.microsoft.com/en-us/software-download/windows10, click the Update now button and run the Windows10Upgrade9252.exe file that it downloads.

舊文章 - 以原文顯示

Answer 10

Our MTTs have pretty basic computers, Win10 with 4 GB RAM (I can provide other stats, if necessary, next time I’m in the office).

Some computers are PT8 just fine, but some are extremely slow. What can I look at to solve this?

舊文章 - 以原文顯示

Comments

wdavidhj:

Our MTTs have pretty basic computers, Win10 with 4 GB RAM (I can provide other stats, if necessary, next time I’m in the office).

Some computers are PT8 just fine, but some are extremely slow. What can I look at to solve this?

While I’m grateful for @John+Wickberg’s reply about my computer, the above is the issue that’s causing our project most grief. No answer so far, though I do realise that I’ve provided very little detail: that’s because there’s not much more to say.

I’ve checked the issues mentioned in Why is Paratext slowly?, and found that the affected user had By Chapter switched off for the project she’s editing, so I changed that, and I’m sure it will help. However, she was reporting trying to type and the text appearing 30 seconds later. My experience is that switching on By Chapter causes slow performance when switching verses; surely it wouldn’t cause problems with simple typing?

wdavidhj:

BTW, on my own computer (Dell XPS-15, 7th gen Core i7 @ 2.8 GHz, 32 GB RAM, 1 TB SSD) it takes about 4 seconds to display a source-language lexicon window when I right click on a lemma in an SLT window, then choose from the lexicons offered.

I’d also be interested in a comment on this. For others of you reading this, how long does a lexicon take to open?

舊文章 - 以原文顯示