Please close/disable all anti-virus and anti-malware programs so they do not interfere with the running of. Program Files TortoiseSVN bin TSVNCache.exe C: WINDOWS. You can safely disable this by turning off caching in your TortoiseSVN settings (set to 'none') This is a file related to Tortoise SVN. It allows for the icon overlay in Windows Explorer for checked out files or folders from a Subversion repository. Not an essential file, unless you are currently using subversion and Tortoise. Ubuntu on Windows allows you to use Ubuntu Terminal and run Ubuntu command line utilities including bash, ssh, git, apt and many more. Please note that Windows 10 S does not support running this app. To launch, use 'ubuntu' on the command-line prompt (cmd.exe), or click on the Ubuntu tile in the Start Menu. The TSVNCache.exe process is not an essential file to the computer performance. Disabling it or enabling it is down to the users' options.
Well - the facts as I understand them :)
Shell Extensions are COM objects. They are implemented as DLLs which areloaded by the Windows shell. There is no facility for shell extensions toexist in a separate process - DLLs are the only option, and they are loadedinto other processes which take advantage of the Windows shell (althoughobviously this DLL is free to do whatever it likes).
For the sake of this discussion, there are 2 categories of shell extensions:
![Tsvncache exe disable pop-up blocker Tsvncache exe disable pop-up blocker](/uploads/1/1/9/6/119612774/542942979.png)
- Ones that create a new “namespace”. The file-system itself is an example ofsuch a namespace, as is the “Recycle Bin”. For a user-created example,picture a new tree under “My Computer” which allows you to browse a remoteserver - it creates a new, stand-alone tree that doesn’t really interactwith the existing namespaces.
- Ones that enhance existing namespaces, including the filesystem. An examplewould be an extension which uses Icon Overlays to modify how existing fileson disk are displayed or add items to their context menu, for example.
Tsvncache Exe Disable App
The latter category is the kind of shell extension relevant for TortoiseBzr,and it has an important implication - it will be pulled into any processwhich uses the shell to display a list of files. While this is somewhatobvious for Windows Explorer (which many people consider the shell), everyother process that shows a FileOpen/FileSave dialog will have these shellextensions loaded into its process space. This may surprise many people - thesimple fact of allowing the user to select a filename will result in anunknown number of DLLs being loaded into your process. For a concreteexample, when notepad.exe first starts with an empty file it is using around3.5MB of RAM. As soon as the FileOpen dialog is loaded, TortoiseSvn loadswell over 20 additional DLLs, including the MSVC8 runtime, into the Notepadprocess causing its memory usage (as reported by task manager) to more thandouble - all without doing anything tortoise specific at all. (In fairness,this illustration is contrived - the code from these DLLs are already inmemory and there is no reason to suggest TSVN adds any other unreasonableburden - but the general point remains valid.)
This has wide-ranging implications. It means that such shell extensionsshould be developed using a tool which can never cause conflict witharbitrary processes. For this very reason, MS recommend against using .NETto write shell extensions[1], as there is a significant risk of being loadedinto a process that uses a different version of the .NET runtime, and thiswill kill the process. Similarly, Python implemented shell extension may wellconflict badly with other Python implemented applications (and will certainlykill them in some situations). A similar issue exists with GUI toolkits used- using (say) PyGTK directly in the shell extension would need to be avoided(which it currently is best I can tell). It should also be obvious that theshell extension will be in many processes simultaneously, meaning use of asimple log-file (for example) is problematic.
In practice, there is only 1 truly safe option - a low-level language (suchas C/C++) which makes use of only the win32 API, and a static version of theC runtime library if necessary. Obviously, this sucks from our POV. :)
Tsvncache Exe Disable Command
[1]: http://blogs.msdn.com/oldnewthing/archive/2006/12/18/1317290.aspx