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?
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?