Features implemented and bugfix:
1, FIXME: BSOD when mounting as readonly
2, FIXME: Ext2Srv service blocked by Antivirus
Supported Ext3/4 features:
1, flexible inode size: > 128 bytes, up to block size
2, dir_index: htree directory index
3, filetype: extra file mode in dentry
4, large_file: > 4G files supported
5, sparse_super: super block backup in group descriptor
6, uninit_bg: fast fsck and group checksum
7, extent: full support with extending and shrinking.
8, journal: only support replay for internal journal
9, flex_bg: first flexible metadata group
10, symlink and hardlink
11, Mount-as-user: specified uid/gid supported
Unsupported Ext3/4 features:
1, journal: log-based operations, external journal
2, EA (extended attributes), ACL support
Features to be implemented in next release:
1, Extents management improvement
2, EA and ACL security checking
Files descriptions:
Ext2Fsd-0.66.exe: setup wizard for Windows systems (win2k, Winxp,
Vista, Win7, Win8, Win10, Server 2003/2008/2012)
Ext2Fsd-0.66.7z: Batch setup package in 7-zip
Ext2Fsd-0.66.zip: Batch setup package in zip
Download link:
http://sourceforge.net/projects/ext2fsd/files/Ext2fsd/0.66/
Files checksum:
C:\Works\Ext2fsd\0.66>sha1sum Ext2Fsd-0.66*
5d49acb25cfdd83e0c41cebf7324f911c8e6b644 *Ext2Fsd-0.66.exe
bca82a345196f176517d2c9939a9710d43cf0625 *Ext2Fsd-0.66.zip
12033fc222514db4fd10a35ad54f315baff82bea *Ext2Fsd-0.66.7z
WARNINGS:
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!
Matt <mattwu@163.com>
https://www.ext2fsd.com
Thanks for the rapid development progress. I appreciate your efforts.
Anonymous
3 May 16 at 11:52 am
Hello,
Today I tried this driver to see the ext3 contents of a HD attached to my win10pro/64 PC.
I downloaded 0.66
windows complained that the signature was invalid
I installed anyway
install went smoothly
I connected the desired drive to a drive letter in ex2 volume manager
I browsed its contents
I disconnected the drive letter in in ex2 volume manager
I went to windows drive management, and removed the partition, created a new partition, started formatting.
windows went bsod.. 😉
windows kept reboooooting with 🙁 and cache_manager as error message.
I resolved by renaming c:\windows\system32\drivers\ext2fsd.sys but it was a far from pleasing experience..
ciao from Italy
ah and by the way thank you very much for this driver, it DID meet my immediate needs! ciao
Michel
4 May 16 at 5:09 pm
Even though you already resolved this, next time you can try booting into safe mode by rapid-tapping f8 upon boot (immediately after you press the Power button). This works as far as up to Win7, I never tried 8 and 10 but it should work.
Daniel
31 May 16 at 1:11 am
Same here. Kept rebooting on me until I stopped the service. (.66). Would do it every time I input a flash drive and the program started managing the drive.
Nick
6 May 17 at 1:57 am
Running Windows 10 Pro 64 bit build 10586.218.
Installed Ext2Fsd-0.66.exe as Administrator
Every time I attempt to open Ext2Fsd Volume Manager, either from Start menu or running executable, I get the “Do you want this program to make changes to your PC” prompt, I click YES, but it does not open a visible application. Task Manager shows both “Ext Volume Manager for Windows (32 bit)” and “Ext2Fsd Service Management (32 bit)” as running processes.
“Ext2 Management Service” is Running.
No ext partitions showing up anywhere, either under Explorer or after rescanning for disks in Disk Management.
Todd
7 May 16 at 11:30 pm
You might have disabled Ext2Fsd service during installation. Try to enable it via Tools->Service Management in Ext2 Volume Manager. Set service startup mode to SERVICE_SYSTEM_START or SERVICE_BOOT_START and then start the service.
Kaho Ng
8 May 16 at 1:09 am
I am having the same problem, running Windows 10. When running the application, I will be presented with UAC and after allowing it to run, the application won’t show up.
And same as him, when inspecting the task manager, the process is there, but there is no cpu and hdd action, kind of like an infinitely idling process.
The processes can be terminated without any errors.
This problem appears even on clean reinstall.
Also since i were just now clean reinstalled Windows 10, I noticed that this bug only appears on the second Windows 10 version (v1511). On the first Windows 10 version (i dont know the version number, sorry), this bug is absent.
If the developer could advise on how to debug and provide necessary information (ie logs), I would greatly appreciate and participate on helping. I really rely on this marvelous software in order to access my Linux’s Home partition.
My OS information is as follows:
Windows 10 Pro 64-bit
Version 1511
Build 10586.218 (as of writing)
Thank you and regards
Shahmi Saidi
9 May 16 at 9:08 am
Same issue here, happened after update to Windows 10 v1511 . Upon successful installation, it runs fine once. After reboot, the application doesn’t show up while it appears in Task Manager. The service is enabled and running.
Managed to run it once again by uninstalling v0.66, rebooting, and installing it on another installation path. The third time this didn’t work either which it might indicate it was coincidental.
Any suggestions will be appreciated .
Stam
8 Jul 16 at 10:04 pm
Same issues – except I can’t uninstall it. Asks for permission and then does nothing. Service and app is running. Same if I attempt to reinstall.
Plymouth Meeting
11 Feb 17 at 6:18 am
I have used ext2fsd for more than seven years. I really appreciate your efforts.
Recently, I have upgraded from win7 to win10. Then I found that the old ext2fsd cannot work any more.
So, I have reinstalled the last ext2fsd V0.66.
However, I found that the newest one does not work with the options SERVICE_BOOT_START .
Probably, there are some problems when it started.
Although I can activate it by hand, win10 sometimes said that “The drive is not readable. Do you format it?” (in Japanese) when I tried to access the mounted partition.
The properties of the target drive are:
BUS: ATA
TYPE: basic
MEDIA: Fixed
partition:
status: Online, Linux, codepage: UTF8
Mount points: (D:)
File system: EXT3
Capacity: 112G
FreeSpace: 88G
Would you give me some advice or hints to fix it?
Koichiro Yamauchi
10 May 16 at 7:21 am
I have a strange problem with this version. I put a USB HDD formatted in EXT3, delete the content and go to copy some new files.
But then, after some time (it´s randomized, to some seconds to minutes), the new drive disappears suddenly and a Windows copy error appears.
I try to attach again the drive and the content that previously I have deleted is there.
What´s wrong?. Thanks!
Antonio
10 May 16 at 4:01 pm
I can’t copy files to my ext4 partition on this version. Windows Explorer confirmes that files are successfully copied, but disk won’t eject safely and files don’t show up after reboot, maybe there’s something wrong with write permissions?
Downgraded to 0.62, works fine.
denpakyoushi
15 May 16 at 12:17 am
The same is here, but the problem is that 0.62 don´t work in my Win10 machine 🙁
Antonio
24 May 16 at 5:29 pm
Hi,
I use ext4 since longtime. Even with 0.62 I use it as read-only because changing anything, even copying a small file, corrupts the ext4 partition, sometimes with files loss. If I am lucky, a fsck fixes some files and their info, but I wouldn’t trust it to run it otherwise than read-only. This is on Windows 7 and 10 64 bit at least. I am happy with read-only if it works and I am so grateful for developer’s efforts.
mike
28 May 16 at 4:54 pm
I’ve been using Ext2fsd since version 0.5something and been all fine so far. This one 0.65 and 0.66 I thought I was having some issue related to the driver, because 0.64 worked but 0.65 and 0.66 not working, when I first tried them. However, with more experimenting, I believe the issue is not with Ext2fsd, but with Minitools Partition Wizard, and also possibly with Virtual CloneDrive by Elaborate Bytes are some issues, and maybe with any similar software who is involved in drive letter assignment there might be some disagreement between them with Ext2fsd.
I am running Windows 7 Ultimate 32 bit, on Dell Latitude D810 laptop, with internal 50 gig hard drive, and external USB-connected 150 gig drive.
One strange thing was with available letters to assign to my ext3/4 formatted drives. For a little while there seemed that no letters were available, and, already suspecting CloneDrive I uninstalled it, but then was still only able to get available letters by bring up the Remove Dead Letters function, which listed every letter 0: thru Z: as being possible to remove except for ones which were actually in use on NTFS partitions. When I did remove some of them, the program prompt with the “are you sure, this letter appears still in use” or what ever it says in that, but I removed them and then was able to assign them. But after running a registry cleaner (the one in CCleaner) that issue seems to have gone away, and even I reinstalled CloneDrive and still no more of that issue.
The other issue, I had one ext4 partition at the end of my internal drive, that I could assign apparently normally, but could not write to it from within Windows, in fact it would freeze the explorer process when I tried. Any other way of attempt at access that drive within Windows also failed, froze, etc. The ones on the USB connected drive were fine. But that partition, I had made with PartitionWizard, and so, I deleted it and re-created it with Kparted (which I’m sure is just Gparted with a KDE interface) and that not only solved not being able to write to and access it normally within windows, but it also made that 0.66 is now working normally.
I have not yet tried working with this in my Windows 10 installation but I will give it a go and see how that flies, and post back here when I have.
Router Gray
17 May 16 at 5:52 am
My latest Windows 10 64 bits seems to work with ext2fsd, except that I have assigned some letter automatically to a partition I don’t intend to access. If I remove its letter, it affects some external USB device which has 5 drive letters assigned and it looses all its letters except for the first disk of it. Weird.
mike
29 May 16 at 3:46 am
I’ve experiencing bugs, where when I mount the drive with EXT2,3 or EXT4, the system did mount it, and all work fine, till, when i unmount, the drive wouldn’t unmount.
-When I tried to remove letters using Ext2FSd, it won’t popup, just idling.
-When I try to open Disk management, it stuck at “Connecting to Virtual Disk Service…”
-If i run any tools such as EaseUs Partition manager, or Minitools Partition wizard, the utilities can’t start.
-When I acess Device manager, it can’t uninstall the drive driver.
-When I unplugged the drive, the drive letter still there, and the files still acessible…
-When I shutdown/restart, it will take approx 10~12 min, then BSOD, says DRIVER_POWER_STATE_FAILURE
I’m using Windows 10 Build 10586 x64
-Fixed the problem with uninstalling the Ext2FSd
Naqhiuddin
31 May 16 at 8:47 pm
The latest version that works on Windows 7 (x64) is 0.52. The rest simply DON’T INCLUDE the wlh driver. I don’t know who made this decision but this should be noted somewhere. Please. Thanks for the software.
Mau
16 Jun 16 at 3:37 am