After months of development and refinement in collaboration with hardware vendors and software developers, Microsoft is pleased to announce the availability of Shader Model 6.6! Shader Model 6.6 empowers shader authors with new tools for greater flexibility to make existing shaders faster and more versatile as well as to devise all new techniques.
To give Shader Model 6.6 a try, developers will need a few tools. To compile shaders using Shader Model 6.6, you need the latest DirectX Shader Compiler release. To run those compiled shaders, you’ll need the DirectX 12 Agility SDK and the corresponding graphics driver.
Release 390 is an 'Optimal Drivers for Enterprise'(ODE) branch release. ODE branches are designed and tested to provide long-term stability and availability for ISV certification, OEMs, and Enterprise customers.
What’s New in Version R390 U17
This release adds security updates for driver components.
See the NVIDIA Security Bulletin 5172 for details.
Windows 10 Open Issues in Version R390 U17
[Assimilate Scratch]: The application may crash due to a kernel exception in the NVIDIA OpenGL driver. See “Open Issues in Version 392.59” on page 21 of Release Notes for more details.
[Quadro M6000][Quadro Sync]: Unexpected flashing may appear on the display connected to the second GPU.
Please consult your NVIDIA support team for details on resolving this behavior.
[Multi-GPU Mosaic][Quadro Sync]: Application corruption and possible blue-screen crash occurs when enabling WARP while Mosaic and Quadro Sync are enabled.
Use NVCleanstall to install on GeForce Fermi
Security Bulletin: NVIDIA GPU Display Driver - April 2021
NVIDIA has released a software security update for NVIDIA GPU Display Driver. This update addresses issues that may lead to code execution, denial of service, escalation of privileges, and information disclosure.
To protect your system, download and install this software update through the NVIDIA Driver Downloads page.
Go to NVIDIA Product Security.
Crikey, a man needs his sleep, helping is tiring work
You need a non UEFI BIOS motherboard to use some DOS commands, sas2flsh included
Use either the Windows or UEFI boot versions of the command, links in first post should have both versions