You would to better reading the thread before posting.
Yea I did. Thanks for that. The âdo nothingâ setting does work on windows 10. If it doesnât work for you and your environment then contact EndNote support directly instead of complaining on a forum where nobody can help with the expertise that EndNote support has.
No it doesnât. It works for some people. The more people respond to the forum, support can see what is happening without lots of individual calls tying them up. Also, it lets other users know they are not alone when the fix does not work. Itâs what forums are for. Though, the Internet has gone downhill since the Eternal September.
Besides, they are working on a fix that still needs fully testing.
Re Clarivate support. In another thread, I found a connection file to Cambridge University didnât work. This was in EndNote V20 that I upgraded to in Feb 2023. I contacted the University, who said they changed their system in 2019. Also, that the University did a new official connection file (it is on their website) and in 2019 send the file to Clarivate support explaining the changes. Clarivate did nothing with the official University update in the last 5 years and have been sending out the old non-working file.
If there was a solution or temporary solution for the restarting EndNote, then Clarivate should post it to this forum. Otherwise, they will get very many people calling them with the same question. Which is a waste of resources.
Well. I reported this a couple of month back and looking back to this forum frequently to see if there are any changes. Setting to not open the last database isnât really an option and I tried but did not work on my Win10 system.
What I did, I scratched around on the internet looking for the previous build of Endnote which was 20.4.1. Uninstalled the buggy 20.5 and installed 20.4.1. Whoila back to a working system.
When Endnote did integrate the bug with 20.5.x. I donât understand what is so difficult to have a timely patch to fix this for so many user. Waiting to sell 21 is a good practice to my view.
1 Like
I think you mean âWaiting to sell 21 is NOT a good practice to my view.â
Otherwise, a cynic might say that it looks like they introduced a bug in the last version of V20 with the fix in the paid upgrade to V21 forcing all users to pay to fix the bug Clarivate introduced. Though, knowing SW development, I donât think this is what happened here.
I am sure that Clarivate will do a V20 patch to fix this one point for those not going to V21.
The restarting is fixed in Endnote 21 AND, so I am told it will be fixed in EndNote 20.6
(though this information is worth what you paid for it 
)
Seriously I am using EN21 and the restarting bug is fixed.
I have it on good authority that it will be fixed in EN20.06
This bug fix with the âDo nothingâ setting appears to work on my computer after a few tests. More tests in the days ahead.
Summary of the bug fix as described by EndNote technical teamâs advice to jfullert1:
With an EndNote library open, click EndNote menu Edit + Preferences + Libraries. If the setting at the top is âOpen the most recently used libraryâ then change that to âDo nothingâ.
Here are my experiences with this bug fix.
- With an EndNote library open, set âDo nothing.â You need to ensure EndNote retains the âDo nothingâ setting. I suggest selecting the âDo nothingâ setting when Microsoft Word is not open.
- Close EndNote 20.5 with its âDo nothingâ setting set.
- Reopen EndNote 20.5 through the Windows Start menu and not by clicking on an EndNote library file. . Do not reopen EndNote 20.5 application by opening an associated EndNote reference library.
- After reopening EndNote 20.5 through the Windows Start menu, recheck that EndNote 20.5 retains the âDo nothingâ setting. If EndNote 20.5 retains the âDo nothing setting,â this bug fix might work for you.
- Then close EndNote 20.5.
- Now you are ready to test this bug fix by clicking on an EndNote library and then closing EndNote 20.5.
The bug is fixed in V21, and I am informed that it will be fixed in V20.06 that is due out very shortly.
Alas, yesterdayâs successful and even reproducible fix of this problem on my computer did not endure. The bug is back with my version of EndNote 20.5. Thus, I do not recommend this purported fix.