Windows 7 immediately disconnects a USB drive





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I am having a problem with Windows 7 x64 consistently disconnecting one specific USB mass storage drive immediately after it is connected. The drive in question is a Cowon C2 digital music player which works both in MSC (mass storage controller) or MTP (Media Transfer Protocol) modes, i.e. there are no device-specific drivers needed/available. The basic issue is the same in both MSC and MTP modes.



When I connect the player, Windows plays the "USB connect" sound and the device appears (under its correct name) in the device manager, but it never appears as a drive. The player itself displays "USB Connected" for a split-second before reporting that it has been disconnected again. Since the player, by design, reboots after it has been disconnected, Windows plays the "USB disconnect" sound before restarting the whole cycle once the player has powered back on.



I am connecting the player through an Intel X79 Chipset motherboard (Gigabyte GA-X79-UD3) to Windows 7 Pro 64-bit. The player used to work fine the first time I connected it in MSC mode, showing up as an external drive; the issue only appears when subsequently connecting it again. This can be reproduced: uninstalling the standard Windows mass storage driver (USBSTOR.SYS) from the device manager while the device is visible there, then reconnecting the device, the driver is automatically reinstalled and the device remains visible. After disconnecting and reconnecting it, the problem occurs once more. In MTP mode, driver installation fails in the first place, but that might be due to other reasons. The problem is the same: as soon as the device is connected to the computer, Windows disconnects it again.



It is not a problem with the player, since the issue does not occur on another system running the exact same operating system. It is also not a problem with the USB controller, since the issue is the same on both the Intel USB 2.0 and the Fresco Logic FL1009 USB 3.0 controller ports. I have also not had the problem with any other drive so far.



Among the things I have tried so far:




  • Disabling USB legacy mode in BIOS

  • Disabling energy-saving power down for all USB controllers in Windows' device manager

  • Removing and reinstalling USB controller drivers

  • Restoring the player to factory defaults


None of these made a difference. I would be very grateful for any hints on what else to try.



Edit: Here is another new hint; I found out that when I connect the drive before booting Windows, it is available in Windows Explorer as it should, and does not automatically disconnect. If I remove and reconnect it though, the infinite connect/disconnect-loop starts anew.










share|improve this question































    0















    I am having a problem with Windows 7 x64 consistently disconnecting one specific USB mass storage drive immediately after it is connected. The drive in question is a Cowon C2 digital music player which works both in MSC (mass storage controller) or MTP (Media Transfer Protocol) modes, i.e. there are no device-specific drivers needed/available. The basic issue is the same in both MSC and MTP modes.



    When I connect the player, Windows plays the "USB connect" sound and the device appears (under its correct name) in the device manager, but it never appears as a drive. The player itself displays "USB Connected" for a split-second before reporting that it has been disconnected again. Since the player, by design, reboots after it has been disconnected, Windows plays the "USB disconnect" sound before restarting the whole cycle once the player has powered back on.



    I am connecting the player through an Intel X79 Chipset motherboard (Gigabyte GA-X79-UD3) to Windows 7 Pro 64-bit. The player used to work fine the first time I connected it in MSC mode, showing up as an external drive; the issue only appears when subsequently connecting it again. This can be reproduced: uninstalling the standard Windows mass storage driver (USBSTOR.SYS) from the device manager while the device is visible there, then reconnecting the device, the driver is automatically reinstalled and the device remains visible. After disconnecting and reconnecting it, the problem occurs once more. In MTP mode, driver installation fails in the first place, but that might be due to other reasons. The problem is the same: as soon as the device is connected to the computer, Windows disconnects it again.



    It is not a problem with the player, since the issue does not occur on another system running the exact same operating system. It is also not a problem with the USB controller, since the issue is the same on both the Intel USB 2.0 and the Fresco Logic FL1009 USB 3.0 controller ports. I have also not had the problem with any other drive so far.



    Among the things I have tried so far:




    • Disabling USB legacy mode in BIOS

    • Disabling energy-saving power down for all USB controllers in Windows' device manager

    • Removing and reinstalling USB controller drivers

    • Restoring the player to factory defaults


    None of these made a difference. I would be very grateful for any hints on what else to try.



    Edit: Here is another new hint; I found out that when I connect the drive before booting Windows, it is available in Windows Explorer as it should, and does not automatically disconnect. If I remove and reconnect it though, the infinite connect/disconnect-loop starts anew.










    share|improve this question



























      0












      0








      0








      I am having a problem with Windows 7 x64 consistently disconnecting one specific USB mass storage drive immediately after it is connected. The drive in question is a Cowon C2 digital music player which works both in MSC (mass storage controller) or MTP (Media Transfer Protocol) modes, i.e. there are no device-specific drivers needed/available. The basic issue is the same in both MSC and MTP modes.



      When I connect the player, Windows plays the "USB connect" sound and the device appears (under its correct name) in the device manager, but it never appears as a drive. The player itself displays "USB Connected" for a split-second before reporting that it has been disconnected again. Since the player, by design, reboots after it has been disconnected, Windows plays the "USB disconnect" sound before restarting the whole cycle once the player has powered back on.



      I am connecting the player through an Intel X79 Chipset motherboard (Gigabyte GA-X79-UD3) to Windows 7 Pro 64-bit. The player used to work fine the first time I connected it in MSC mode, showing up as an external drive; the issue only appears when subsequently connecting it again. This can be reproduced: uninstalling the standard Windows mass storage driver (USBSTOR.SYS) from the device manager while the device is visible there, then reconnecting the device, the driver is automatically reinstalled and the device remains visible. After disconnecting and reconnecting it, the problem occurs once more. In MTP mode, driver installation fails in the first place, but that might be due to other reasons. The problem is the same: as soon as the device is connected to the computer, Windows disconnects it again.



      It is not a problem with the player, since the issue does not occur on another system running the exact same operating system. It is also not a problem with the USB controller, since the issue is the same on both the Intel USB 2.0 and the Fresco Logic FL1009 USB 3.0 controller ports. I have also not had the problem with any other drive so far.



      Among the things I have tried so far:




      • Disabling USB legacy mode in BIOS

      • Disabling energy-saving power down for all USB controllers in Windows' device manager

      • Removing and reinstalling USB controller drivers

      • Restoring the player to factory defaults


      None of these made a difference. I would be very grateful for any hints on what else to try.



      Edit: Here is another new hint; I found out that when I connect the drive before booting Windows, it is available in Windows Explorer as it should, and does not automatically disconnect. If I remove and reconnect it though, the infinite connect/disconnect-loop starts anew.










      share|improve this question
















      I am having a problem with Windows 7 x64 consistently disconnecting one specific USB mass storage drive immediately after it is connected. The drive in question is a Cowon C2 digital music player which works both in MSC (mass storage controller) or MTP (Media Transfer Protocol) modes, i.e. there are no device-specific drivers needed/available. The basic issue is the same in both MSC and MTP modes.



      When I connect the player, Windows plays the "USB connect" sound and the device appears (under its correct name) in the device manager, but it never appears as a drive. The player itself displays "USB Connected" for a split-second before reporting that it has been disconnected again. Since the player, by design, reboots after it has been disconnected, Windows plays the "USB disconnect" sound before restarting the whole cycle once the player has powered back on.



      I am connecting the player through an Intel X79 Chipset motherboard (Gigabyte GA-X79-UD3) to Windows 7 Pro 64-bit. The player used to work fine the first time I connected it in MSC mode, showing up as an external drive; the issue only appears when subsequently connecting it again. This can be reproduced: uninstalling the standard Windows mass storage driver (USBSTOR.SYS) from the device manager while the device is visible there, then reconnecting the device, the driver is automatically reinstalled and the device remains visible. After disconnecting and reconnecting it, the problem occurs once more. In MTP mode, driver installation fails in the first place, but that might be due to other reasons. The problem is the same: as soon as the device is connected to the computer, Windows disconnects it again.



      It is not a problem with the player, since the issue does not occur on another system running the exact same operating system. It is also not a problem with the USB controller, since the issue is the same on both the Intel USB 2.0 and the Fresco Logic FL1009 USB 3.0 controller ports. I have also not had the problem with any other drive so far.



      Among the things I have tried so far:




      • Disabling USB legacy mode in BIOS

      • Disabling energy-saving power down for all USB controllers in Windows' device manager

      • Removing and reinstalling USB controller drivers

      • Restoring the player to factory defaults


      None of these made a difference. I would be very grateful for any hints on what else to try.



      Edit: Here is another new hint; I found out that when I connect the drive before booting Windows, it is available in Windows Explorer as it should, and does not automatically disconnect. If I remove and reconnect it though, the infinite connect/disconnect-loop starts anew.







      windows-7 usb-flash-drive mp3-player






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Oct 16 '12 at 0:26







      Daniel Saner

















      asked Oct 15 '12 at 22:50









      Daniel SanerDaniel Saner

      486518




      486518






















          1 Answer
          1






          active

          oldest

          votes


















          0














          It looks like the driver was messed with by something. What you should do is try and install the official drivers from the manufacturer's website. If you want to check if it is a hardware issue, consider testing it with an ubuntu LiveCD



          Other things to try:




          1. Start into safe mode: KB Article

          2. Try automated registry repairs: Advanced SystemCare

          3. All out system restore (BACKUP!!): Guide






          share|improve this answer


























          • As stated in my question, there is no driver, the device works as a standard USB mass storage device. And as also stated, it is not a hardware issue since the device connects fine to other Windows 7 systems.

            – Daniel Saner
            Oct 15 '12 at 22:58











          • Sorry, by hardware I meant on the motherboard, or maybe it could just be windows 7... You should give the livecd a shot because that will confirm if it is windows or the board.

            – Wijagels
            Oct 15 '12 at 23:08











          • By your most recent edit it looks more like your copy of windows 7 may have been dropped on it's head.

            – Wijagels
            Oct 15 '12 at 23:09











          • Works on a Live Ubuntu, as expected since it also works on different Win7 systems. Rather than Windows 7 itself I am suspecting some other application or driver interfering. I would sure love to know a way to check that... I have changed absolutely nothing, hardware or software, between now and back when it used to work.

            – Daniel Saner
            Oct 15 '12 at 23:16






          • 1





            Have you tried a system restore? (Make backups first!!!) Certain applications, ahem, microsoft, tend to do background things that can sometimes make a mistake and mess with things. Sometimes registry cleaners such as Advanced SystemCare can fix some problems. Try out a restore only if you have the time and the backups. Good thing it's a software fault and not a hardware issue! This shouldn't cost a cent to fix. EDIT: Also try safe mode, enable startup applications 1 at a time KB: link

            – Wijagels
            Oct 15 '12 at 23:22














          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',
          autoActivateHeartbeat: false,
          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%2f488195%2fwindows-7-immediately-disconnects-a-usb-drive%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









          0














          It looks like the driver was messed with by something. What you should do is try and install the official drivers from the manufacturer's website. If you want to check if it is a hardware issue, consider testing it with an ubuntu LiveCD



          Other things to try:




          1. Start into safe mode: KB Article

          2. Try automated registry repairs: Advanced SystemCare

          3. All out system restore (BACKUP!!): Guide






          share|improve this answer


























          • As stated in my question, there is no driver, the device works as a standard USB mass storage device. And as also stated, it is not a hardware issue since the device connects fine to other Windows 7 systems.

            – Daniel Saner
            Oct 15 '12 at 22:58











          • Sorry, by hardware I meant on the motherboard, or maybe it could just be windows 7... You should give the livecd a shot because that will confirm if it is windows or the board.

            – Wijagels
            Oct 15 '12 at 23:08











          • By your most recent edit it looks more like your copy of windows 7 may have been dropped on it's head.

            – Wijagels
            Oct 15 '12 at 23:09











          • Works on a Live Ubuntu, as expected since it also works on different Win7 systems. Rather than Windows 7 itself I am suspecting some other application or driver interfering. I would sure love to know a way to check that... I have changed absolutely nothing, hardware or software, between now and back when it used to work.

            – Daniel Saner
            Oct 15 '12 at 23:16






          • 1





            Have you tried a system restore? (Make backups first!!!) Certain applications, ahem, microsoft, tend to do background things that can sometimes make a mistake and mess with things. Sometimes registry cleaners such as Advanced SystemCare can fix some problems. Try out a restore only if you have the time and the backups. Good thing it's a software fault and not a hardware issue! This shouldn't cost a cent to fix. EDIT: Also try safe mode, enable startup applications 1 at a time KB: link

            – Wijagels
            Oct 15 '12 at 23:22


















          0














          It looks like the driver was messed with by something. What you should do is try and install the official drivers from the manufacturer's website. If you want to check if it is a hardware issue, consider testing it with an ubuntu LiveCD



          Other things to try:




          1. Start into safe mode: KB Article

          2. Try automated registry repairs: Advanced SystemCare

          3. All out system restore (BACKUP!!): Guide






          share|improve this answer


























          • As stated in my question, there is no driver, the device works as a standard USB mass storage device. And as also stated, it is not a hardware issue since the device connects fine to other Windows 7 systems.

            – Daniel Saner
            Oct 15 '12 at 22:58











          • Sorry, by hardware I meant on the motherboard, or maybe it could just be windows 7... You should give the livecd a shot because that will confirm if it is windows or the board.

            – Wijagels
            Oct 15 '12 at 23:08











          • By your most recent edit it looks more like your copy of windows 7 may have been dropped on it's head.

            – Wijagels
            Oct 15 '12 at 23:09











          • Works on a Live Ubuntu, as expected since it also works on different Win7 systems. Rather than Windows 7 itself I am suspecting some other application or driver interfering. I would sure love to know a way to check that... I have changed absolutely nothing, hardware or software, between now and back when it used to work.

            – Daniel Saner
            Oct 15 '12 at 23:16






          • 1





            Have you tried a system restore? (Make backups first!!!) Certain applications, ahem, microsoft, tend to do background things that can sometimes make a mistake and mess with things. Sometimes registry cleaners such as Advanced SystemCare can fix some problems. Try out a restore only if you have the time and the backups. Good thing it's a software fault and not a hardware issue! This shouldn't cost a cent to fix. EDIT: Also try safe mode, enable startup applications 1 at a time KB: link

            – Wijagels
            Oct 15 '12 at 23:22
















          0












          0








          0







          It looks like the driver was messed with by something. What you should do is try and install the official drivers from the manufacturer's website. If you want to check if it is a hardware issue, consider testing it with an ubuntu LiveCD



          Other things to try:




          1. Start into safe mode: KB Article

          2. Try automated registry repairs: Advanced SystemCare

          3. All out system restore (BACKUP!!): Guide






          share|improve this answer















          It looks like the driver was messed with by something. What you should do is try and install the official drivers from the manufacturer's website. If you want to check if it is a hardware issue, consider testing it with an ubuntu LiveCD



          Other things to try:




          1. Start into safe mode: KB Article

          2. Try automated registry repairs: Advanced SystemCare

          3. All out system restore (BACKUP!!): Guide







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Oct 15 '12 at 23:28

























          answered Oct 15 '12 at 22:55









          WijagelsWijagels

          1187




          1187













          • As stated in my question, there is no driver, the device works as a standard USB mass storage device. And as also stated, it is not a hardware issue since the device connects fine to other Windows 7 systems.

            – Daniel Saner
            Oct 15 '12 at 22:58











          • Sorry, by hardware I meant on the motherboard, or maybe it could just be windows 7... You should give the livecd a shot because that will confirm if it is windows or the board.

            – Wijagels
            Oct 15 '12 at 23:08











          • By your most recent edit it looks more like your copy of windows 7 may have been dropped on it's head.

            – Wijagels
            Oct 15 '12 at 23:09











          • Works on a Live Ubuntu, as expected since it also works on different Win7 systems. Rather than Windows 7 itself I am suspecting some other application or driver interfering. I would sure love to know a way to check that... I have changed absolutely nothing, hardware or software, between now and back when it used to work.

            – Daniel Saner
            Oct 15 '12 at 23:16






          • 1





            Have you tried a system restore? (Make backups first!!!) Certain applications, ahem, microsoft, tend to do background things that can sometimes make a mistake and mess with things. Sometimes registry cleaners such as Advanced SystemCare can fix some problems. Try out a restore only if you have the time and the backups. Good thing it's a software fault and not a hardware issue! This shouldn't cost a cent to fix. EDIT: Also try safe mode, enable startup applications 1 at a time KB: link

            – Wijagels
            Oct 15 '12 at 23:22





















          • As stated in my question, there is no driver, the device works as a standard USB mass storage device. And as also stated, it is not a hardware issue since the device connects fine to other Windows 7 systems.

            – Daniel Saner
            Oct 15 '12 at 22:58











          • Sorry, by hardware I meant on the motherboard, or maybe it could just be windows 7... You should give the livecd a shot because that will confirm if it is windows or the board.

            – Wijagels
            Oct 15 '12 at 23:08











          • By your most recent edit it looks more like your copy of windows 7 may have been dropped on it's head.

            – Wijagels
            Oct 15 '12 at 23:09











          • Works on a Live Ubuntu, as expected since it also works on different Win7 systems. Rather than Windows 7 itself I am suspecting some other application or driver interfering. I would sure love to know a way to check that... I have changed absolutely nothing, hardware or software, between now and back when it used to work.

            – Daniel Saner
            Oct 15 '12 at 23:16






          • 1





            Have you tried a system restore? (Make backups first!!!) Certain applications, ahem, microsoft, tend to do background things that can sometimes make a mistake and mess with things. Sometimes registry cleaners such as Advanced SystemCare can fix some problems. Try out a restore only if you have the time and the backups. Good thing it's a software fault and not a hardware issue! This shouldn't cost a cent to fix. EDIT: Also try safe mode, enable startup applications 1 at a time KB: link

            – Wijagels
            Oct 15 '12 at 23:22



















          As stated in my question, there is no driver, the device works as a standard USB mass storage device. And as also stated, it is not a hardware issue since the device connects fine to other Windows 7 systems.

          – Daniel Saner
          Oct 15 '12 at 22:58





          As stated in my question, there is no driver, the device works as a standard USB mass storage device. And as also stated, it is not a hardware issue since the device connects fine to other Windows 7 systems.

          – Daniel Saner
          Oct 15 '12 at 22:58













          Sorry, by hardware I meant on the motherboard, or maybe it could just be windows 7... You should give the livecd a shot because that will confirm if it is windows or the board.

          – Wijagels
          Oct 15 '12 at 23:08





          Sorry, by hardware I meant on the motherboard, or maybe it could just be windows 7... You should give the livecd a shot because that will confirm if it is windows or the board.

          – Wijagels
          Oct 15 '12 at 23:08













          By your most recent edit it looks more like your copy of windows 7 may have been dropped on it's head.

          – Wijagels
          Oct 15 '12 at 23:09





          By your most recent edit it looks more like your copy of windows 7 may have been dropped on it's head.

          – Wijagels
          Oct 15 '12 at 23:09













          Works on a Live Ubuntu, as expected since it also works on different Win7 systems. Rather than Windows 7 itself I am suspecting some other application or driver interfering. I would sure love to know a way to check that... I have changed absolutely nothing, hardware or software, between now and back when it used to work.

          – Daniel Saner
          Oct 15 '12 at 23:16





          Works on a Live Ubuntu, as expected since it also works on different Win7 systems. Rather than Windows 7 itself I am suspecting some other application or driver interfering. I would sure love to know a way to check that... I have changed absolutely nothing, hardware or software, between now and back when it used to work.

          – Daniel Saner
          Oct 15 '12 at 23:16




          1




          1





          Have you tried a system restore? (Make backups first!!!) Certain applications, ahem, microsoft, tend to do background things that can sometimes make a mistake and mess with things. Sometimes registry cleaners such as Advanced SystemCare can fix some problems. Try out a restore only if you have the time and the backups. Good thing it's a software fault and not a hardware issue! This shouldn't cost a cent to fix. EDIT: Also try safe mode, enable startup applications 1 at a time KB: link

          – Wijagels
          Oct 15 '12 at 23:22







          Have you tried a system restore? (Make backups first!!!) Certain applications, ahem, microsoft, tend to do background things that can sometimes make a mistake and mess with things. Sometimes registry cleaners such as Advanced SystemCare can fix some problems. Try out a restore only if you have the time and the backups. Good thing it's a software fault and not a hardware issue! This shouldn't cost a cent to fix. EDIT: Also try safe mode, enable startup applications 1 at a time KB: link

          – Wijagels
          Oct 15 '12 at 23:22




















          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.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f488195%2fwindows-7-immediately-disconnects-a-usb-drive%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







          Popular posts from this blog

          Список кардиналов, возведённых папой римским Каликстом III

          Deduzione

          Mysql.sock missing - “Can't connect to local MySQL server through socket”