Over the past few months there have been significant problems with new comment email notifications. As a result, some comments made in the past ~3 months may have gone unanswered.
The comment queue will now be reviewed manually and more often to ensure everyone gets timely responses to any questions. Today, replies are being posted to any comments that have gone unanswered during this time period.
Apologies to anyone whose comments went unanswered! If you don’t receive a response in the comments, please use the contact form.
An update will be posted when this issue is fully resolved by the vendor.
FATXplorer 3.0 Beta 12 is out now and brings with it a new feature and various fixes.
New Feature: Disk Health Checker
Beta 12 utilizes a new API introduced in Windows 10 1607 (Anniversary Update) to check disk health/status. FATXplorer will now tell you whether your disk is healthy or not, and if there is a problem, what the problem is.
Here’s what it looks like when there are no problems:
And when there are problems:
An alert will also pop up on the bottom right of your screen. You can click the magnifying glass to see a little more information:
Frequent users of the beta may be familiar with these messages:
Great news! These messages should no longer pop up – a fix has been implemented. These messages were most prevalent on Windows 7, but also popped up randomly on Windows 10. With the fix, the messages no longer pop up on Windows 7, but due to the random nature of the messages on Windows 10, it’s hard to know if the problem is completely solved. It probably is, but if you see it again in Beta 12 onwards, please reach out.
Beta 12 includes a host of memory-related fixes. Special thanks to Reddit user neakmenter for reporting the issues and helping test the fixes.
First, in general, memory usage has been reduced by 85% or more in some cases (like working with hundreds of thousands of files), and a bug was fixed where memory wasn’t being released after unmounting.
Second, a memory-saving strategy has been introduced in the form of a new toggle switch to help in cases where many folders are opened:
As described in the tooltip, if your want full performance without compromises, you should toggle on extra memory (the default). It will speed up file and folder creation, updating, and deletion. It is most noticeable when copying a lot of small files Do note that this has been the default behavior in all previous betas – the only thing new is being able to disable it. The amount of memory that will be used depends on how many folders are in the mounted partition, and whether you interact with/open them. To put this into perspective, if you have 50,000 folders, and then open them all by calculating the size of all of them, FATXplorer will use around 1 GB of extra memory on top of what it is already using. Basically, unless you are very memory-conscious and/or are working with 100,000+ folders that you open each time you mount a partition, you shouldn’t need to disable this feature.
As a simple test, copying both Mass Effect 3 and Call of Duty: World at War (20,738 files, 295 folders, 16.8 GB) to the WD Black 3.5″ HDD used in the initial benchmarks yields the following results:
Copy: Extra Memory On: 00:04:03, Off: 00:04:50
Delete: Extra Memory On: 00:00:33, Off: 00:00:38
And on the WD Black 2.5″:
Copy: Extra Memory On: 00:05:35, Off: 00:05:50
Delete: Extra Memory On: 00:00:27, Off: 00:00:42
As you can see, allowing extra memory has some benefits. If you are copying hundreds of GB, the difference will probably be even greater.
Update to Beta 12 today to get all these fixes. Your RAM sticks will thank you!
It has been several months since FATXplorer 3.0 Beta 1 was released and since then, more than a thousand people from all over the world have given it a try! Before the year comes to an end, I thought I would give an update on how things are going.
Beta Program Statistics
In the past 90 days:
- Around 1k unique users have launched the beta, with 30-40 active daily. People from all over the world are using it!
- Around 7.1k devices mounted.
Beta 11 is available today. The last big beta announcement was #4 back in June. Since then, 6 more betas have been made available over the built-in updater, bringing various fixes and improvements. If you’re curious what’s changed, here is the release history document.
Beta 11 now runs on .NET 5, which is the next major version of the Microsoft .NET platform. It doesn’t bring anything truly groundbreaking for FATXplorer, but various tweaks have been made here and there to take advantage of new APIs and features. Performance should also be a bit better. You need to download and install the .NET 5 runtime before launching Beta 11.
You can get Beta 11 through the built-in updater, or the download links here.
HDD Locking/Unlocking Dilemma
Many have written in asking if FATXplorer will be able to unlock OG Xbox HDDs. Unfortunately, there is no good news to share on this front. It doesn’t look like this is possible due to Windows security features introduced in Windows 8, see here. Emails sent to that Microsoft address have gone unanswered. A workaround may eventually be found, but for the foreseeable future, you will need to unlock your HDDs through other means.
Licensing and Beta Program End Date
Questions have been received regarding license keys in the beta builds. Each build has a hard-coded expiration date (90 days from the day of release). There is currently no licensing in the beta builds, thus no option to enter a key. The beta program will run into 2021 until it has reached feature parity with v2.5. When that day comes, then you will be able to enter a license key to make the build work indefinitely.
License keys you purchase today will work in v3.0 when it’s out of beta.
The next big feature to be introduced in 2021 is the new formatting tools. For Xbox 360 users, there won’t be anything particularly new here, but FATXplorer will gain the ability to remove Windows partitions, which will resolve most cases of formatting errors. For OG Xbox users, there is considerably more customization that can be done compared to Xbox 360. More details to be forthcoming in the new year.
Work is also ongoing on a redesigned and faster website.
Keep the feedback coming – have a Merry Christmas and see you in 2021!
A new KB article has been posted: OG Xbox F & G Drive Help
Many beta testers have written in asking why FATXplorer doesn’t handle their F drive correctly. After investigating each case, 3 primary problems have been identified. Read the above-linked article for detailed descriptions of these problems and how to fix them.
The moment everyone has been waiting for has finally arrived: full read/write support for original Xbox devices! With FATXplorer 3.0 beta 4, you can mount any partition on your original Xbox HDD or MU and explore it like you would as if you plugged in an external USB drive.
It has taken a while to get here, but as you will soon see by the performance comparisons below, it was worth the wait!
Since FATXplorer v2.5 doesn’t support original Xbox, we’ll be using drives that are formatted with an Xbox 360 Content Partition. You can expect the same performance between original Xbox and Xbox 360. Two WD Black-series HDDs will be used, connected to a desktop PC via direct SATA III connection:
- WD Black 3.5″ 7200rpm HDD, Model WD2003FZEX (2 TB)
- WD Black 2.5″ 7200rpm HDD, Model WD5000LPLX (500 GB)
2020 Warning: There are reports that some WD5000LPLX drives do not get flashed properly by HDDHakr, resulting in the drive not working in Xbox 360 consoles. The drive used in this test, which works fine, was manufactured August 16, 2018. If you intend to purchase this drive for use in an Xbox 360, make sure you check your retailer’s return policy.
Here are the relevant specs of the PC these test were run on:
|CPU||Intel® Core™ i7-6700K|
|Storage||Samsung SSD 970 EVO Plus 1TB (NVMe SSD)|
|RAM||16 GB DDR4 @ 3333 MHz|
Your PC specs combined with your Xbox disk specs may result in different performance than what is shown below.
Each test was performed at least twice to verify performance consistency. The copies and deletions are done on a mounted Content Partition using Explorer.
The larger the partition and the smaller the cluster size, the longer it takes for FATXplorer to load it. Improvements made in v3.0 have reduced the loading time for the largest disks and partitions to just a few seconds. For this test, we will be using the 3.5″ 2 TB HDD (the performance gap isn’t as noticeable with 500 GB), and the cluster size was reduced to 8K (all tests after this use the default 16K cluster size).
Many Small Files
Several customers expressed frustration in the past in regard to v2.5’s performance when it came to copying many small files. Improving performance here was a focal point during the redesign. After asking these customers to try out v3.0, they confirmed that it is indeed significantly faster. For this test, 4096 single-byte files were created and copied to the disk.
Next, let’s delete all those files:
That synthetic test looks great, but let’s test a real-world scenario. Mass Effect 3 has 4,005 files and is 10.5 GB in size. The large number of mixed-size files makes this game a great test case.
As you can see, in some cases the improvements to file copies in v3.0 can be measured in minutes, not seconds!
Deleting all those files looks like this:
Now let’s try a different game: Call of Duty: World at War. This is a 6.32 GB game with 16,732 files.
Just like with Mass Effect 3, the speed improvement can be as much as 2 minutes!
FATXplorer v3.0 brings improvement in every area and performance may improve even more in the future!
As a token of appreciation to beta testers who are not already license-holders, download and try FATXplorer v3.0 beta before June 24, 2020 and you can find a $5 coupon in the status bar of the application (at the bottom). The license will work on v3.0 when it is officially released.
At long last, original Xbox support in FATXplorer is in a very usable state! Below is a video showcasing the mounting of my HDD image, and the mounting of a HDD image that has a custom partition table on it that someone generously provided. This is being done on a Windows 7 VM – even though Microsoft has recently ended support for it, it will still be a FATXplorer 3.0-supported OS.
Beta 1 is very near! Just a little more bug fixing is needed before emails go out to those who have shown interest in testing.
Work on the base UI for FATXplorer 3.0 has recently finished for the upcoming beta and should closely resemble what will eventually be released as the final product. The UI has been completely redone to give FATXplorer a more modern look and to work well with high resolution displays, while also offering modern features, such as a dark mode and scalable SVG icons.
Note that everything seen here is subject to change as development progresses, and based on feedback.
When you run FATXplorer, the first thing you will see is the new main window:
Let’s start at the top. You’ll notice a few buttons on the title bar at the top right.
The first one is the mode toggle. This lets you toggle between light and dark mode, and there is also an option to use the Windows setting. For Windows 10 1607 (Anniversary Update) and newer, FATXplorer will toggle light and dark mode automatically based on your Windows default app mode setting. Changes take effect in real-time, too! FATXplorer has been designed to work great with both modes and dark mode should be great for your late-night sessions. Here’s what it looks like:
The second button is the palette selector. You have 7 different color palettes to choose from that will change some FATXplorer UI elements to match that color. The default is a shade of green to reflect Xbox colors.
The last button is minimize to tray. This is already in 2.5 and works exactly the same. This is useful after mounting a device so you can remove FATXplorer from view to maximize screen real estate and to avoid the possibility of accidentally closing it and unmounting your device(s).
Now for the main menu. The old FATXplorer has used a ribbon throughout the 2.x series of releases. It has been replaced with bold, wide tiles to highlight key functions:
The devices tile menu, when clicked, shows all devices connected to your computer that have Xbox storage. You have all the familiar functions from 2.5 and some new ones:
Show Log – FATXplorer 2.5 technically features this, but it’s a hidden feature, and only outputs to a file. In 3.0, you can instantly see the complete device detection log. This is very valuable when your device isn’t showing up. It should give you some insight into any problems.
Load Special – This is for advanced cases and some recovery scenarios. It will let you configure the offset and length of the partition you are looking for, and it will override the default device scanning parameters to look for this specific partition on all devices being scanned. This feature is not done yet and will be implemented later.
Format a device to FATX specifications (both original Xbox and Xbox 360). This feature is not done yet and will be implemented later – will function similar to 2.5 formatting tools, but with the inclusion of original Xbox support + homebrew partition table.
Configure your settings. There aren’t really any settings at the moment, so this is a placeholder and a settings window will be implemented later.
A drop-down that contains a few shortcuts and options. When sending in a support request, you’ll want to create a support package to help support narrow down problems you are running into.
Mounting a device works pretty much the same way as it does in 2.5, but the UI for doing so is completely new:
If you want to prevent any sort of write operation from happening, you can toggle Read-Only. In 2.5, there was a common question of “what are all these partitions for / what is in them?” Partitions are now listed with descriptions to help answer these questions.
The new Toolkit, Content, and Recovery views are not ready yet. Advanced Information is an option for HDDs that will obtain the output of smartmontools (a popular HDD SMART utility) and display it. This can be very useful if you suspect your HDD is dying and want a quick and easy way to check SMART values.
Finally, at the bottom of FATXplorer you’ll see the driver status. If the driver is not installed, you can click it to install it. It’ll also flash blue when there’s an update available for it. If you don’t click to install here, it’ll ask you right before you mount a device. There is also Show Log, which is a toggleable log window that’ll show you technical details about what is going on behind the scenes.
When can I try it?
Not much longer now! Work will now shift to getting drive mounting in a functional state. The next post on this site should be the beta announcement.😉
In the meantime, please feel free to share any feedback on the new UI in the comments below!
Hi everyone, it’s been a while since the last update, so I wanted to provide an update on where things are.
Original Xbox Support
The hype around this feature is real and it’s really cool how the OG Xbox scene has come back to life. It’s important to me that original Xbox support is as complete as possible because so many people have expressed interest in it. The partition layout was easy to figure out. The complexity came from the beginning sectors of the disk. There is a wealth of data: refurb information, manufacturing information, cache databases, XBL profile/machine information, and network configuration. After poking around quite a bit, I have mapped out basically 99% of it. It’s relatively undocumented data and I’ve found some things that may not have been discovered before. The plan is to provide some kind of viewer so everyone will be able to see this data. Some of you may find it quite interesting!
Partitions: Aside from being able to look at all of that disk data, 3.0 will have full support for all official Microsoft stock partitions, and also customizations by the homebrew community (the partition table, larger disks with F drive). You’ll also be able to format/customize your partitions.
Disk Unlocking: I have researched the possibility of adding a disk locker/unlocker and came to the conclusion that some IDE/SATA -> USB adapters do not support the ATA commands needed to carry out these operations. FATXplorer will not be able to unlock your disk if it is locked.
Driver: The current version of FATXplorer uses an older file system driver. It still works just fine, but doesn’t take full advantage of Windows 8 & 10 features. The new driver in 3.0 will have full compatibility with Windows 10, so if you’ve experienced any strange behavior with the current version, 3.0 should work better for you.
Requirements: 3.0 has a minimum requirement of Windows 7 SP1. It was originally going to be Windows 8, but Windows 7 is still quite popular, so some small concessions were made to make it work on Windows 7. XP and Vista support will not be available.
Licensing: 3.0 is a free upgrade to current license holders. You’ll still be able to use it on all PCs that you own. I am floating the possibility of creating a new licensing option: a “day pass” that will grant you full access to FATXplorer, for 1 day, at a low price. This may be useful to people who just need to use FATXplorer for something, like a disk content transfer, and don’t plan to use it again. This is just an idea for now, but if this is something you or a friend may like, please leave a comment voicing your support!
AF/4K Disks: 3.0 will have support for AF disks (AF means Advanced Format, not the expletive you may be thinking of😛). If you have an AF disk, you may see better read/write speeds compared to the current version of FATXplorer. Please note that Microsoft OEM disks are not AF, but if you’ve purchased a drive within the past few years, it probably is. (FATXplorer will tell you if your disk is AF.)
Old Code: Some of FATXplorer’s code is, believe it or not, 10 years old now! The reason the 3.0 update is taking longer than usual is because the project has essentially been restarted. This is not a bad thing – it will help make FATXplorer work well for the next 10 years! It comes at a good time with the developments Microsoft has done with .NET Core, particularly with integrating Windows UI frameworks into it.
New Recovery Features
These will come a bit later, but there will be a new feature to help find “lost” files, such as old game builds that are still on-disk, but separated from the directory tree. If you’re a preservationist and have some disks that may have interesting files on them, please reach out so I can add you to a list to try out new recovery features when they’re ready.
The website has been slow and, by 2019 standards, looks dated. A new website is coming. The plan is to keep all existing posts and comments. This may happen before 3.0 releases.
Thank you to those who continue to voice their support for FATXplorer and original Xbox support. I know the wait has been painful, but I think you will be pleased with what is coming.🙂