WARNING! DO NOT USE! MESSES UP WITH YOUR SYSTEM AND CAUSES DATA LOSS!

[mario98]

The problem is after installing the software, removing external hard disks from the system (via save remove) fails silently. The drive is still shown in Windows Explorer, but in device manager, it reports that the driver crashed. Problem is if you then restart your system, Windows hangs for several minutes and then crashes with a Blue Screen. Also this causes data loss. A lot of files that were currently open were overwritten with all zeros! This software was to blame. After I uninstalled this software, my system worked normally again! This happens also if you go into device manager and disable any hard drive that is currently in use. Then the operation never completes and again Windows will not be able to shutdown properly. If this software is not installed, Windows normally just complains that the drive is in use and suggests a restart. This software completely messes up with this! This software wasn't running at this time. It was just installed on the system. I only use this software occasionally but installation alone broke my system. I think the driver is not very compatible and does some unusual things.

Windows 10 x64 1803

@matt-wu Please take action and make a big fat warning on your website until you fixed this bug! This is a very serious bug!

[elderK]

Hey there,

I just wanted to add to this issue to show that Mario isn't alone and isn't just some random statistic.

I've been encountering similar issues - primarily with external USB drives.

You perform some operations - say copy a bunch of files, eject and remove the device when Windows gives you the all clear.

The "drive" is still visible and weirdly, still navigable. You can write new files, read files that were around. It's as if the device was never disconnected.

Of course, all of these changes are not persisted. They cannot be, as the device was removed.

More problematic is that the things you copied, before ejecting, never seem to be written through to the device. I've tested this several times and checked the device on different systems to confirm that the data was or was not written.

The data is not written...

Somehow, somewhere, ext3fsd is failing seriously, silently.

EDIT: I've been encountering these issues on Windows 10x64.

~K

[mario98]

It's even worse than just the data that was written to external hard drive. In my case, data written to internal storage (NTFS partitions) were overwritten by all zeros. I lost my browser profile this way because it got corrupted along with a bunch of other config files (settings for Notepad++ etc.) This is because once the system is in this failed state, it can never actually dismount any HDD any more, even at restart it will hang and only a hard reset will allow you to restart the system. Shutdown may work due to Windows 10 hybrid shutdown, but if you try to actually shout down, your system is lost / corrupted. You must pray that no critical files get overwritten.

If you can see in Wikipedia, Ext2Fsd is known to cause troubles since 2009. I think this software never actually worked as expected. The author just hacked some code that works on his particular system but never tested it somewhere else. I think the author should delete the software. Worse than having no software is having one that is pretending to work but will actually just waste your time or even worse destroy your system.

It's like a Siren. It attracts people who are impressed by the feature claims but in reality it will just trash your system.

[mario98]

It's true, folks. Did the authors respond to this comment since the last two month? No. Did they do anything to fix this, or to warn people to not use this software with Windows 10? No. Instead, they just hide away from their problems their software creates and are not ready to take responsibility. Probably you think "oh, it's all open source and voluntary work, it's ok". No, it's not.

Imagine someone goes to a shopping mall to give out "free lemonade" but then it turns out their lemonade poisons people and they have to go to the hospital. That wouldn't be okay either and those guys would have a hard time to justify their action in front of government or consumer protection agencies.

We need the same standard for software developers. Whenever you release something to the public, whether it is open source or not, you should be held accountable for any damage you caused by grossly negligent conduct. If people come forward to you to report your software is toxic and you do not react this is grossly negligent conduct in my opinion.

[sonicpp]

Instead, they just hide away from their problems their software creates and are not ready to take responsibility. Probably you think "oh, it's all open source and voluntary work, it's ok". No, it's not.

Have you ever read the GPL license? Why are you using software without the knowledge of license it is using?

We need the same standard for software developers. Whenever you release something to the public, whether it is open source or not, you should be held accountable for any damage you caused by grossly negligent conduct. If people come forward to you to report your software is toxic and you do not react this is grossly negligent conduct in my opinion.

If you want warranty, go and spend some money on buying some paid software. This is such a nonsense, I really hope you are just random troll.

[arisboch]

@sonicpp Fuck this lawyering.

Just warn everyone everywhere you can that this software is shit.

Edit: Downvoting my comment doesn't change the fact that this software destroys data.

[agowa]

Your read the release note right?

The driver may crash your system and ruin your data unexpectedly, since there might be software conflicts and I could only test it on some of the popular platforms. You should use it with care and use it at your own risk!

And also I think this project is dead, as the last commit is from Oct 31, 2017 (Not counting the readme change on Feb 12, 2018) So If you want to rant about not warning about issues with windows 10, try the latest windows 10 that was available back than. It should be obvious, that this project: a) Got most likely abandoned b) Was only in an prerelease non production ready state (Versionnumber below 1.00).

[Amaroq-Clearwater]

Have you tried running the installer for the driver in Compatibility Mode? I'm trying that now to see if it makes a difference.

In Windows 10, it is possible to configure driver installations to run in Compatibility Mode so that the operating system will perform workarounds to make the driver work, but it does require reinstalling the driver.

No guarantees that this will actually make a difference. We'll see.

The only solution to getting this driver working completely, I'm afraid, is for somebody else to start working on it.

[agowa]

For everyone ranting about the project, if you want to have a production ready solution with support, you should buy https://www.paragon-software.com/de/home/linuxfs-windows/ this. It works great, from what I've tested and it claims to support Btrfs/XFS/Ext2/3/4 all of them with read write access.

And for anyone else that wants to take this task on to implement an FOSS alternative, please don't let them get you down. Keep going! ;-)

[Ruedii]

Maybe you should give useful system logs with your bug report, instead of just complaining.

Otherwise people will think you are a troll.

[hmtheboy154]

wow

[Heath123]

For everyone ranting about the project, if you want to have a production ready solution with support, you should buy https://www.paragon-software.com/de/home/linuxfs-windows/ this. It works great, from what I've tested and it claims to support Btrfs/XFS/Ext2/3/4 all of them with read write access.

And for anyone else that wants to take this task on to implement an FOSS alternative, please don't let them get you down. Keep going! ;-)

That also corrupts data

[agowa]

@Heath123 Than contact the support of paragon software, it's a commercial solution with support, so just use it...

[Heath123]

@Heath123 Than contact the support of paragon software, it's a commercial solution with support, so just use it...

Lots of people had the issue, they should have fixed it themselves, I’m just warning people that it could also cause problems

[agowa]

@Heath123: I'm using it without these errors. Others are using it without errors. So the error is not something that hits everybody. Than go and fill a bug report (or leave it), but this is the wrong place to complain about it...

[Heath123]

No, it's the right place place, because you said it doesn't have the corruption issue when in fact it does, and people need to know that

[Merith-TK]

2020 still having issues, except now when the partition gets unmounted by any means, even during system shutdown

FEKKING BLUESCREEN WITH A RANDOM ERROR CODE

THis most recent time it complained the powerdriver had an issue but ive had it complain that the following were the issue 1) Networking 2) My harddrive 3) The ethernet 4) The System Clock

I have even completely uninstalled the driver from my system, and several months later, issue is still persisting

[agowa]

@Merith-TK this project is dead, it doesn't look like anyone is going to fix it. So it will just get worse over time as compatibility to the operating system keeps decreasing...

[Ruedii]

If someone knows anyone who could fork and pick up this project it would help.

In the mean time I would recommend against using this project for read-write access to drives.

It is still quite suitable for read-only access, but writing to Linux partitions from Windows has been historically troublesome and this app is not different.

[Merith-TK]

Part of the problem is that it took me several weeks to remove the driver from my system, the Uninstaller does not remove the driver at all. I had to go through, open the file system in Linux, and delete all files that even have the name ext in them. Just to get the driver gone.

On Wed, Feb 3, 2021, 11:32 AM Ruedii notifications@github.com wrote:

If someone knows anyone who could fork and pick up this project it would help.

In the mean time I would recommend against using this project for read-write access to drives.

It is still quite suitable for read-only access, but writing to Linux partitions from Windows has been historically troublesome and this app is not different.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/matt-wu/Ext3Fsd/issues/26#issuecomment-772764541, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACPQOXRBOPQ4H4CXUCXWCO3S5GQFJANCNFSM4FRRHISA .

[mpathy]

Why you using this? There are several software that doesnt damage your system. But yes, until it works at least as the other software available, it should be taken down, it could be considered malware, in my opinion.

[Merith-TK]

Or atleast updated so the Uninstaller REMOVES THE FUCKING DRIVER FROM SYSTEM32

Legit. I had to boot from a live Linux USB, mount my hard drive, and manually sudo rm -f the file. and any other file related.

On Fri, Jun 4, 2021, 6:34 AM Markus Majer @.***> wrote:

Why you using this? There are several software that doesnt damage your system. But yes, until it works at least as the other software available, it should be taken down, it could be considered malware, in my opinion.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/matt-wu/Ext3Fsd/issues/26#issuecomment-854728583, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACPQOXQXAMEP26LUBWVJEUTTRDI7LANCNFSM4FRRHISA .

[Ruedii]

Should be modified to be a read only driver too.

R/W Should have been considered experimental.

On Fri, Jun 4, 2021, 9:53 AM Merith @.***> wrote:

Or atleast updated so the Uninstaller REMOVES THE FUCKING DRIVER FROM SYSTEM32

Legit. I had to boot from a live Linux USB, mount my hard drive, and manually sudo rm -f the file. and any other file related.

On Fri, Jun 4, 2021, 6:34 AM Markus Majer @.***> wrote:

Why you using this? There are several software that doesnt damage your system. But yes, until it works at least as the other software available, it should be taken down, it could be considered malware, in my opinion.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/matt-wu/Ext3Fsd/issues/26#issuecomment-854728583, or unsubscribe < https://github.com/notifications/unsubscribe-auth/ACPQOXQXAMEP26LUBWVJEUTTRDI7LANCNFSM4FRRHISA

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/matt-wu/Ext3Fsd/issues/26#issuecomment-854740467, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAYFL2OPXRQ72B4KCUPQ2CLTRDLG5ANCNFSM4FRRHISA .

[agowa]

Or maybe you shouldn't expect something that hasn't been updated in ages to work on modern operating systems?

I'm now going to clone this git repo because it could be interesting for reference in the future and I as a dev would already have deleted this just because of the disrespect within this thread...

[arisboch]

@agowa338 A dev like this doesn't deserve any respect.

[Merith-TK]

@agowa338 A dev like this doesn't deserve any respect.

Please be respectful in issues, especially considering you have not contributed to litterally anything here on github

[arisboch]

@Merith-TK And I thought figuratively.

[Heath123]

Or maybe you shouldn't expect something that hasn't been updated in ages to work on modern operating systems?

I'm now going to clone this git repo because it could be interesting for reference in the future and I as a dev would already have deleted this just because of the disrespect within this thread...

It doesn't have to be deleted, there can be a huge warning on the README and maybe the repo can be archived

[Ruedii]

Someone needs to make a copy of this and deactivate the write functionality by default.

[srghma]

my drive after this app

e2fsck -n /dev/sda3

Journal superblock has an unknown incompatible feature flag set.
Abort? no

Journal superblock is corrupt.
Fix? no

NIXOS_ROOT: ********** WARNING: Filesystem still has errors **********

exit_code = 12

---

false alarm