Administrators in large-scale environments (e.g., a university with 5,000 workstations) need stability above all else. This patch addresses specific bugs that could cause Frozen machines to experience unexpected reboots or fail to enter "Thawed" mode when scheduled via the . 4. Better Support for Virtualized Environments
The "Patch" component usually refers to upgrading from a previous build (e.g., 8.62.x) to the latest 8.63 build. Notably, Deep Freeze 8.63 is the to fully support Windows 7/8.1 legacy systems while introducing full compatibility with Windows 11 22H2 and Windows Server 2022. Deep Freeze 8.63 Patch
If you already have Deep Freeze 8.6x installed and you are in a , you can perform an in-place upgrade. Command line deployment sample: Administrators in large-scale environments (e
| Issue | Status | Workaround | | :--- | :--- | :--- | | | Under review | Disable BitLocker on the system drive before installing 8.63, then re-enable. The patch improves compatibility but does not resolve 100% of scenarios with TPM 2.0. | | Windows Defender Exclusions reset | Patched in hotfix | Manually re-add C:\Program Files\Faronics\Deep Freeze\* to Defender exclusions after patching. | | Mac Agent incompatibility | Not applicable | Deep Freeze 8.63 is Windows-only. Mac users remain on version 7.x or Cloud variant. | | Console connection via IPv6 | Partial fix | Use hostnames or IPv4 addresses for reliable wake/push. | Command line deployment sample: | Issue | Status
:: Check exit code if %errorlevel% equ 0 ( echo Patch installed successfully. ) else ( echo Error %errorlevel% - check %temp%\DFPatch.log )
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.