Welcome Guest ( Log In | Register )

Outline · [ Standard ] · Linear+

 W10, Drivers

views
     
acbc
post May 10 2016, 08:54 AM

Look at all my stars!!
*******
Senior Member
9,048 posts

Joined: Jan 2003
U need USB 3.0 and Bluetooth drivers. There are no native support under W10.
acbc
post May 10 2016, 09:13 AM

Look at all my stars!!
*******
Senior Member
9,048 posts

Joined: Jan 2003
QUOTE(horns @ May 10 2016, 09:07 AM)
just use the latest drivers from gpu manufacturer. use ddu to clean the old drivers in safe mode first.
uh? what do you mean? usb3 and bluetooth drivers are provided natively afaik
*
And sux. Need to use third party. USB 3.0 also crap. Devices kept disconnecting. Also need third party. Native ones useless.
acbc
post May 10 2016, 09:24 AM

Look at all my stars!!
*******
Senior Member
9,048 posts

Joined: Jan 2003
QUOTE(horns @ May 10 2016, 09:21 AM)
ok. a simple 'fix' to frequent disconnecting devices is to use a usb 2.0 hub between the device and your computer.
*
What a useless solution! Only proves USB 3.0 support is broken under W10. No problem under W7.
acbc
post May 10 2016, 09:29 AM

Look at all my stars!!
*******
Senior Member
9,048 posts

Joined: Jan 2003
QUOTE(horns @ May 10 2016, 09:27 AM)
yeah ok it's up to you hehe
*
I'll stick to my Mac full time instead of part time. At least El Capitan has full native USB 3.0 support. Fast and stable. And works! MS and Nadella can bury themselves. As for my W10 machine, already downgraded back to W7. So much better.
acbc
post May 23 2016, 07:54 AM

Look at all my stars!!
*******
Senior Member
9,048 posts

Joined: Jan 2003
QUOTE(TruboXL @ May 23 2016, 01:34 AM)
lel what you talking about? Windows 7 didn't even have native USB3 support either. Can confirm you cannot install Windows 7 directly over USB3 ports without additional drivers...
Just asking... Your nvidia GPU is?? If you look up Device Manager does it say something like 3D controller or VGA controller?
*
W7 has vendor support for USB 3.0 and stable for months. W10 none. Devices will disconnect randomly. It is a known fault. Check the MS forums. No proper solution apart from system restore. Worthless OS.
acbc
post May 24 2016, 05:07 PM

Look at all my stars!!
*******
Senior Member
9,048 posts

Joined: Jan 2003
QUOTE(TruboXL @ May 24 2016, 04:57 PM)
right... but m$ft is getting rid of win7 and win8.x so maybe will focus more w10 soon...
*
I moved to the Mac officially last March after 25 years with Windows. Fed up with W10. Will keep W7 running for as long as possible.
acbc
post May 26 2016, 03:10 PM

Look at all my stars!!
*******
Senior Member
9,048 posts

Joined: Jan 2003
QUOTE(chocobo7779 @ May 26 2016, 02:52 PM)
acbc Go blame the driver maker - Microsoft is no way responsible for this issue.  icon_idea.gif

The problem is hardware and software developers are glacial to changes (i.e. seriously can't they dedicate some resources to make a decent Windows driver)?  shakehead.gif

Only large hardware makers (such as AMD and nVidia) are able to do that - so why can't those smaller developers can do that?  doh.gif

I'm looking at TP-Link, especially.  shakehead.gif
*
Hardware maker is Intel. Blame who again?

Anyway, I've moved out of Windows for life. Fed up. Too much troubleshoot and less work done. Thanks for Nadella for forcing me to change.

 

Change to:
| Lo-Fi Version
0.0166sec    0.74    6 queries    GZIP Disabled
Time is now: 11th December 2025 - 06:52 AM