Page 1 of 1

Partition undeleted, then UFD not recognized in USB 3.0 port

PostPosted: Mon Nov 02, 2015 6:44 pm
by FValley
After BING 1.85 undeleted a partition on a USB 3.0 flash drive, Windows 8 can not recognize the UFD in a USB 3.0 port, but can in a USB 2.0 port.

Using BootIt Next Generation v.1.85, with Windows 8 (not 8.1) Pro 64-bit, and SanDisk Extreme USB 3.0 64GB Flash Drive.

New UFD comes from the factory with one partition and FAT32 format.

Inserted new UFD in USB 3.0 port of computer #1 running Windows 8. Windows recognized it and assigned drive letter.

Decided to repartition the new UFD with 2 partitions, and reformat with NTFS. Used Windows Disk Management to delete the UFD's single factory partition that had FAT32 format.

However, after the partition was deleted, then decided not to repartition or reformat.

Since Disk Management can't undelete a deleted partition, needed to use 3rd party software that could.

Removed the UFD from USB 3.0 port on computer #1, and inserted it into USB 2.0 port on computer #2 that doesn't support USB 3.0.

In computer #2, ran BING 1.85 to undelete the deleted partition on the UFD, and was successful.

Reinserted the UFD with the now undeleted partition into USB 3.0 port on computer #1, and the UFD's blue LED turned on.

However, Windows Disk Management and Diskpart did not recognize the UFD in the USB 3.0 port.

Removed the UFD from USB 3.0 port on computer #1, and inserted it in a USB 2.0 port also on computer #1.

Windows Disk Management and Diskpart then recognized the UFD in the USB 2.0 port, although they didn't when it was in a USB 3.0 port after the partition deletion and undeletion.

The UFD's disk and partition information shown by Disk Management while in the USB 2.0 port after the partition deletion and undeletion was the same as that shown when the UFD was first in the USB 3.0 port before the partition deletion. For example, partition capacity 58.42 GB and file system FAT32 were shown both before and after the partition deletion and undeletion.

To summarize, after the UFD's factory partition was deleted by Windows Disk Management while in a USB 3.0 port, and then undeleted in a USB 2.0 port by BootIt NG 1.85, Windows 8 can only recognize it when the UFD is in a USB 2.0 port, and can no longer see it when it's in a USB 3.0 port.

How can this be fixed so Windows 8 can again see the UFD in a USB 3.0 port?

Thank you.

Re: Partition undeleted, then UFD not recognized in USB 3.0

PostPosted: Mon Nov 02, 2015 9:47 pm
by TeraByte Support(PP)
You could try doing a DISKPART "clean" on the UFD and then recreate the partition. That will usually fix that type of problem. Save anything off the drive that you want to keep first, though, since it will delete the partition.

Re: Partition undeleted, then UFD not recognized in USB 3.0 port

PostPosted: Mon Nov 02, 2015 11:44 pm
by TeraByte Support
FWIW, you should be using BIBM, not BING (although if it was just
partitioned, it's the same, if non-partitioned, then nothing to really
undelete but BIBM would handle that better).

And the USB2/USB3 doesn't matter as far as the partitioning. There is a
different hardware connection between USB2/3. You may want to try powering
off the system and unplugging (yes actually unplug) it for about 30 seconds.


"FValley" wrote in message news:10538@public.bootitng...

After BING 1.85 undeleted a partition on a USB 3.0 flash drive, Windows 8
can not recognize the UFD in a USB 3.0 port, but can in a USB 2.0 port.




Re: Partition undeleted, then UFD not recognized in USB 3.0

PostPosted: Thu Feb 11, 2016 4:08 pm
by FValley
Thank you for both replies. My apologies for the very long delay for this update.

There was apparently nothing wrong with the SanDisk USB 3.0 UFD.

The problem was Windows 8.

Windows 8 would detect the USB 3.0 UFD the first time it was inserted in a USB 3.0 port, but not subsequently. This problem affected both USB 3.0 ports on the computer. It also occurred with two identical SanDisk USB 3.0 UFDs, one whose factory partition was deleted and then undeleted (as reported in my original post), and a second new UFD that was inserted into the USB 3.0 ports straight from its bubble pack.

After the initial detection, Windows 8 would only detect the UFD if either (1) it was inserted in a USB 3.0 port before Windows 8 was opened, or (2) inserted first in a USB 2.0 port, removed, then inserted in a USB 3.0 port.

However, although the UFD was in a physical USB 3.0 port, when detected, Windows 8 assigned it to a logical USB 2.0 port. The reported connection was USB 2.1, which I believe means a USB 3.0 device in a USB 2.0 port. The port assignment and connection were found using USB Device Tree Viewer 2.5.8 and USBDeview 2.46, both freeware programs.

Neither Windows 8 built-in "Hardware and Devices" troubleshooter nor the Microsoft Fix it for "Hardware devices are not working or are not detected in Windows" (https://support.microsoft.com/en-us/mat ... e_problems) found any problems.

Used Windows 8 Device Manager to check for updates for the Windows 8 built-in Intel USB 3.0 eXtensible Host Controller and USB Root Hub (xHCI) drivers, but it reported that the latest drivers were already installed.

Found no solution on Internet, except for a website that reported Windows 8's built-in USB 3.0 drivers did not work with some USB 3.0 devices, and recommended replacing them with drivers designed for Windows 7. (Intel never released USB 3.0 drivers designed for Windows 8.) This recommendation was for Windows 8 only, and specifically not for 8.1.

Before doing this replacement, Windows 8 suddenly and inexplicably began to correctly recognize the UFD in a physical USB 3.0 port, i.e., the UFD was assigned to a logical USB 3.0 port, and the connection was USB 3.0, not 2.1. Moreover, the UFD could be inserted at any time, so no need to do so before Windows opened, or put it in a USB 2.0 port first.

I don't know what caused the problem, or how it fixed itself, but it hasn't reappeared since.