Salta al contenuto principale

Very Slow Opening Files in TextPad With Acronis TrueImage 2014 Installed

Thread needs solution

Since installing True Image 2014, TextPad (64bit) has become extremely slow to open files when right clicking in Windows Explorer and using the context menu. It takes a minimum of 15-30 seconds to open. It doesn't matter how small the file is--it is always very slow. This problem doesn't occur when opening files from the TextPad menu in the program. When I uninstalled True Image 2014 the problem was solved immediately--TextPad now opens files in about 1 second. I have Windows 7 and a brand new , quite fast, computer. Unfortunately I need to open files in TextPad constantly throughout the day so this causes a big problem for me.

There was another forum post at https://forum.acronis.com/forum/55572 that asks the same question but there are no answers to it.

Is there some part of ATI 2014 that I can turn off to stop this problem?

0 Users found this helpful

Could be a file association issue. TextPad uses DDE messages and could be in conflict. You can try to change your file associations as follows:

1. In Explorer click on Tools and select Folder Options
2. Select the tab File types.
3. Select the file type from the list and click Edit.
4. Under "Actions" select the "open" option click Edit.
5. Clear the option "Use DDE"
6. In the box called "Application used to perform action" add "%1" (including the quotes) to the end of the line.

Thank you for the suggestion.
Apparently the FileTypes tab is no longer on the Folder Options dialog in Win7. From searching around about how to do what you suggested in Win7 I get the impression that there is not a "Use DDE" equivalent anymore.

Did you ever get to the bottom of this? I've had the same problem for years!

I have tried editing the registry with the "%1" addition as recommended by some people but this hasn't helped me at all.

There is also a free tool available called "Default Programs Editor" which gives you a graphical user interface to make these kinds of changes at defaultprogramseditor.com but looking at my settings with that they still show as the recommended ones.

Thanks

DavidC

If you have had other computers on your network that no longer exist or network shares, mapped drives that no longer exist you might try this solution: Note:Taken from another Forum discussion of a like problem.

It sounds like there are a few different problems going on throughout this thread. Thanks to our IT consultant, we fixed this in our office yesterday. The problem was that there were references in the registry to computers that were no longer on the network.

One of the ways to test if your problem is similar is to disable the network card. If your delay in opening files goes away, it could have to do with an invalid registry entry. So the first step would be to search the registry for entries of any computer names that no longer exist on the network. The entry will look like this: \\graphicscomputer\share\public folder or something. It's located under a key structure like "Shell -> Open -> Command". If you can't think of any computers or locations that are no longer on the network, you can also search for "\\". You will want to back up the registry key (by exporting it) before deleting it. Delete it, then check if the problem is fixed. Otherwise, restore the key. Only entries that reference network locations are likely culprits, so avoid anything that references your local drives. Obviously, edit the registry at your own risk. 

I appreciate the suggestion as a 30 second delay does sound like it could be a network issue, however I have just disabled the NIC and the problem persists so in my case it is not that.

I have performed the registry tweak on another (XP) computer successfully in the past but no difference on this machine (Win7).

Thank you for your input.

DavidC

I am providing a link to a third party app that you can use to explore and change the Shell Extensions on your machine. I do caution that you scan the download file before installing for the usual nasty bugs! In most cases context menu problems are the result of poorly written shell extensions contained in the context menu placed there by third party apps. This app will allow you to test each one of them on a one by one basis or in groups so may be worth a shot, you be the judge.

http://www.nirsoft.net/utils/shexview.html

Another item that can cause problem behavior with menus is corrupted system files within Windows itself. To scan and correct such issues simply run the
SFC \SCANNOW from an admin command prompt.

Good Luck.