Doesn't work after windows 10 creators update #14

Barteks2x · 2017-10-27T19:07:10Z

The service refuses to start. This is all I know.

dd-han · 2017-11-22T16:57:50Z

Downgrade to 0.68 will works.

but 0.68 could corrupt your data, so I switch to Paragon ExtFS.

ngkaho1234 · 2017-11-23T02:31:07Z

@dd-han Ext2Fsd 0.69 was released 3 days after the issue was opened. What problem did you encounter with 0.69?

dd-han · 2017-11-23T03:13:18Z

@ngkaho1234 When I install ext2fsd without reboot, Ext2 Volume Manager unable to regcognized my ext4 partitison as following screenshot.

After reboot, Ext2 Volume Manager can regcognized my ext4 partition and Ext2Fsd start success (It fail when Win 10 16299.64 still for Windows Insider only. Maybe reinstall fix that problem).

Then I add driver letter for my ext4 partition. But it unable to show capacity or any infomation in explorer.

If i double click on my ext4 volume (F:), just format dialog.

That's problem I encounter with 0.69, and 0.68 fine.

kid1412621 · 2017-12-02T12:06:17Z

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.

nmlgc · 2017-12-08T00:43:18Z

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

DaJakerBoss · 2017-12-30T18:01:38Z

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.

kid1412621 · 2018-01-29T17:05:53Z

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

DaJakerBoss · 2018-01-29T17:14:38Z

@kid1412621 The latest Insider Preview (Fast)

kid1412621 · 2018-01-30T01:50:12Z

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

DaJakerBoss · 2018-01-30T02:18:18Z

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?

kid1412621 · 2018-01-30T02:58:28Z

@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.

DaJakerBoss · 2018-01-30T15:42:28Z

What Linux operating system did you install?

kid1412621 · 2018-01-30T16:06:14Z

@DaJakerBoss Ubuntu 17.10

DaJakerBoss · 2018-01-30T21:09:48Z

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

kid1412621 · 2018-01-31T02:05:52Z

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

DaJakerBoss · 2018-01-31T13:37:28Z

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

kid1412621 · 2018-02-01T12:43:36Z

@DaJakerBoss

dd-han · 2018-02-03T15:59:03Z

UPDATE: not only GPT problem

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

but reproduce fail on my removable storage device...

DaJakerBoss · 2018-02-04T23:58:00Z

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

ngkaho1234 · 2018-02-13T06:00:26Z

@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.

sonvirgo · 2018-03-18T02:18:51Z

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

DaJakerBoss · 2018-03-18T17:23:50Z

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

…

On Mar 17, 2018 at 9:18 PM, おとめ座ひなたぼっこ ***@***.***> wrote: Same here, WINDOWS 10 170928, Ubuntu 17.04. Only format dialog? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#14 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Afs4zynf4GZTirNbn7iUv2lVNzb4OyPDks5tfcQMgaJpZM4QJfUa> .

kid1412621 · 2018-04-09T15:25:42Z

@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.

DaJakerBoss · 2018-04-09T16:31:10Z

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.

DaJakerBoss · 2018-04-09T16:43:28Z

@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.

kid1412621 · 2018-04-10T02:26:30Z

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

marcosx86 · 2018-07-25T00:47:51Z

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

nmlgc · 2018-07-27T16:49:06Z

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.

marcosx86 · 2018-07-27T16:53:07Z

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.

…

On Fri, Jul 27, 2018 at 1:49 PM Nmlgc ***@***.***> wrote: As a workaround for the now dropped 64-bit volume support, it might be worth a try to simply disable the 64-bit flag using resize2fs with the -s option from a Linux system. Worked fine for my 2 TB drive; with the default block size of 4 KiB, 64-bit blocks would only really be necessary for ≥16 TB drives. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#14 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFCFhvptLF_fW52-MptKg3cCTozYKZtks5uK0SEgaJpZM4QJfUa> .

-- Marcos Silva Cunha Celular: +55 71 91348243 (TIM)

kid1412621 · 2019-02-16T04:50:35Z

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?

ngkaho1234 · 2019-02-16T04:55:46Z

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

…

On Sat, Feb 16, 2019, 12:50 PM kid1412621 ***@***.*** wrote: 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? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#14 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALUjKDGDUUx3QusEKlhqFEVFR5JEh0rxks5vN44cgaJpZM4QJfUa> .

kid1412621 · 2019-02-16T16:45:34Z

What is 9p protocol?

…

On Sat, Feb 16, 2019, 12:55 Ka Ho Ng ***@***.*** wrote: Seems no. As they clearly mentioned that the functionality was implemented with 9p protocol. On Sat, Feb 16, 2019, 12:50 PM kid1412621 ***@***.*** wrote: > > 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? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#14 (comment)>, or mute > the thread > < https://github.com/notifications/unsubscribe-auth/ALUjKDGDUUx3QusEKlhqFEVFR5JEh0rxks5vN44cgaJpZM4QJfUa > > . > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#14 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AZD4pifjH-H2FG3M46V_ty_5sGIFujbUks5vN49UgaJpZM4QJfUa> .

achan-pancan · 2019-04-01T17:49:54Z

Are you guys getting this mismatch too? If you try to click start in Ext2's Service Management, it says the service could not be started.

isolationism · 2019-04-17T22:19:24Z

I'm seeing exactly this behaviour as well, @achan-pancan. Windows 10, trying to mount an EXT3 (Linux Mint) partition on an external M.2 NVMe drive.

AdamSFX · 2019-04-23T14:28:22Z

I have the same issue as @achan-pancan and @isolationism - Windows 10 Pro v1803, I just get a format disk message when I try to access a drive, windows shows the service as running, but Ext2 shows it as not running and says it can't be started.

isolationism · 2019-04-23T14:32:40Z

For what it's worth @AdamSFX, my explorations online uncovered that an older release of ext2fsd, ext2fsd-0.53, works for me (and others similarly afflicted) in Windows 10 — though I have so far only entrusted it with read-only operations. YMMV.

AdamSFX · 2019-04-23T15:06:06Z

Thank you! Yes this works for me also.
I am using an external SSD to transfer large video files from a LINUX based camera so I don't have OS corruption issues to worry about and I have been able to read and write to the drive without problems using ext2fsd 0.53

zeronote · 2019-06-18T02:45:57Z

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

pechter · 2019-11-06T07:45:23Z

Same problem. Reverted to ext2fsd-0.68 which works.

hungmol · 2019-12-06T06:50:42Z

I have the same issues on Windows 10 Pro build Version 1909 when used the newest version 0.69. The issue was solved by switched back to version 0.68

sergiirepin · 2020-01-29T09:02:30Z

DON'T use the version 0.68 with Ubuntu on ext4. It will corrupt Ubuntu file system.
https://askubuntu.com/questions/849872/how-can-i-prevent-windows-10-from-corrupting-the-ext4-superblock-every-time

Fixmetal · 2020-04-14T09:22:50Z

In my case it was all due to Secure Boot. I had to disable it, enter Windows and modify a policy:
bcdedit.exe /set {current} nx AlwaysOff (if this command does not run, fire below command:)
bcdedit.exe /set nx AlwaysOff
Then rebooted and enabled Secure Boot again. Ext2fsd just started back again.
Windows 10 Pro 10.0.18363 here.

hfavisado · 2020-05-07T12:53:25Z

Reverting to 0.68 worked for me too. I'm on Version 10.0.18363.778.

brosahay · 2020-05-24T17:56:09Z

I am using 0.68 as my data (external drive) and OS are on different partitions. Running on Version 10.0.18363.836. This thread was helpful.

jaack65 · 2022-05-19T12:57:37Z

Cannot get ext2fsd service to start at all even without any other drive only Win 10 C:\

hal9k · 2022-10-25T02:03:30Z

I had this exact problem and it turned out that Windows 10 Home does not work with v0.69; I had other PCs running Windows 10 Pro and they work well with v0..69.
Solved it after installing v0.68 on the Windows 10 Home machines.

Doesn't work after windows 10 creators update #14

Doesn't work after windows 10 creators update #14

Comments

Barteks2x commented Oct 27, 2017

dd-han commented Nov 22, 2017

ngkaho1234 commented Nov 23, 2017

dd-han commented Nov 23, 2017

kid1412621 commented Dec 2, 2017

nmlgc commented Dec 8, 2017

DaJakerBoss commented Dec 30, 2017

kid1412621 commented Jan 29, 2018

DaJakerBoss commented Jan 29, 2018

kid1412621 commented Jan 30, 2018

DaJakerBoss commented Jan 30, 2018 via email

kid1412621 commented Jan 30, 2018

DaJakerBoss commented Jan 30, 2018 via email

kid1412621 commented Jan 30, 2018

DaJakerBoss commented Jan 30, 2018 via email

kid1412621 commented Jan 31, 2018

DaJakerBoss commented Jan 31, 2018 via email

kid1412621 commented Feb 1, 2018 • edited

dd-han commented Feb 3, 2018 • edited

DaJakerBoss commented Feb 4, 2018 via email

ngkaho1234 commented Feb 13, 2018 • edited

sonvirgo commented Mar 18, 2018

DaJakerBoss commented Mar 18, 2018 via email

kid1412621 commented Apr 9, 2018

DaJakerBoss commented Apr 9, 2018 via email • edited

DaJakerBoss commented Apr 9, 2018

kid1412621 commented Apr 10, 2018 • edited

marcosx86 commented Jul 25, 2018

nmlgc commented Jul 27, 2018 • edited

marcosx86 commented Jul 27, 2018 via email

kid1412621 commented Feb 16, 2019

ngkaho1234 commented Feb 16, 2019 via email

kid1412621 commented Feb 16, 2019 via email

achan-pancan commented Apr 1, 2019

isolationism commented Apr 17, 2019

AdamSFX commented Apr 23, 2019

isolationism commented Apr 23, 2019

AdamSFX commented Apr 23, 2019

zeronote commented Jun 18, 2019 • edited

pechter commented Nov 6, 2019

hungmol commented Dec 6, 2019

sergiirepin commented Jan 29, 2020 • edited

Fixmetal commented Apr 14, 2020

hfavisado commented May 7, 2020

brosahay commented May 24, 2020

jaack65 commented May 19, 2022

hal9k commented Oct 25, 2022

kid1412621 commented Feb 1, 2018 •

edited

dd-han commented Feb 3, 2018 •

edited

ngkaho1234 commented Feb 13, 2018 •

edited

DaJakerBoss commented Apr 9, 2018 via email •

edited

kid1412621 commented Apr 10, 2018 •

edited

nmlgc commented Jul 27, 2018 •

edited

zeronote commented Jun 18, 2019 •

edited

sergiirepin commented Jan 29, 2020 •

edited