↶Read/Write Errors Due To InactivityWhen disks are suspended during a running process due to power saving settings, read or write errors may occur.

↶GPT ConversionSome configurations did not allow to select GPT conversion.

☯Disk in the wrong categoryIn some cases, special disks were displayed in the wrong category in the disk select drop-down. For example the individual disks on Intel and Nvidia RAIDs as “RAID” instead of “AHCI” and some SCSI disks as “IDE” instead of “SCSI”.

☯Full speed for SD cardsFor certain internal SD controllers, namely the AU6601, an issue has been fixed that has limited the maximum data transfer speed to less than 5 MB/s.

⇗Save/open file: automatic file extension adjustmentIf the file type filtering in a "save file" or "open file" popup is changed to a different type, the file extension of the currently entered file name will now automatically be changed accordingly.

☯Disk recognition working slowIn rare cases, disk only became visible in the program after a long waiting period, even if they were connected before the program had been started.

☯NVMe / M.2 disks not availableNVMe / M.2 disks were not available in some cases, among others on AMD Ryzen-based systems.

↶Creating encrypted images failedWhen starting a backup or creating an image with encryption enabled, the creation process will cancel with an error immediately after startig it.

☯Disks or input devices not availableIn few cases, disks or input devices were not available.

⛐Saturday-Crash when storing reportIf a copying or imaging process was started or ended on a Saturday - or when running over several days including a Saturday, the app could crash while writing a report. IMPORTANT: The created copy or the image are not affected because the actual process has already been completed at this point.

⛐Apps do not startApps get stuck in a loop after starting.

⇗Bootability of cloned non-Windows OSesThe bootability of Linux and UNIX operating systems cloned, restored from an image or stored to a virtual disk has been be improved further.

☯M.2 / NVMe disks not recognizedM.2 / NVMe disks were not recognized correctly on some systems.

☯Battery indicator on MacBooksBattery status on MacBooks is now displayed correctly.

⇗Apple traget mode supportedFor Apple Mac PCs, connected via Firewire, target mode is now supported for direct access to the disks installed in the Mac.

⇗NVMe-Performance with Intel Rapid StorageFor NVMe disks used with an Intel Rapid Storage onboard controller, linear data access (read and write) has been significantly accelerated.

↺USB issues with TUSB73x0 XHCI controllersA bug in the TUSB73x0 XHCI controller series caused general issues with USB devices.

⇗Auto-continue when out of disk spaceIf insufficient storage space is detected during the creation of an image or backup, the creation is stopped with a message. After freeing up storage space, the user can click a button to continue the process. In order to improve cooperation with other applications and services, that can automatically occupy and also release storage space (e.g. temporary files), the available storage space is now monitored during the interruption and the process will continue automatically as soon as sufficient storage space becomes available again.

⇗Faster System Log writing on shutdownWriting the System Log, created automatically immediately before completely shutting down the software, is now performed significantly faster in many cases.

⇗Supporting former HFS+ versionsVersions of HFS + that do not yet support hardlinks can now be processed.

☯Opening files with SpotFor some files, opening from Hex or Pad did not work from Spot without displaying an error.

☯Error when opening image files via Jumplists or Windows ExplorerFiles with special characters in their names or folder path could not be opened via the jump list in the taskbar or via Windows Explorer.

⇗NTFS file system adjustments failureIn special cases (e.g. NTFS not formatted by Windows) the NTFS file system adaptation could fail if the file system is to be downsized or defragmented or if the target has a different sector size.

⇗M.2 / NVMe on Intel RST RAIDM.2 / NVMe disks, that are members of an Intel RST RAID, are now recognized correctly.

⇗No automatic resize for special MacOS partitionsSpecial partitions on MacOS disks for which resizing is not useful are now excluded from the automatic resizing.

☯Unable to create System LogsSystem Logs cannot be created, neither automatically nor by user interaction.

☯Boot loader read errorOn some systems the boot loader would stop with a "Could not read file" error message, after a warning with code "BC01" had been displayed.

☯NVMe/M.2 disks not visibleOn some Intel 400 series chipsets existing NVMe or M.2 disks did not show up.

↶Newer M.2/NVMe disks not visibleIn some cases, newer M.2/NVMe disks were not displayed.

☯NVMe or M.2 disks not visibleIn some cases, existing NVMe or M.2 disks were not displayed.

↶Inaccessible Software RAIDsSome Software RAIDs have not been presented as such, but only as individual disks.

↶Incorrect entries in Windows File Explorer context menu The entries for Miray file images in the Windows File Explorer's context menu did not show the correct icons and labels.

↶Bootsetup fails on creating a BootstickWhen creating a boot stick in Boot Setup with the UEFI option activated, Boot Setup fails with the error "File cannot be written" when writing the 32-bit EFI extension.

☯Cloning with SmartCopy & FullCopy failsWhen trying to clone a disk that has no valid partitions in the partition table with SmartCopy or FullCopy, the process could not be started, the "Start" button remained deactivated.

☯Size Adjustment after copy/restoreIn a few cases, the copy cancels if 1M partition alignment is disabled in the advanced options and the target disk is used up to the capacity limit.

⇗Partitioner: Create new PartitionTableCreation of a new partition table sometimes failed at first try.

↶UEFI Boot failedBooting from USB drives, created with Boot Setup, failed on UEFI systems.

⇄Bootstick does not boot on certain UEFI systemsWhen booting the program from a USB stick, the UEFI boot files were not recognized by some UEFI systems and the boot process therefore failed.

⛐Crash when running long termIn a few cases and only on a limited number of systems, a resource issue led to the currently running app or the entire software environment to crash if the program had been running for a long time. This could happen regardless of the apps or tasks being executed during that time.

☯TRIM for NVMe DisksThe TRIM option for NVMe disks was not available in the apps for copying and restoring from an image.

☯Low Screen Resolution, only GreyscaleIn few cases on 64 bit systems, there was just a low screen resultion in greyscale available.

☯TRIM for NVMe DisksThe TRIM option for NVMe disks was not available in the apps for copying and restoring from an image.

☯CD/DVD Writer not found in BootSetupIn some cases, BootSetup did not find the CD/DVD writer, although it is present.

⇗Detection of Bitlocker VolumesVolumes that are encrypted using BitLocker are now detected and displayed as such; they will be copied in their original state, without any alterations.

⇗Multi-M2 Support with Intel-RSTWhen using more than one M.2 disk in a system with "NVMe Remapping" or "Intel Rapid Storage Technology" (Intel-RST) enabled, now all of the M.2 disks can be detected, not only one as before.

☯Linux-Shell App not workingAfter starting the Linux Shell App, there is still no Linux shell is not available.

⇄Opening After RenamingIf a file or folder had been renamed in Spot, confirming that with the <Enter> key led to the file or folder being renamed, but also (unexpectedly) to be also opened.

☯Double Entries for Network SharesIn some cases, there had been two entries for one network share (for example in Sopt or in the Network Share Applet). This also caused two different drive shortcuts to be assigned (like 'S:' or 'x01:').

⛐Missing Network Share Causes Apps to CrashIf a previously used network share was no longer available, for example because its host had been disconnected from the network or switched off, an attempt to access it with an App (e.g. Spot) crashed the App.

↶Bit-pattern Test w/o Write RunIn the 'Bit-pattern Test (4 runs) with Anti-Mirroring' the two write runs were skipped. The built-in verification recognized this error, so that in this case no successful test run was reported.

☯Creating a Bootstick FailedIf a USB stick was unformated but not completely empty, Boot Setup failed to make it bootable.

⇗USB 3 compatibility (TI Controllers)Certain Texas Instruments USB 3 controllers were not usable due to their non standard compliant behavior. After adding several workarounds for these issues, these controllers are fully usable now.

☯XFS file access in large foldersFolders with a large number of entries might have been missing some entries when being displayed (for example with Spot). Copies or images created from these disk were not affected.

↶Program crash on NTFS size adjustmentIn certain NTFS configurations, the final size adjustment (if selected) could result in a program crash.

☯Migrating Dynamic Disks: Target not bootableAfter Migrating Dynamic Disks (Windows), the target disk was not bootable.

☯migrating Dynamic Disks: Partition not accesibleWhen migrating Dynamic Disks (Windows), the first partition was not accessible on the target disk.

☯ISO-Imager report not storedIf the user saved a report in the ISO Imager, the associated steps could be carried out without an error message, but a report file was still not created.

☯Window boot issues after GPT conversionWhen converting to GPT, the boot configuration of Windows had not been adjusted correctly. As a result, booting Windows from the target disk failed.

☯Surface Tablet switches off automaticallyMicrosoft Surface Go tablets turned themselves off about 15 s after starting.

☯Touchscreen/Touchpad support improvedNow there are more built-in touch screens and touch pads supported.

☯Compatibility with older NTFSWith NTFS file systems, created with older versions of Windows (NT4 and earlier), in some cases compressed files could not be read.

☯USB token not recognizedIn some cases, the USB token was not recognized even though it was connected.

☯ISO-Imager report not storedIf the user saved a report in the ISO Imager, the associated steps could be carried out without an error message, but a report file was still not created.

☯DataSelect causes cancellationIn a few scenarios, utilizing DataSelect, HotCopy and other mechanisms at a time, the cloning or restore process could result in a failure, which then led to a automatic error cancellation of the process.

⇗HotCopy/LiveImageHotCopy and LiveImage now also works correctly, if Windows is configured not to mount every Volume automatically.

☯Boot Setup message shows faulty charactersThe message in Boot Setup, displayed when files on the boot stick could not be updated, may show incorrect text and/or Chinese characters.

☯Error with DirectRestoreIn few cases, file systems were not accessible on the target disk after it had been restored using DirectRestore.

☯4K alignment with failure in NTFSWhen Cloning or restoring an NTFS file systems from an image, cluster sizes of 2 KB or less in combination with the 4K alignment option could cause the process to hang or result in file system errors on the target disk.

⇗Accessing FAT file systems created with macOSIn FAT file systems, created by macOS, folders and files with the same name as the volume label could not be accessed.

⇗APFS SmartCopy and file accessVarious improvements for detection, copying and resizing of APFS file systems with lots of checkpoints/snapshots, including file access through Spot.

↶No files found on ReFSOn ReFS file systems, the existing files were not displayed. Images stored on a ReFS file system could therefore not be accessed for restore or to be mounted as Virtual Disks.

⇗GPT conversion for Windows 10When converting Windows 10 systems to GPT, using a different Windows version or without using Windows (self-booting), GPT conversion will now also work.

⇗Maintaining Linux bootabilityWhen copying and restoring Linux installations, additional Linux boot information is now taken into account. As a result, more different configurations of Linux can now be cloned or restored from an image while maintaining bootability, especially also with Suse Enterprise Linux.

☯Recognizing M.2 in MacBooksOn certain MacBooks (mainly from 2015 and 2017) the intregrated M.2 disk has not been not recongnized correctly.

☯No Access to Network SharesIn cases where the credentials for accessing a network share contained a comma character (','), the share could not be accessed.

↶Verification errors with HotCopy/LiveImageA small number of verification errors was reported on temporary files that had been changed by the system during the process. The copy/image was still correct.

☯"Safely remove disk" not applicableIn Windows, after restoring or copying to a disk, it could not be deregistered using the Windows "Safely Remove" function.

⇗Formating faulty boot sticks automaticallyIf the Boot Setup detects that a selected drive is faulty, the "Format Disk" option will automatically preselected automatically.

☯DataSelect delivers unformatted filesystemCertain NTFS configurations could lead to DataSelect not being able to delete all files, which could in some cases produce a file system error on the target, which then was reported as "unformated".

⛐PartitionCopy crashThe PartitionCopy App could crash in some cases after selecting source and target.

⛐SmartCopy crash on disk selectionDisks with unformatted partitions can trigger the SmartCopy app to crash in the disk selection element.

↶Clones/Images of Unformatted PartitionsIf the file system of a partition is shown as type "RAW" in Windowsn (usually meaning they are not formatted yet), it was not possible to create a copy or image from, since the access was denied by Windows.

☀MBR-to-GPT conversionCopying/Restoring allows the conversion of an MBR based partitioning scheme to a GPT based partitioning scheme. Operating systems offering UEFI support are adjusted accordingly as well.

☀OS-Adjust AppWith the OSAdjust app, operating system adjustments can also be made outside of copying processes or restoring from an image, in particular volume ID, partition ID and disk signature. Drivers can be customized and USB boot (if supported) can be activated.

◱VMImage image typesThe VM image types VMDK, VHD, VHDX, VDI and DMG now can also be created with a fixed size.

☀Migration AppThe new Migration apps (Disk and Partition) replace old versions and offer an improved experience.

☀Differential Image AppThe new Differential Image app (DeltaImage) replaces the old version and offers an improved experience.

☀PartitionCopy AppThe new PartitionCopy app replaces old version and offers an improved experience.

☀DirectRestore AppSimplifies the unchanged restoring of images / backups with identical size and without file system adjustments. Can also be used to prevent changes in partition sizes, the position of partitions on the disk or other adjustments for specific application scenarios.

☀PartitionRestore AppRestore a single partition from a disk image into an existing partition on the target. Other already existing partitions on the target are unaffected.

☀ImageConvert AppEasily convert an existing file image into a different image type. The original image will be preserved, the converted image will be created as a new file image. May also be used to consolidate an existing combination of base image, differential image and overlay into a new file image.

☀BitRestore AppA special app for BitImages to restore them 1:1 to a physical disk, without any changes in partition size, partition position, partition table and data.

☀Toolbox-Applet: New Auxiliary "Hex"The auxiliary "Hex" is now available as a hex editor for files in the toolbox applet in the system bar.

⊕Spot: Opening files in Pad or HexIt is now possible to open selected files in Spot by double-clicking or via the context menu (right-click). The hex editor "Hex" and the text editor "Pad" are currently available for this. All files of a multiple selection can also be opened via the context menu.

⇗Spot: Folder creation dateThe creation date for folders is now also displayed in Spot. This is also the case when there is a multiple selection of a mixture of folders and files.