Yea, I tried that. I tried extracting the Dell driver and installing it manually. Nothing works. "Microsoft Generic Display Driver" is the best MS can do. Windows 10 is gone from my PC.
It looked that way to me, too, for awhile...until I noticed that 10130 reinstalled that funky CCC2 & the 15.xxxxxxx.3 WDDM 2.0 drivers right over the top of the 15.5 betas I had just installed and which were running fine. Now with 10130, I remove them and install the 15.5's then, inevitably, in a day or two they'll be overwritten by the buggy WDDm 2.0 drivers....mine are crashing the CCC right after boot about 4 out of every 5-6 boots! Going to try and shoehorn the 15.5's in again to see if I can get stability back. It's annoying...but that's part of the deal... Edit: OK, finally achieved stability for the last several hours and a couple of reboots. I got these to install: Drivers 14.502.1014.1001-150526a-184427E CCC 2015.0526.1819.31103 In uninstalled WDDM 2.0 drivers, rebooted, and then renamed WU_CCC2 in C:\AMD & C:\Program Files to WU_CCC2.bak, and installed the above...the 15.5 betas. No crashing CCC for some time, now, which is always nice... The only question is, how long will it last?
We got to win you back, it's probably just this build, and MS was so much counting on you spending big bucks with them, hehe Please come back, you'll be over in Win 8 forums now, weep, weep
With respect to the drivers, I think 10130 is a step backwards. Three cases in point: I have a Dell Latitude E6420 laptop, pure Intel hardware (CPU, Chipset, GPU, Wireless, NIC, etc, all Intel products) and with 10125 installed a few days ago I noticed the following: 1) the wireless driver installed by Windows Update was from April 2015 2) the NIC driver (Intel Gigabit) was from April 2015 3) the GPU driver (HD 3000) was from May 2015 (not even 2 weeks ago) I ended up removing it because I'm just testing Windows 10 when new builds appear. I grabbed 10130 and installed that - please note I don't use VMs for testing so these installs are on the bare metal hardware of the laptop directly - and then discovered: 1) the wireless driver was from April 2014 (a year older) 2) the NIC driver was from June 2014 (10 months older) The HD 3000 driver would not update as the 10125 did, so I rebooted once and hit Windows Update again, nothing found. I mucked around with the OS for a while, discovered some changes I wasn't too happy with (I won't get into details over it), and then rebooted again. After the 3rd or 4th reboot suddenly it started pulling the video driver from Windows Update but... It's a driver dated April 2014 so a full year older than the one that 10125 installed from Windows Update (and yes they're different version numbers - in all the examples the newer drivers are larger version numbers hence being newer). I even reinstalled 10125 an hour ago to check this and again, it downloaded the drivers from Windows Update that are from April and May of 2015 but build 10130 doesn't: it uses drivers almost a year older. Something is pretty seriously borked I'd say. Got rid of both builds and I think I'm done with Windows 10 at this point. I can't find a reason to use it, I can't stand the way it functions, I can't stand how badly it performs compared to Windows 7 on the same hardware in my own testing (it's much worse), and I can't imagine myself using it as a day to day OS even when it's released for free. That's it for me I suppose, I hope the rest of you find some good reasons for using it.
Nope, sorry. I use Win7 on a air gapped PC for HTPC, and Slackware on everything else. Good luck with Win10!
did u leave it like this or did u also unclick the bottom option get drivers for your manufacturer? i did when back to WU and nothing happen tells me i have latest updates.
Got an 0xC1900101 - 0x40017 when I tried to update from 10041. Did a system cleanup before and unplugged all USB devices. Microsoft has really to improve the update process. The OS acts like a sissy in that.