FileZilla always takes too long to start or do local operations











up vote
0
down vote

favorite
1












I work with FileZilla Client during all the day, and I'm having a lot of problems when I need to do quick local actions (like create folders, for e.g.), and whenever I try to open it.



After clicking on the FZ icon, it may take 5 minutes to open. No matter how many times I've opened FZ on that day.



Just to clarify that, I use Windows 10 (64b) and I don't have any mapped network drivers. I've already checked both Online Providers and HKEY settings, there doesn't seem to be anything that would suggest that the PC is trying to connect or read any remote folders I may have forgotten.



Does anyone know any workaround?










share|improve this question




























    up vote
    0
    down vote

    favorite
    1












    I work with FileZilla Client during all the day, and I'm having a lot of problems when I need to do quick local actions (like create folders, for e.g.), and whenever I try to open it.



    After clicking on the FZ icon, it may take 5 minutes to open. No matter how many times I've opened FZ on that day.



    Just to clarify that, I use Windows 10 (64b) and I don't have any mapped network drivers. I've already checked both Online Providers and HKEY settings, there doesn't seem to be anything that would suggest that the PC is trying to connect or read any remote folders I may have forgotten.



    Does anyone know any workaround?










    share|improve this question


























      up vote
      0
      down vote

      favorite
      1









      up vote
      0
      down vote

      favorite
      1






      1





      I work with FileZilla Client during all the day, and I'm having a lot of problems when I need to do quick local actions (like create folders, for e.g.), and whenever I try to open it.



      After clicking on the FZ icon, it may take 5 minutes to open. No matter how many times I've opened FZ on that day.



      Just to clarify that, I use Windows 10 (64b) and I don't have any mapped network drivers. I've already checked both Online Providers and HKEY settings, there doesn't seem to be anything that would suggest that the PC is trying to connect or read any remote folders I may have forgotten.



      Does anyone know any workaround?










      share|improve this question















      I work with FileZilla Client during all the day, and I'm having a lot of problems when I need to do quick local actions (like create folders, for e.g.), and whenever I try to open it.



      After clicking on the FZ icon, it may take 5 minutes to open. No matter how many times I've opened FZ on that day.



      Just to clarify that, I use Windows 10 (64b) and I don't have any mapped network drivers. I've already checked both Online Providers and HKEY settings, there doesn't seem to be anything that would suggest that the PC is trying to connect or read any remote folders I may have forgotten.



      Does anyone know any workaround?







      windows ftp sftp filezilla mapped-drive






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Oct 10 at 16:42









      Pierre.Vriens

      1,20561218




      1,20561218










      asked Oct 10 at 15:56









      Mateus Oliveira

      11




      11






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote













          You can confirm if there is any mapped drive by issuing a net use command from the Command Prompt or from the PowerShell.



          FZ on its own only queries drive icons and drive labels, but there are many other potential causes for accesses to offline resources. For example:




          • AV scanner scanning the entire network share just because the drive label was requested

          • Mapped drive or UNC path in %PATH%

          • Shell extension loaded from network resource

          • The icon associated with a specific file type located on a network resource.


          It could be even a disk failure. Scan your disk and check its S.M.A.R.T. status.






          share|improve this answer





















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1365581%2ffilezilla-always-takes-too-long-to-start-or-do-local-operations%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            1
            down vote













            You can confirm if there is any mapped drive by issuing a net use command from the Command Prompt or from the PowerShell.



            FZ on its own only queries drive icons and drive labels, but there are many other potential causes for accesses to offline resources. For example:




            • AV scanner scanning the entire network share just because the drive label was requested

            • Mapped drive or UNC path in %PATH%

            • Shell extension loaded from network resource

            • The icon associated with a specific file type located on a network resource.


            It could be even a disk failure. Scan your disk and check its S.M.A.R.T. status.






            share|improve this answer

























              up vote
              1
              down vote













              You can confirm if there is any mapped drive by issuing a net use command from the Command Prompt or from the PowerShell.



              FZ on its own only queries drive icons and drive labels, but there are many other potential causes for accesses to offline resources. For example:




              • AV scanner scanning the entire network share just because the drive label was requested

              • Mapped drive or UNC path in %PATH%

              • Shell extension loaded from network resource

              • The icon associated with a specific file type located on a network resource.


              It could be even a disk failure. Scan your disk and check its S.M.A.R.T. status.






              share|improve this answer























                up vote
                1
                down vote










                up vote
                1
                down vote









                You can confirm if there is any mapped drive by issuing a net use command from the Command Prompt or from the PowerShell.



                FZ on its own only queries drive icons and drive labels, but there are many other potential causes for accesses to offline resources. For example:




                • AV scanner scanning the entire network share just because the drive label was requested

                • Mapped drive or UNC path in %PATH%

                • Shell extension loaded from network resource

                • The icon associated with a specific file type located on a network resource.


                It could be even a disk failure. Scan your disk and check its S.M.A.R.T. status.






                share|improve this answer












                You can confirm if there is any mapped drive by issuing a net use command from the Command Prompt or from the PowerShell.



                FZ on its own only queries drive icons and drive labels, but there are many other potential causes for accesses to offline resources. For example:




                • AV scanner scanning the entire network share just because the drive label was requested

                • Mapped drive or UNC path in %PATH%

                • Shell extension loaded from network resource

                • The icon associated with a specific file type located on a network resource.


                It could be even a disk failure. Scan your disk and check its S.M.A.R.T. status.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 22 at 13:27









                josuegomes

                214




                214






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1365581%2ffilezilla-always-takes-too-long-to-start-or-do-local-operations%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown