Android_808
Member
Thread Starter
- Joined
- Mar 5, 2016
- Messages
- 6
- Likes
- 1
It has been noted on several sites that MS are now going to be enforcing the previously stated requirement of sending them kernel mode drivers to be signed.
It doesn't affect anything on installations upgrading to the new build to stop existing setups from working but will on clean installs of build 1607 onwards. If signed by a valid cross-signing certificate issued prior to July 29th, 2015, drivers will continue to pass signing checks. Boot drivers are not blocked but may be in future versions. If you turn off secure boot you can still use unsigned drivers.
Is this going to cause issues in anyway for Redfox/Elby products?
https://blogs.msdn.microsoft.com/wi...r-signing-changes-in-windows-10-version-1607/
It doesn't affect anything on installations upgrading to the new build to stop existing setups from working but will on clean installs of build 1607 onwards. If signed by a valid cross-signing certificate issued prior to July 29th, 2015, drivers will continue to pass signing checks. Boot drivers are not blocked but may be in future versions. If you turn off secure boot you can still use unsigned drivers.
Is this going to cause issues in anyway for Redfox/Elby products?
https://blogs.msdn.microsoft.com/wi...r-signing-changes-in-windows-10-version-1607/