-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows 10 build 2004: Cannot Start Ext2Fsd service #35
Comments
exactly the same problem, disabling digital signature verification is not an option ((( |
@rah66 It is quite weird because on one machine I have which works fine, Ext2Fsd was installed when it was on Windows 10 version 1903 and even now, having updated to 2004, it still works and runs fine. However, on the other machine which was already on version 2004 when I installed Ext2Fsd, the service just will not start at all. |
I cannot start the Ext2fsd service. The event viewer reports. "The digital signature cannot be verified." |
insaneous! |
I once encountered the same issue - but simply installing version 0.68 should fix it. |
I've installed V0.69 on two computers, both now running Windows 10 build 2004.
On one machine, the Ext2Fsd install works fine and I can connect, read and write to an EXT4 USB drive. However, on the other Windows 10 machine, I just cannot get to the same state - the volume will not appear as an EXT4 drive and therefore I'm being asked by Windows to format the disk.
On the problem machine, when I check in the Ext2 Volume Manager, the Service Management states that "Ext2Fsd is NOT started" yet Windows Services indicates differently. If I then use Powershell to query the "Ext2Fsd" service, it is marked as "Stopped" yet trying to manually start the service also fails.
If I check Event Viewer, the Error is that "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." Which is odd given that the other Windows 10 machine works fine without issue.
Has anyone run into this before?
The text was updated successfully, but these errors were encountered: