A subsequent known issue emerged with the release of Deep Freeze 8.71. The 8.71 console was unable to see the activation status of clients running Deep Freeze 8.63 and earlier versions. This issue did not require re-activation after upgrading, but customers could work around it by updating the license key in the 8.63 console and allowing client devices to be reactivated with the updated key before upgrading to 8.71.
If an upgrade to Deep Freeze 8.63 requires a license key update (this is more common when jumping multiple major versions), ensure that the updated key is applied to the console upgrading client workstations. For organizations eventually upgrading to version 8.71 or later, activating the updated key in the 8.63 console first and allowing client devices to reactivate can prevent activation-related issues down the line.
Select the Thawed workstations, right-click, and choose . Point the console to the new 8.63 installation package.
:: Check exit code if %errorlevel% equ 0 ( echo Patch installed successfully. ) else ( echo Error %errorlevel% - check %temp%\DFPatch.log ) Deep Freeze 8.63 Patch
Are you using the or the On-Premise Enterprise Console ?
To get the highest return on investment from your Deep Freeze deployment, incorporate these structural best practices into your network topology: Leverage Data Igloos for User Data Persistence
While the 8.63 patch resolves many legacy bugs, certain environmental factors can cause installation issues. A subsequent known issue emerged with the release
Deep Freeze automatically detects Windows Update cycles, downloads patches while Thawed, and freezes the machine once installation finishes. 6. Troubleshooting Common Issues in Patch 8.63
Maximize the efficiency of Deep Freeze 8.63 by integrating these habits into your IT workflow.
43598 Resolved an issue where workstations were randomly hanging with no discernable pattern. ( Case No. WPD-530-71307) Version 8. Deep Freeze Enterprise Latest Version and Release Notes If an upgrade to Deep Freeze 8
Some aggressive Endpoint Detection and Response (EDR) agents may flag the deep-level drivers of patch 8.63 as suspicious. Add the Deep Freeze installation directory ( C:\Program Files (x86)\Faronics ) to your antivirus exclusion list. Conclusion
While the 8.63 patch resolves numerous legacy bugs, environmental variables can occasionally cause installation hurdles.
Deep Freeze 8.63 represents a significant milestone in Faronics’ ongoing commitment to providing robust, reboot-to-restore protection for Windows environments. While it brought critical fixes for Windows 10 hangs, RDP reboot anomalies, Windows Update boot issues, and console stability problems, the version was not without its own challenges—including post-release boot failure issues and compatibility concerns with newer console versions.
Detailed release notes can be found on the Faronics Enterprise Release Notes and Standard Release Notes pages. Deep Freeze Server Standard Release Notes - Faronics