to get 10 bit color you have to install earlier driver...the stock win 10 driver downloaded wih win update also works...
After updating my laptop Windows 10 to 1803, my USB headphones are NOT working automatically. I need to disable speakers in "Manage audio devices" only then my headphones work. No use if I try to make any device as "default". Does anyone have same/similar issue? Appreciate any help resolving it, Many thanks!
after you plug you usb headphone uninstall the driver in device management...and unplug...restart and plug again...or update your usb driver
Could anyone please advise on How to revert back to 1709? I don't have c:\windows.old folder... "go back to the previous version of windows 10" option also missing
Simply reinstall 1709. You can do a new clean installation (recommended), but you can also do so using the "restore" or "refresh" method of Windows. If you use this method, you will have to disable automatic updates, otherwise your Windows will notify you that it has found a newer version and will automatically install it. It I tried personally and it works excellently. Of course you need to have the previous version, i.e. 1709. If you do not have it, at first You must get it, then should make DVD or USB and use it. Or if You want, You can use refresh function, ie You can install from hard drive using refresh function, but as I said, be careful, You may get the latest, ie 1803 version, if You enable updates during installation process.
Reverting back means a simple mouse click and 10min later he is back from 1803 to 1709, from which he probably upgraded to 1803. "ResetPC" and "start fresh" don't offer to reinstall a previous installed OS, they re-install the current OS, which he doesn't want. Not a bug/issue
err I regret bitterly by stating that the 1803 version is the best version of Windows so far because after using only 3 days I have discovered several bugs that do not pay to be detailing anything here so I am returning to EnterpriseS faster than Usain Bolt...although this version also has some problems but they are liable to solve
Obscure bug I just ran into today.. In 1709, on a PC with a Pro for Workstations license in firmware, one could install straight-up Win10 Pro, activate it against the PfW key, and it would turn into PfW seamlessly. In 1803 this doesn't seem to work, it gives the generic "Can't find activation server/DNS/blocked/used already" messages. To get this to work I ended up using the built-in tool "changepk.exe" which lets me specify the key (on the command line fortunately) and it then turns the install into PfW and activates it. A workaround, but yet another branch in my activation batch file. Sigh.. Oh, and it's a bug, because on the VLSC site they very clearly say PfW keys can be used to activate Pro, but using normal methods, that doesn't work.
What pfw key activated 1709 pro-ws, up till the current CU it wasn't even supported by updates, only 16251<>16288 (pre rs3) range could be activated by the product.ini key, so you must be talking about other keys.
Maybe my post was confusing. In 1709, one could take a PfW-in-firmware'd laptop, like the Dell Precision 7720 mobile workstation. They could flatten the drive. They could then install Windows 10 **PRO** on it. They could then activate it, either via the GUI or with slmgr (using the PfW key pulled with oem-dm or whatever). It would then take that Win10 **PRO** install, turn it into Win10 PfW, and activate it. It did all this without even so much of any feedback it had done so.
After 1803 upgrade on several different brand notebooks, I have noticed that quite a few of them now fails to turn off. They all restart properly. It's only when you choose Shut Down that they fail. Windows seems to do the ordinary shut down, and the screen goes blue with the typical "Shutting Down" text and after a few seconds the screen goes black. But the machine then never shuts down completely. This only happens if the machine use EFI boot on a GPT disk. Regular BIOS mode og MBR formatted disks are no problem. But as you all know, going back again from EFI to MBR is hardly possible. Strange thing is that booting into SAFE-mode doesn't help. The affected machines still fails to shut down. Even when booting from a USB installation stick, it fails to shut down as long as the selected boot is EFI. Has anyone detected if MS has noticed and officially recognized this as a bug?
i am using amd....my gpu broke 10 bit with latest drivrr that said 1803 compatible...but once i used older driver works
I'm seeing this with a couple of machines. I'm attributing it to drivers. On my gaming rig Win10 originally did this but after some driver updates it suddenly stopped doing it. I have an old Lenovo tower doing it that I am also attributing to old drivers that I have no updates for. A quick fix is to disable the Fast Boot thing. This has always made Win10 properly shut down on these machines.