The latest ForceWare NVidia driver adds the driver support (right now, it's exclusive to Maxwell and Kepler-based GPUs, though the driver itself supports all NV GPUs back to 4xx).
You mean, I suppose, that you want to made aware when Microsoft ships to RTM...? These are previews not finals--lots of stuff is very rough yet. Caveat Emptor--but really, I don't get hung up on cosmetics very much. Only thing I didn't like in this build (so far) was the inelasticity of the start menu--but we fixed that with a simple registry tweak already covered on this forum.
Guys, heads up. For some reason 1. CPU core is butchered. Just tried FC4 and it was impossible to maintain stable 60 FPS. MSI AB clearly shows that first core is slacking. Changing power plan to performance didn't help. Does anyone has the same issue? I have Core i7-4790K.
We fixed the start menu by turning the older one back on... I agree, build 9901 was horrifically buggy...been a long time since I dropped my c:\ partition--but 9901 did it to me. Was my own fault, though, for jumping out of officially released preview builds..!
From my personal experience, third step isn't necessary. Setting region to US and adding US language as default is enough.
Cortana requires you to login with a Microsoft Account and doesn't support local accounts. There is no option to supply Cortana with Microsoft Account credentials on a per-app basis like you can, say, the Feedback app. It requires you to switch from a local account. If anyone knows otherwise, please chime in.
Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX] "IsConvergedUpdateStackEnabled"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings] "UxOption"=dword:00000000 It is in the control panel which is still there when right clicking the start button.
Nope, that's just the way it is. I finally bit the bullet and logged in. Surprised that I still login using domain account, and impressed by the amount of stuff it synced over from my Windows Phone.
sfc /scannow goes to about 3% for me before saying "Windows Resource Protection could now perform the requested operation". Anyone know what's up?
After disabling UAC and reverting the Start Menu (and removing all Modern UI apps), Un-converging Windows Update, and figuring out the weird driver issue on my dual-graphics AMD laptop; I'm pretty happy with how things look and perform in the new build, so far anyway. I'm just hoping app/game compatibility goes well.