What's new in InstantRecovery Build 322
- Fixed Windows crash caused by the InstantRecovery security driver. The security driver is only found in InstantRecovery Business editions.
- Optimizations to the Copy Engine.
What's new in InstantRecovery Build 321
- The Manager for Home now requires Administrator privileges. This is so Schedules will work correctly.
- The Copy Engine reserved stack size has been doubled to 32MB.
- Fixed issue where some Reparse Points were not being removed from a snapshot.
What's new in InstantRecovery Build 318
- Fixed issue when remote controlling InstantRecovery, the CONNECT command would fail with the error: "Remote user does not have Admin rights". See the Advanced > Remote Controlling InstantRecovery section of Help for more information on configuring for remote control.
What's new in InstantRecovery Build 317
- CopyEngine buffer size increased.
- Fixed issue if Boot Splash Delay is configured for 1 second. Native-mode Pr-Boot would display "Press F1 for Boot Options in 4294967279 seconds".
- Fixed issue with Copy/Verify and Windows 10.
What's new in InstantRecovery Build 316
- The Security Driver is now enabled by default for InstantRecovery Professional and Server. As before, the Security Driver can only be disabled and re-enabled with the CLI. The Security Driver is not available in InstantRecovery Home.
- The status of the Security Driver is now shown in the Info Box of the Manager.
- The CLI now notes that a reboot is required after disabling the Security Driver. Unlike uninstall, the Security Driver is still active until the next reboot.
- Security Driver info now included in Support Info in the Registry section.
- The name of the Security Driver is now irecsd.sys and the description is "InstantRecovery Security Driver".
- Uninstall deactivates the Security Driver but it is not fully removed until the next reboot. It does not have to happen immediately but will need to be done before a reinstall. This will affect an update. You will need to uninstall, reboot and then reinstall. The installer now always prompts for reboot after uninstall. It also checks that a reboot was done before a reinstall.
- When the Anchored File list includes a linked file (Junction, Symbolic or Hard) it causes the pre-boot to fail. The anchored file must be the actual name of the file. An error is now returned when anchoring a file or folder whose name includes a linked folder or file. If Windows supports it, the actual file name is shown in the error message.
- Archives are no longer NTFS compressed. This is because NTFS does a horrible job of allocating large compressed files. This change was made several versions ago but was not well documented.
- Now, when an archive is created, the file is allocated the full estimated file size. At completion, the file is trimmed to the actual size. This greatly reduces fragmentation of the file. On a clean system, there is no fragmentation.
- An error is now generated if after a copy operation less than 20 GB will remain on the system volume. If the destination disk is not the system volume the check is only for sufficient disk space.
- The insufficient disk space error now notes the System Reserve space and references the help file for more information.
- The IR icon now displayed in the Remove Programs list (Control Panel). It used to just be a default icon.
- The Tray Icon options have been changed to be more consistent. It now says "Never show" instead of "No tray Icon".
- The Data Anchoring screen for Getting Started and the Introduction screen for Data Anchoring have been changed to urge the user to anchor any cloud-based folders.
- The option for "" has been removed from the copy wizards. It is an advanced feature not appropriate in a wizard. You can still create a compressed snapshot with the CLI.
- An error is now displayed if the keyboard fails in the native-mode pre-boot. Previously, it flashed by too quickly.
What's new in InstantRecovery Build 314
- Fixed an issue under Windows 10 where a empty folder being removed from a snapshot fails with a "Directory not empty" error - even though all files in it have been removed.
- GUI fixes to be consistent in how KB, MB, GB are displayed.
- Background color on splash screen changed to better match the image when the size of the GUI is increased.
- Fixed last screen of Rename Archive - the screen said Next instead of Finish.
What's new in InstantRecovery Build 311
- With Windows 8 and Windows 10, the security on a folder under WindowsApps was sometimes not copied correctly. This resulted in an Access Denied error when updating files in the folder at a later time.
What's new in InstantRecovery Build 310
- Native-mode pre-boot supports multiple keyboards.
- Fixed snapshot order bug that caused an issue with booting to password protected snapshots.
- Create Empty Snapshot no longer disabled for native-mode pre-boot. Instead a message is displayed when the user selects it from the menu.
- Windows 10 supported - gets volume GUID without using MountedDevices.
- TPM (Trusted Platform Module) enabled check in installer and ISRSetup. Installer warns and allows user to cancel install. ISRSetup uses native-mode pre-boot if TPM enabled.
- BIOS Pre-boot now shows selected snapshot when booting to a snapshot from the Manager.
- Fix for Reparse Point to a Compressed file.
What's new in InstantRecovery Build 307
- Fixed an access denied issue in ISRSetup.
- Increased Stack Size in RemoveAll.
What's new in InstantRecovery Build 306
- Support has been added for GPT (Guid Partition Table) drives.
- Fixed SSN::GetTempFileName - Access is denied issue.
- Fixed an issue with updating a recovery snapshot in Windows 8.x where tiles do not show.
- Schedule rename issue fixed.
What's new in InstantRecovery Build 302
Updating to a newer build of InstantRecovery requires several steps:
- On install, improved detection and notification of unsupported configurations.
- Improved speed in creating/updating archives.
- Default Boot Delay changed from 2 seconds to 20 seconds.
- Fixed Run-time Error 424 issue when opening a URL from within the GUI.
- Fixed GUI crash due to archives with a space in the archive file name before the .arx extension.
After installation, when you next run InstantRecovery, you will see your existing snapshots.
- Uninstall the existing build of InstantRecovery. When prompted to Remove Program Only or Remove All, select Remove Program Only.
- Install the new build of InstantRecovery.
Warning: If you select Remove All during uninstall, all of your existing snapshots will be deleted and you will not be protected until you create a new recovery snapshot.