Enmotus Support

FuzeDrive/FuzionX - What's New and Changelog

What's New in v1.8

  1. Support for FuzeDriveSSD P145/P146
  1. Fix issue with Sabrent NVMes in 4K mode
  1. Fix for ASUS motherboards that report GPT corruption after a create

What's New Since StoreMI v1.5

  1. FuzeDrives can be completely unfuzed
  1. Fix for conflict with Windows Sandbox and OneDrive Personal Vault
  1. Secure Boot no longer needs to be disabled for new bootable tiers
  1. Ryzen B550 motherboards supported

Changelog

v1.8.0:
AHCI Driver:
Fix issue with some ASUS motherboards that report GPT corruption after a FuzeDrive create
Fix for false error reports when using 4K-mode drives
Configuration tools:
Add support for FuzeDriveSSD P145 and P146
Licensing:
Remove FuzionX program expire date
v1.7.1:
Configuration tools:
Fix bug allowing drives to be pooled.
Fix regression where user is allowed to fuze a non-bootable drive where FuzeDrive program files are installed.
Installer:
Warn user if drive pooling has been enabled.
v1.7.0 [FuzeDrive/FuzionX] (FIRST RELEASE of FuzionX):
Configuration tools:
Add support for FuzeDriveSSD P200.
Allow multiple tiers when using one or more FuzeDriveSSDs with a paid FuzeDrive license, or when using multiple FuzeDriveSSDs with FuzionX.
Roll back some of the GUI changes from v1.5 to allow for multiple tier support.
Miscellaneous bugfixes.
Service:
Fix for stuck unfuze
Installer:
Recognize AMD Zen3 (5000 series) CPUs.
v1.6.2:
AHCI Driver:
Add support for Ryzen B550 motherboards.
Installer:
Fix for EnTier Service upgrade issue affecting some users.
Additional fix for "license system lock error" when upgrading.
v1.6.1:
Installer:
Fix for "license system lock error" when upgrading from v1.5 to v1.6.
Upgrade failures will now roll back to prior version.
v1.6.0:
AHCI Driver:
Fix for Microsoft container issues, including a boot issue caused by Windows Sandbox, and a freeze when unlocking OneDrive Personal Vault.
Configuration tools:
Add "UnFuze" option which moves all data to the slow media, then re-linearizes it and removes the tiering metadata, so the FuzeDrive driver is no longer required to access the drive (i.e., cloning to a third disk and back again is no longer required, though it is likely faster to use that method).
Fixes for various drive discovery issues
Systray tool:
Fix spurious "Activate acceleration" warnings.
More error conditions are recognized (usually issues with the underlying hardware), and certain errors will no longer pop up constantly.
EFI Loader:
For new bootable tiers, a new boot loader is used that does not require Secure Boot to be disabled.  The FuzeDrive logo is no longer displayed.
v1.5.3 [FuzeDrive/StoreMI] (FINAL RELEASE of StoreMI):
AHCI Driver:
Fix for corner case of a nonbootable tier disappearing in FuzeDrive v1.5.2
TRIM requests from the OS are now properly sent to the non-tiered SATA SSDs attached to the primary AHCI controller
Configuration tools:
Fix for NVMe drive misidentification
Fix for issues converting tiers after uninstalling and reinstalling the software
Show an error message when an NVMe drive is selected while AMD NVMe RAID is enabled
Show an error message when a shrink is necessary on a BitLocker volume
Fix for GUI issue where drives that were part of a broken tier would not be displayed
Fix for CLI issue where drives did not appear as captured until after a reboot
v1.5.2 [FuzeDrive]:
AHCI Driver:
Ignore Microsoft Xbox Beta Gaming Services virtual disk miniport driver to resolve recurring blue screens
Fix for cache stability issues with some configurations
Fix for corner case of blue screens or hangs under heavy load
Present VDRIVE carveout (drive created when fast drive is larger than license capacity) as appropriate drive type instead of always as HDD
Fix issue with major Windows upgrades failing on the first try
Tiering Priority is now scaled when Tiering Rate is changed
Configuration tools:
Better handling of OEM partition moving
Installer:
Fix update check broken in v1.5.0
v1.5.1 [FuzeDrive]:
AHCI Driver:
Add support for all Ryzen platforms to FuzeDrive, including 500-series motherboards as well as older mobile/SFF chipsets
Configuration tools:
Revert hibernation file lock speed-up from FuzeDrive v1.3.8, as it could cause issues
Fix cosmetic issues that sometimes occurred after drives were added or removed to system, or when certain older USB devices were plugged in
v1.5.0 [StoreMI]:
AHCI Driver:
Add support for the new Ryzen 500-series motherboards
Additional fixes for rare intermittent hangs or blue screens affecting certain configurations, including a TRIM issue introduced by recent Windows updates
Enhance VMAP auto-healing
Configuration tools:
Updated GUI
Switch to a custom JRE based on OpenJDK 11 with better support for 4K monitors
Additional fixes for misidentified drives
When creating a tier, warn about drives with low SMART health
Post-reboot processes after bootable tier creation/modification start silently before user sign-on
Better handling of partition moving and resizing
Systray tool:
Add controls for tiering priority to tray menu, which sets how high host IOs must be before promotes are delayed
Display errors in toaster messages
Add a display to describe current errors
Service:
Add errors to Windows Event Log
EFI Loader:
Improved EFI startup auto-recovery options added for failed transforms
v1.3.8 [FuzeDrive]:
Configuration tools:
Fix for rare issue where drives would be misidentified
Speed up hibernation file locking
v1.3.7 [StoreMI]:
AHCI Driver:
Fix intermittent hangs that affected certain configurations
Fix for carve-out instability
Fixes for cache instability
Delay promotes during high IO periods
Configuration tools:
Fix for an issue with relocated recovery partitions sometimes becoming inaccessible
Licensing:
Generate static hostname so new license isn’t consumed after a Windows reinstall
Installer:
Fix for rare issue where lock file couldn't be written
v1.3.5 [FuzeDrive]:
AHCI Driver:
Fix blue screen that affected certain configurations
Installer:
Recognize updates from StoreMI v1.3.4+
Always scan drive controllers rather than relying on a previous result
v1.3.4 [FuzeDrive/StoreMI]:
Configuration tools:
Resolve an issue with nonbootable tiered NVMEs not working when booting from another NVMe
Installer:
Fix bug where new installs would fail after viewing Drive Controller Information
v1.3.3 [FuzeDrive]:
AHCI Driver:
Better self-repairing of VMAP errors
More fixes for unsupported IOCTLs from apps like HWiNFO
Stability enhancement to FuzeRAM cache startup
EFI Driver:
Ignore optical/USB/SD devices (resolves extremely long boot times for some users)
Configuration tools:
Users must delete a secondary data drive on their own (e.g., in Disk Management) before Create Bootable
Don’t allow tiering a non-bootable drive when FuzeDrive software is installed on it
Warn before transforming MBR drive when resulting drive will be greater than 2TB
Automatically relocate recovery partition, and better expand routines
Better error messaging
Allow use of JRE9/10
Systray tool:
Add controls for FuzeRAM cache to tray menu
Add "Send Diagnostic Report" button to About screen
Installer:
Fix install failure when USB drive enumerates first
v1.3.2 [FuzeDrive]:
AHCI Driver:
Fix for loss of drive protection from VPAGE0 error (see Errors Help for more information)
Immediately stop promotes when VMAP failures are detected
Fixes to hibernate and sleep
FuzeRAM cache fixes:
Cache re-created after reboot
Cache deleted immediately after FuzeDrive is deleted
Cache attaches to FuzeDrive instead of VDRIVE carve-out
Configuration tools:
Fix getting order of fast and slow wrong in some cases
Fix VDRIVE carve-outs not releasing on delete
Remove unnecessary attempt to shrink when transforming boot drive
Extend volume where possible
Systray tool:
Better notification about hibernation file migration
Fixed issues with reporting errors and warnings
Added Help menu and About entry
Installer:
Offer to clean stale metadata from the boot drive to prevent a recurring blue screen crash
Driver is automatically added to Windows Recovery Environment
Better error message when RAID/IDE mode is enabled
EFI ecmd:
New autoscan parameter added to recover function to automatically determine which drive to unfuze
v1.3.1 [FuzeDrive/StoreMI]:
AHCI Driver:
Fixed a crash when Storage Spaces devices are present
Fix possible boot issues with third party controllers
Support A320 chipset
Fixed a crash when launching HWiNFO (drive statistics are limited)
Configuration tools:
Fix for when Windows disables booting from alternative controllers
Fix for preserving data on GPT drives that are missing the reserved partition
Fix detection of some solid state drives
Tweaks to hibernation migration
Report when chkdsk is necessary to perform shrink
Extend volume where possible when preserving data in full tier mode
Systray tool:
Fix accelerated/accelerating promote count overflow
Installer:
Fix for Unicode languages causing issues with collecting storage controller information
Fix for license issue when installing to drives other than C:
v1.3.0 [FuzeDrive]:
Initial consumer product release

    • Related Articles

    • Deleting FuzeDrive and VirtualSSDs

      Important: The following steps deletes the FuzeDrive and ALL DATA that is stored on each of the drives. All data is completely lost on the FuzeDrive and/or underlying drives so only use this option under the following circumstances. (a) you have ...
    • Uninstalling FuzeDrive

      Background Once a disk has been converted to a FuzeDrive, the data begins to be distributed across the two different tiered storage devices. Depending how long you have been using the FuzeDrive, the data may be widely distributed (as is typical in a ...
    • FuzeDrive/FuzionX/StoreMI v1.5+ Known Issues

      General Issues: To install, your system must be in AHCI mode.  For instructions to convert from RAID or IDE mode to AHCI, see <https://support.zoho.com/portal/enmotus/kb/articles/converting-system-from-raid-or-ide-mode-to-ahci>. Some software ...
    • Recommended Configuration for a New Windows Installation

      The simplest method to install a new copy of Windows onto a FuzeDrive is as follows: 1. Ensure that the BIOS SATA settings are set to AHCI (not RAID) and secure boot is set to off. For boot volumes > 2TB make sure your BIOS is set to boot in UEFI ...
    • Moving a Bootable FuzeDrive To a New Motherboard

      NOTE: This KB regards bootable FuzeDrives.  Non-bootable FuzeDrives can be moved to another system and will work as soon as the FuzeDrive software is installed on the new system.  (Just remember to deactivate your license first.) There are two ways ...