======Trouble Shooting====== **NOTE:** If you encounter a persistent problem when using //Git Winch// please email us at admin@gitwinch.com **Git functionality**\\ We have simplified Git to such an extent that we have only given a small subset of all the stuff that //Git// can do. If you encounter some unusual situations in //Git//, you can always right-click on the folder for the pop-up menu, and drop down to the CMD window of that folder, and execute //Git// commands manually there. In many cases you can also use the excellent //TortoiseGIT// software also to do advanced //Git// work. Read more about TortoiseGit [[advancednotes?do=export_html|here]] **Handling known_hosts file**\\ Whenever you connect to a new Git host using an SSH key, your computer would want to know if the connection to the server is to be allowed. So when you clone a new repository, first //Git Winch// preforms a check to see if the connection is to a "known host". Internally //Git Winch// runs a special batch file "setknownhosts.bat" and that fetches the correct data from the server and if found okay, it would append a file at //known_hosts// which is inside the .ssh sub-folder inside your Windows folder. This uses a special utility called ssh-keyscan and unfortunately, Windows does not update this to the current requirements. So install the latest SSH utilities from https://github.com/PowerShell/Win32-OpenSSH/releases Choose an appropriate .msi installer from the list there and run it. **Syncthing functionality**\\ If you have a work folder that is managed by //Syncthing// and NOT //Git// then there can be an unusual situation where someone in your //Syncthing// group for that folder has locked a file (or the entire folder) and has refused to unlock it. Currently, you can only request that person to unlock it, as //Syncthing// do not support the concept of an "owner" for that folder. **Known Issues**\\ //Git Winch// works closely with the underlying Windows Operating system. Once you start //Git Winch// and then you start making changes to the work folder and/or sub-folders underneath the work folder, Git Winch will throw some errors and you may get some technical messages. Usually //Git Winch// will not work properly after that. So if you do want to make any changes to those folders, do all that when //Git Winch// is NOT running. ----- [[/concepts?do=export_xhtml | Learn the concepts]] | [[/configuration?do=export_xhtml|Configuration]] | [[/advantages?do=export_xhtml | Advantages]] | [[/tsManage2?do=export_xhtml|Management]] | [[ /advanced?do=export_xhtml | Advanced uses]] | [[ /topics?do=export_xhtml | Table of Contents]]