Ext3Fsd not working in latest Windows 10 because driver is not signed

[pppbb]

Please re-release Ext3Fsd 0.69 with signed driver.

[DaJakerBoss]

Well that's odd because I am using the latest Insider preview, and it works just fine.

Go to your settings, head over to Apps, and go to the Apps & features tab. Select the drop down menu, and change it to "Allow apps from anywhere."

[pppbb]

im using latest official release. i allready had the settings enabled. but during install i have short information that instalation of the driver is blocked because its unsigned. the same with Paragon ext4.

[DaJakerBoss]

https://www.maketecheasier.com/install-unsigned-drivers-windows10/

[necrose99]

https://docs.microsoft.com/en-us/windows.../drivers/devtest/tools-for-signing-drivers
sign the driver as Windows domain admin or ADMIN , you can it will shut it up if you on secure-boot.
it Is an option. www.CACert.org , req key as domain if applicable or import your key and sing, as a local admin.
one way of pushing newrer drivers to users. wsuspackage publisher. , Ex. AMD often has newer radon drivers but if you have secure-boot less you sign them as local admin 800X600 ...

[cdclawson]

From what I can tell (not an expert) the driver is signed, but Windows is refusing to start it anyway. "net start ext2fsd" returns the error:

System error 577 has occurred.

Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

Also, Windows's System log shows an event ID 7000 from Service Control Manager:

The Linux ext2 file system driver service failed to start due to the following error: 
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

This is on Windows 10 Pro x64, version 10.0.17134.191 with Secure Boot enabled.

I read on another site that kernel drivers must be signed by Microsoft - normal code signing is not enough. I'm not sure whether that's the problem here. Anyway, I will try signing it as Admin and see what happens.

[DaJakerBoss]

You can turn off driver verification in Windows 10 to install the driver. There's guides on Google and I wish i could get them but I'm a bit busy right now.

On Mon, Aug 6, 2018 at 7:56 PM, Mogster ***@***.***> wrote: From what I can tell (not an expert) the driver is signed, but Windows is refusing to start it anyway. "net start ext2fsd" returns the error: System error 577 has occurred. Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. Also, Windows's System log shows an event ID 7000 from Service Control Manager: The Linux ext2 file system driver service failed to start due to the following error: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. This is on Windows 10 Pro x64, version 10.0.17134.191 with Secure Boot enabled. I read on another site that kernel drivers must be signed by Microsoft - normal code signing is not enough. I'm not sure whether that's the problem here. Anyway, I will try signing it as Admin and see what happens. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#19 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Afs4z8RQ0BpE9pF15wDLM-MA7KQQOLD3ks5uOOXNgaJpZM4RNnJw> .

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

[SwooshyCueb]

All I had to do was turn off secure boot and then it worked fine.

[tcladin]

All I had to do was turn off secure boot and then it worked fine.

Hi, exist some solution do not need turn off secure boot?
I worry that turn off it on Dell Optiplex3060 with win10 and Kubuntu18.04 both 64bit, will have some negative consequence.

[stevenrutherford]

If you are building your own software, or using software someone else built that does not have certs that root up through Microsoft, you won't be able to install that driver while signed driver enforcement is enabled. This is the point.

I don't actually have signed driver enforcement enabled, so I'm not sure if this particular build is signed or not, but it's the only version I can find that was built by Matt Wu: https://sourceforge.net/projects/ext2fsd/

For info on installing unsigned test drivers, go here: https://docs.microsoft.com/en-us/windows-hardware/drivers/install/installing-an-unsigned-driver-during-development-and-test

Disabling secure boot is probably fine, but notably makes you more prone to malware that persists through your boot chain. You can always re-enable it later.

[junalmeida]

@matt-wu What is needed to have the driver signed?

[Ultrafeel]

Hi, exist some solution do not need turn off secure boot?

see point 1, but only one load

https://www.maketecheasier.com/install-unsigned-drivers-windows10/

As soon as you select it, your system will boot into Windows. You can then install unsigned drivers in Windows without issues. After installing, restart your system, and the Driver Signature Enforcement will be automatically enabled from the next reboot.

P.S. 68 version driver can be installed without problems even by hand(Copy the driver over the v69 one in \windows\system32\drivers\ext2fsd.sys).