Deep Freeze Standard 8.56.020.5542 Full Version
Cherie Trojak
Heres my question, So you cannot start deep freeze, but you cant disable or stop it either? so its running in the background but you cannot see anything except for the service? have you tried to go to the registry and remove all the keys associated with DF and then remove all the associated files on your system for DF and then try to remove the service? After all of this restart and try to reinstall if you want it or just leave it removed.
Secondly, Deep Freeze works (in part) through a low-level kernel driver for your hard disk and SATA/IDE bus. There is also a service that runs, and you can disable that service (don't: it will break your system). But you can't just remove a kernel driver by changing a few registry keys. You also need to make sure you have an equivalent kernel driver to handle the disk requests (normally now, rather using the frozen method).
The normal way to uninstall Deep Freeze is to re-run the installation program. If you can't do this, you can still boot from a different location like a CD or DVD and re-install your operating system. Most frozen computers will also disable booting from anywhere but the frozen hard disk in the BIOS, and then lock the BIOS to prevent changes. This means you may also need to hard-reset your BIOS.
It's all software in the end, so I suppose there must be a way to do this on a thawed computer without re-installing the operating system - but it's more than just changing the registry. You've got to alter some files (probably using VolumeShadowCopy) that are used by Windows itself.
I've heard, but not personally confirmed, that the way Deep Freeze enforces trial mode vs regular mode is through the system date. Standard mode will update it's trial expiration every time the computer starts. If you update the system time to 61 days in the future, you can force the machine to boot thawed.
Try this: First have another unit to install Deep Freeze and do not put any password.Then, boot thaw that unit. Copy the file at the root, c:\ "Persi0.*" (something like this). Paste it to the root of the drive that you want to unfreeze, voil! That machine will be unfreezed. You can now uninstall Deep Freeze after booting.
Try To Run Deepfreeze Installer again, it should then say you need to uninstall your current deepfreeze, proceed to uninstallation. A computer restart would be prompted afterwards which you should do.
23770 Resolved an issue where Deep Freeze Enterprise workstation showed Cloud Connector expired message after installing it on the machine where Deep Freeze Cloud was previously installed. (Case No. OUG-468-62852)
21566 Resolved an issue where, switching between multiple ports in Enterprise console while workstations are reporting in, the workstations continuing to report to the wrong port after changing the active port. (Case No: EPS-318-77915)
23113 Resolved an issue where using the Configuration Administrator in Windows 10 Fall Creators Update (64-bit) to repeatedly save then reload a configuration file would alter the available ThawSpaces.
Deep Freeze Enterprise 8.52 was released earlier today to all customers. Shortly after release, an issue regarding certificates was discovered, forcing the retraction of this release. An updated version of Deep Freeze Enterprise will be made available once the issue is corrected. We apologize for the inconvenience.
17579 Resolved issues with random BSOD. The Windows 10 Anniversary Update introduced additional drivers into the system that interfered with the ability of our drivers to properly respond to some requests to our StorageSpace or ThawSpaces.
17893 Resolved issues where Windows updates failed for some cumulative update which may require more space and a larger caching space than the 5GB that Deep Freeze allocated. Version 8.35 will allocate a 10GB cache to address this situation. To increase the size, disable the Cache Window update option in the configuration, restart, and re-enable the option.
17224 Resolved an issue where the workstation did not perform Deep Freeze specific commands initiated from Core console or Cloud console until the workstation connects to the Deep Freeze Enterprise console.
17225 Resolved an issue where upgrading Deep Freeze Workstations from Faronics Core console failed. This issue has been resolved for Deep Freeze 8.33 and above. However, users upgrading from 8.32 to 8.33 may still experience this issue. Contact Technical Support for workaround.
6297 For deployments over 500 workstations, when running Deep Freeze Tasks from the Enterprise console, workstations tasks are slow to complete. This issue was introduced in v7.5 and an upgrade of the clients to v7.6 is recommended to resolve it. (LKH-533-91318)
This is a beta version of Deep Freeze to conduct usability testing and refine features to be widely available in v7.5. If you wish to participate in the Deep Freeze beta program, please email us at deepfre...@faronics.com along with your contact details and why you would like to participate.
L216 On Windows 2003 Enterprise and Standard 64-bit systems: Resolved issue where the workstation restarts and does not install Deep Freeze Client through Faronics Core console. Only after the push install is successful, the installer starts and the install process is launched.
2085 Non-English localizations only: Resolved an issue that caused some strings related to the License to remain in English after applying a License Key in English and then switching to a different language.
This is a beta version of Deep Freeze intended to test compatibility with Windows 7. It has undergone a QA cycle. As with any beta product, this version should only be used if you have backed up all important data and are prepared to re-image client computers if something goes wrong.
1911 Resolved an issue that could cause an existing .rdx file to be unexpectedly deleted in a specific circumstance: If it was opened for editing in the Configuration Administrator and some disallowed settings are specified (such as an empty password), then a Save As command is issued with the existing name; the original file was deleted, but the new file fails to save because of the error in the configuration.
1668 Resolved an issue that could allow the left-hand pane of the Enterprise console to be resized all the way to the left until it was no longer visible and could not be moved back without a restart of the Enterprise console.
1880 Resolved issue where the Type field of the Passwords tab in the Configuration Administrator was user editable; if Type was modified, the specified password would not be accepted on a client computer.
942 Resolved issue that could allow a non-administrator user to kill Deep Freeze processes resulting in the icon not being displayed in the system tray and loss of communication with the Enterprise console (the machine would remain Frozen)
1167 Resolved issue that could cause an abnormal program termination error to appear on a workstation after using the Unlock command in the Enterprise console if a VNC session had previously been used to clear the lock message on the workstation
Founded in 1996, Faronics is headquartered in Vancouver, British Columbia and is a privately-held company with nearly 30,000 unique customers using over 10 million licenses in over 150 countries. Faronics has a history of providing excellent value to customers, selling direct and through channel partners to enhance existing relationships, local presence, and value-added services.
It can be a pain when you are trying to do updates as you have to thaw the machine, reboot, make your changes and refreeze again. It adds about five minutes to your workload but if you really need to lock down a machine then it works great.
We also use it in a library environment, and so far it has been one of the best problem preventing solutions we could have. To save yourself some time, be sure to use the central administrator version. Some of the key features that we found valuable were of course the system freezing, the ability to create a drive that is accessible to a user that is not frozen, the ability to schedule maintenance times for the machines to thaw themselves and lockout the users during this time, and the ability through the Central Admin Console to mass freeze and thaw without having to punch in a password multiple times.
Deep Freeze has been a godsend for our company. Hands down the best piece of software we use. It works great on computers that need to be on 24-7/computers that are open to the public (kiosk computers). System and file integrity always stay the same and it keeps your computer running like new.
I tried contacting faronics on 6 different occasions, absolutely no answers. I see Standard Edition for $45, but it says something like 1 year maintenance package. I was trying to ask them what that means. Is the program only active for 1 year and then you have to renew it? Or is it a one time key/installation that lasts forever? Anyone here ever buy it?
The licenses are a one time purchase, but the Support means you are getting updates and support for it. If you don't pay it, good luck! I had a ticket with Faronics that went on for 4 months, at the end of the 4th month they told me they wouldn't continue to work on the issue unless support was paid for. Being in the situation I was in I moved on to an alternative solution.
If you're using Deep Freeze Standard, there's a freeware alternative called Reboot Restore Rx. Dunno where you stand on paying those support fees, but might be worth switching over if only for some pretty hefty cost savings!