{"id":613,"date":"2016-08-19T23:40:00","date_gmt":"2016-08-20T06:40:00","guid":{"rendered":"https:\/\/kb.terabyteunlimited.com\/kb-articles\/new-driver-signing-uses-sha256-as-required-by-microsoft\/"},"modified":"2021-09-07T15:05:19","modified_gmt":"2021-09-07T22:05:19","slug":"new-driver-signing-uses-sha256-as-required-by-microsoft","status":"publish","type":"lsvr_kba","link":"https:\/\/www.terabyteunlimited.com\/kb\/kb-articles\/new-driver-signing-uses-sha256-as-required-by-microsoft\/","title":{"rendered":"New Driver Signing uses SHA256 as Required by Microsoft"},"content":{"rendered":"

Problem:<\/font><\/strong> <\/p>\r\n

Installing Image for Windows, PHYLock, or TBIMount on versions of Windows 7 or Windows Server 2008 R2 results in an error message that a digitally signed driver is required. The message is displayed after the installation has completed and, in the case of a reboot being necessary, may appear after the option to restart the system has already been selected. Note that on some systems a warning will not be displayed.<\/p>\r\n

This issue does not affect Windows 8.0 or later.<\/p>\r\n

Example error:<\/p>\r\n

\r\n

Windows requires a digitally signed driver
\r\n
\r\n A recently installed program tried to install an unsigned
\r\n driver. This version of Windows requires all drivers to have a
\r\n valid digital signature. The driver is unavailable and the
\r\n program that uses this driver might not work correctly.
\r\n
\r\n Uninstall the program or device that uses this driver and
\r\n check the publisher's support website to get a digitally
\r\n signed driver.\r\n
\r\n
\r\n Driver: phylock
\r\n Service: phylock
\r\n Publisher: TeraByte, Inc.
\r\n Location: C:\Windows\System32...\phylock.sys<\/font><\/p>\r\n <\/blockquote>\r\n

In the case of the phylock.sys driver, booting the system in this state will result in Windows failing to start. In most cases, Windows will boot to the Recovery Environment (WinRE) and perform a Startup Repair, which will use System Restore to return the system to a bootable state. The root cause found would be reported as "Boot critical file ...\phylock.sys is corrupt."<\/p>\r\n

Cause:<\/font><\/strong> <\/p>\r\n

The Windows installation is not updated (Microsoft issued updates to add support for SHA-2 signing and verification functionality in March 2015).<\/p>\r\n

Solution:<\/font><\/strong><\/p>\r\n

There are several options available to resolve this issue:<\/p>\r\n