Before the keynote, I had a theory that it would be included but, after the announcement, figured that it might be pushed until GDC or BUILD (but I kept an open mind). It is not on any changelog that I can see, and it was not mentioned anywhere in the briefing as potentially being in an upcoming preview build. The interesting part, to me, is how Microsoft pushed DX12 into this release without, you know, telling anyone. I haven't got around to troubleshooting much, but it seems like a weirdly-timed, abrupt hardware failure (BIOS is only reporting half of the RAM installed, iGPU is 'enabled' but without RAM associated to it, etc.). Update: Looks like a stick of RAM (or some other hardware) blew, coincidentally, about 30 minutes after the update finished, while the computer was running, which also confused my UEFI settings. When it came back, my Intel GPU (which worked for a few minutes after the update) refused to be activated, along with the monitor it is attached to. There was not even enough time for a bluescreen. Within a half hour of using it, I suffered an instant power-down. Note: I have already experienced some issues with Build 9926.

No-one needs to know how old my motherboard is… Really, all this means is that one barrier has been lifted, leaving the burden on hardware and software partners (except to release the SDK, that's still Microsoft's responsibility).

At the moment, there has not been any drivers or software released for it, and the SDK is also no-where to be found. Until today, DXDIAG reported DirectX 11 in the Windows 10 Technical Preview. Microsoft has added DirectX 12 with the latest Windows 10 Technical Preview that was released today.

Directx 12 win 10