ZzmadzZ
100+ Head-Fier
- Joined
- Dec 17, 2014
- Posts
- 455
- Likes
- 213
I am still having issues caused by the IBASSO DX200!! I would warn any one on here thinking of purchasing one or dealing with Advanced MP3 players(they sell on amazon in the UK) to tread extremely carefully!!
some background Received DX200 was not seen by any PCs in my house(little circle would never bring up option screen of USB for charging file transfer etc) was Advised by "IBASSO" to try another USB type C lead...joy!!! DX200 worked, however the next morning when i tried to take some flac files off my other players(Fiio Questyle) none of these players were seen by my PC ...i then spent two days trying to resolve this issue(on windows/PC forums etc).
As i was getting no joy i was told to pursue the Trader not IBASSO which i did via recorded delivery letter sent out to AMP3 players on the 20th of April i had no reply from them(email or letter) so by Sunday the 29th i tried contacting them again through Amazon, which they responded to today Monday the 30th and arranged to speak to them via a phone call inn which they have claimed "As they did not advise me to try another USB C lead that there is no line of Proof that the DX200 caused my PC issues!!! "
I am absolutely fuming ..everything worked fine i could change flac files from player Fiio to Questyle(and from server to either) with no problems until the DX200 entered the mix but now i am left with a PC that will not see either DAPs it still sees the DX200 though.
So even if i send the IBASSO back get a full refund i will be left with a PC that i can no longer transfer files to my other Players...Thanks a Bunch IBASSO and Advanced MP£ players
Erm... from your issue. It seems that there is an issue with windows and not iBasso DX200...
Whatever you described cannot be caused by DX200......
I will say restart your computer, and go to your device manager, plug in your other daps, check if the pc recognises it when you plug them in. If it says unknown device right click on it, select properties and update the driver....
Seems like it’s a windows driver issue.