Symptom: A machine was working fine (Frozen), then Windows Update installed a new "Feature Update" (e.g., 22H2 to 23H2). Now it says "pending activation new." Cause: Windows Feature Updates rewrite the Boot Configuration Data (BCD). Deep Freeze sees this as a "new" boot environment. Solution: You must reinstall Deep Freeze after major Windows feature updates. Plan for this in your maintenance cycles.
Believe it or not, 80% of "pending activation" cases are solved by a single restart.
Windows Fast Startup (Hybrid Boot) often causes Deep Freeze activation to hang because the OS does not perform a full hardware initialization.
Deep Freeze, developed by Faronics, is a kernel-level driver application used to "freeze" a computer's configuration. It restores a workstation to its original state upon every reboot, effectively eliminating configuration drift, software corruption, and malware persistence.
However, administrators often encounter a confusing status message in the Deep Freeze Enterprise Console: "Pending Activation (New)."
This article details the technical background of this status, why it occurs, how it differs from other "Pending" states, and best practices for resolving it. deep freeze pending activation new
If you provide more context (school PC, personal PC, error dialog box), I can give more specific steps.
Deep Freeze Pending Activation New: How to Fix This Status and Secure Your System
Deep Freeze is a powerful kernel-level protection software designed to restore a computer to its original configuration upon every restart. It is widely used in schools, libraries, and corporate environments to prevent unauthorized changes and malware persistence. However, users often encounter a frustrating status message in the Enterprise Console or local interface: "Pending Activation." When this status appears on a new installation, it means the software is installed but not yet fully licensed or communicating with the activation server.
The "Pending Activation" status typically occurs during the initial deployment phase. While the software may appear to be working, it is essentially in a grace period. If this isn't resolved, the software may eventually disable its protection features or stop responding to console commands, leaving your workstation vulnerable. Understanding why this happens and how to push the activation through is essential for any system administrator.
One of the most common causes for a pending activation on a new install is a network communication error. Deep Freeze needs to "call home" to the Faronics activation servers to verify the license key. If your organization uses a strict firewall or a proxy server, the activation request might be blocked. You must ensure that the workstation has outbound access to the specific URLs and ports required by Faronics. Typically, this involves whitelisting the activation server addresses in your security appliance to allow the encrypted handshake to complete. Symptom: A machine was working fine (Frozen), then
Another frequent culprit is an incorrect or expired license key. During the "new" setup phase, it is easy to accidentally input a trial key or a key from a previous version that isn't compatible with the latest build. If the console sees a mismatch between the installed version and the license permissions, it will hold the status at "Pending." Double-checking the license tab in the Deep Freeze Enterprise Console is a vital troubleshooting step. If the key is correct, you might need to manually trigger the activation by right-clicking the workstation in the console and selecting the option to activate online.
In some cases, the issue is related to the "Frozen" state of the machine itself. If you attempt to activate a machine while it is in a Frozen state, any changes made to the licensing files during that session will be discarded upon reboot. This creates a loop where the software tries to activate, succeeds temporarily, but reverts to "Pending" after a restart. To fix this, you must "Thaw" the machine, perform the activation process, ensure the status changes to "Activated," and then re-freeze the system. This ensures the license token is permanently written to the hard drive.
For large-scale deployments, the Deep Freeze Cloud or Enterprise Console offers automated tools to handle these "new" activations. If you see a large group of machines stuck in "Pending," you can use the command-line interface (CLI) or the console's "Update License" task. Pushing a fresh configuration file that includes the correct license key often forces the workstations to re-attempt the activation process. If the status persists, checking the local logs on the workstation can provide specific error codes that point to whether the issue is a DNS failure, a timeout, or a rejected key.
In summary, seeing "Deep Freeze Pending Activation New" is a sign that your deployment is incomplete. By verifying network connectivity, ensuring the machine is in a Thawed state during the license application, and confirming the validity of your license key, you can move your workstations from a vulnerable pending state to a fully protected, activated status. Regular monitoring of your console will help you catch these issues early before the grace period expires.
Are you using the Cloud version or the On-Premise Enterprise console? Are the machines currently Frozen or Thawed? Result: Full reboots will now complete the activation
Are you seeing a specific error code (like 0xc0000005) next to the status?
On your personal PC?
Is it stuck?
Before fixing the error, we must understand the state. Deep Freeze is a "reboot-to-restore" software that freezes a computer’s desired configuration. When you see "Deep Freeze Pending Activation New," it typically indicates one of three scenarios:
In short, the word "Pending" means the system is in a transitional state. The word "New" suggests this is the first activation cycle for that specific installation or policy.
Older versions of Deep Freeze (pre-8.5) had significant issues with Windows 10/11 Fast Startup and NVMe SSDs. If you see "pending activation new" consistently, upgrade to Deep Freeze 9.0 or later. The newer versions handle UEFI bootloaders and modern storage drivers more reliably.