We sincerely apologize for the inconvenience that this issue may have caused. We are implementing additional checks in our build and QA processes to better identify erroneous drivers to avoid this from happening in the future. On Monday night (Nov 1), our engineers reverted the incorrectly built driver to prevent further spread of this issue. After the automatic update, the system would become stuck and unable to complete the boot process into Windows.
Unfortunately, this update included an incorrectly built driver of our software that would get automatically updated (if an old version is found) by the “self-healing” functionality that Deep Freeze Cloud includes. On Friday night (Oct 29), Deep Freeze Cloud released an update to provide Server OS support for Deep Freeze. As we investigated the issue further, we found that the issue was not related to the Windows Updates(s) applied over the weekend but rather an update we introduced in Deep Freeze Cloud. Initially, the issue appeared to be related to the most recent Windows Updates as the bulk of the customers who reported this issue ran maintenance tasks over the weekend.
On Monday, Nov 1st, Faronics was made aware of some issues where Deep Freeze Cloud customers running the Deep Freeze product were not booting up properly. Posted by Adam Zilliax on 01 November 2021 04:48 PM
0 kommentar(er)
