Search in start button, how to sign in to Microsoft account, select one, if your already signed in, sign out, then back in again and then you might have to do what other man said, also their is a service in Services (Microsoft Account sign on or something like that, may need to start the service. May have to reboot if you started service, and check again to make sure it's running
For driver problems always the developer of those drivers are responsible and to blame! And as Windows 10 is still in extensive testings, using even as many as available drivers within the testing phase, you still could not blame Microsoft for to give the test user the ability even to test those will working or not! If you couldn't accept that, better you use only what's already tested to be working by OTHERS then YOU. And if you do so, the only you could could blame are the other testers and the driver developer, still not the developer of the those OS who put such drivers in the database of available drivers. After the final (RTM) of the OS, you still could blame the developer of those drivers which fails and not the developer of the OS. That you could do only, if you have the proof that the OS developer has modified the driver which has problem and that only, if the Majority of Users that OS having the same problem! If you just one of a low percentage of users who facing the same problems with the same driver, you'll have to find the culprit somewhere else but the OS!
Go to device manager, find the synaptic's driver, right ckick on it and select disable. Then run windows update and see if in installs same driver, if so, in device manager uninstall driver completely from your computer and reboot, it will install something, if it the same driver, Call MS, lol
You're funny. The BSOD "DPC WATCHDOG VIOLATION" is also happening in Windows 8.1. Not a chance I'm taking this risk. I have already did that in Windows 8.1 and it also deleted the default driver and after that I couldn't reinstall any synaptics driver(also failed to reinstall Synaptics driver from Windows Updates but I wouldn't want to install that any way since it will just BSOD) and the touchpad wouldn't work any more. Had to reinstall Windows 8.1 twice because didn't know it was the synaptics driver was causing the "DPC WATCHDOG VIOLATION" BSOD and deleting the driver inside Device Manager.
Most annoying bug I found so far on build 10125. I can't compare 2 files properties from the same folder. If you do right click -> Properties on a file the window freezes and you can only open other Properties dialog if it's from another window. I hope they fixed it already on 10130 build.
There isn't any work around and also not any new or modified driver which which would bypass the 'glitch'! In reality, I didn't need that driver (till now), it just bothers me if there's something shown not working correctly in Device Manager! And since that problem is present a few years already, I don't think it will be solved by Broadcom, and that isn't a problem of Microsoft in any means.
the old ways before i find the driver pack solution and genius i was use the old way like nexus76 told you...you are just go in device manager copy the id of device and paste it in google ...
hehe bro ready the edit my downloaded iso got corrupted during downloading as i used this program megadownloaderapp(dot)blogspot(Dot)in
Thanks. And the link for ISO with SHA1 5e80e5504233d21444d48003795245c224d8ab64, please? WZor or OSBetaArchive? Edit: The MegaDownloader_v1.21.exe installed few programs without my permission. And it changed all my Internet settings.
why you want an link of corrupted .iso that throws error ? do me favour you have "10125.0.150516-2126.FBL_IMPRESSIVE_CLIENTPRO-CORE_OEMRET_X64FRE_EN-US.iso" download quicksfv (google it ) extract iso with winrar so you will get folder with that name and now create .sfv using quicksfv of that folder and upload it so i check CRCs with my folder
if install.wim diff checksums then no point ps. maybe try with torrent & recheck or someone can make a QuickPar files
will try it here is hash of install.wim File install.wim CRC-32: cde4cadf MD4: ec612b5d61e330b94c71da4dc6202ce5 MD5: 6079525436e01c8b2ce1508270cf7710 SHA-1: 999bbc0b06c2c546d47ddd58cc51d605aa46e0a0