the latest Ext2Fsd(ext2fsd-0.69) doesn't work after windows 10 --- solved using ext2fsd-0.53 or 0.68

I have the same issue,firstly I thought something going wrong during the installation.
But after trying several times I changed my mind.
As @dd-han said, 0.68 is fine ,but it causes superlock during linux booting.
However 0.69 cannot work properly.It really heart-broken.

Same here, ext4 is broken on 0.69. Couldn't even get it to work by reinstalling 0.68, strangely enough.

It works perfectly for me, and I am using the latest insider preview for Windows 10 and the latest Ext2Fsd. No write privileges, but I can read...

Target partition is a 64-bit EXT4 partition.

​​@DaJakerBoss​​ which win version? Now I am using win 10.0.17074 and ext3fsd 0.69. The issue is still not fixed.

​​@kid1412621​​ The latest Insider Preview (Fast)

​​@DaJakerBoss​​ weird, insider slow here. My Linux portion is ext4. But it shows ext3 in ext3fsd. ?

I am using build 17063 (updating to 17083 as we speak), and I think it identifies it as EXT4, what did you use to make the partition?

@DaJakerBoss I don't make the partition. I just formatted the partition during installing the linux system.
I cannot wait for the latest version to fix this. This issue bothers me for a long time.

What Linux operating system did you install?

​​@DaJakerBoss​​ Ubuntu 17.10

Hmmm... I am using 18.04 dev so that might be it?

​​@DaJakerBoss​​ ? u suggest to update Ubuntu?U think thia bug is duo to Linux?

Umm no I was just saying I had a different version of Ubuntu. Do you have a GPT or MBR partition table.

UPDATE: not only GPT problem

looks like MBR (Disk1) works fine and GPT (Disk0) not working

​​​​

but reproduce fail on my removable storage device...

​​​​

I have an MBR system. If it has to do with the partition table than we have issues.

​​@kid1412621​​ It shows the filesystem as EXT3 in Ext2Mgr also if the driver refuses to mount it. It can be related to incompatible features, such as 64bit. See ​​e7c1142​​ .

If you want to know more about your EXT4 filesystem, you might use debugfs like this: debugfs -R stats PATH_TO_VOLUME .

Feel free to mail to me if you have any inquiries.

Same here, WINDOWS 10 170928, Ubuntu 17.04. Only format dialog?

just to be clear we have tried unsigned drivers boot in Windows, correct

​​…​​

@ngkaho1234 Thanks for reply.But I have no idea how to use this tool.
Could you guys add a wiki page for it?

Hey @DaJakerBoss , I just changed my laptop's motherboard,and reinstalled dual systems(Win 10 and Ubuntu 17.10),still cannot mount ext4 partition properly.

Hey ​​@kid1412621​​ You didn't really have to do all that (and hope you didn't) just so you could mount your ext4. IIRC an update had some issues with 64-bit EXT4 mounting, and had potential to mess up your partition data. The latest update (0.69) should fix that, so make sure you update.

Don't use Ext2Fsd 0.68 or earlier versions with latest Ubuntu or Debian systems. Ext2Fsd 0.68 cannot process EXT4 with 64-BIT mode enabled, then it could corrupt your data. Very sorry for this disaster issue, I'm working on an improvement.

Also, one quick question, are you using an MBR or GPT partition table? I don't know if this would be any cause but I'm collecting info. I will look for more info regarding your situation.

​​@dd-han​​ going back to your comment from earlier, USB and SSD/HDD are handled differently by the system as far as I know. Different drivers and such. I will try to recreate this with my computer at home.

Does anyone have a system that uses different inputs for USB (2.0, 3.0, 3.1/Thunderbolt)? It would be interesting to see if interfacing has any effect on this. I'm going to try SATA and SATA->USB-3 connectors to see myself.

@DaJakerBoss I done that because of fixing hardware issue. I didn't do that for mount ext4 on purpose.
I am using the latest version of Ext3Fsd. And of course,GPT.
If there is possibility to relate to unsigned drivers boot?

Using Ext2fsD 0.69 on Windows 10 build 1803, my system stop booting after installing it. Solved by killing ext2fsd.sys on system32/drivers...

As a workaround for the now dropped 64-bit volume support, it might be worth a try to simply convert the file system to 32-bit using ​​resize2fs -s​​ from a Linux system. Worked fine for my 2 TB drive; with the default block size of 4 KiB, 64-bit block counts would only really be necessary for ≥16 TB drives.

Should not be easier and better compat to ignore 64-bit enabled partitions? Anyways, I'll check if it is the cause, because I have the same HD config on my desktop (Win10 + Deb8 Ext4) and it worked fine.

​​…​​

​​https://blogs.msdn.microsoft.com/commandline/2019/02/15/whats-new-for-wsl-in-windows-10-version-1903/​​

Does this mean windows have native support for ext4?

Seems no. As they clearly mentioned that the functionality was implemented with 9p protocol.

​​…​​

What is 9p protocol?

​​…​​

I have the same issues on Windows 10 Pro as pointed out by others, solved using ​​ext2fsd-0.53​​.