I have installed Sophos SafeGuard 5.5 on 3 HP laptops for testing and all 3 are displaying Delayed Write Failed. Has anyone else had this problem?
Thanks in advance
This thread was automatically locked due to age.
We're deploying 5.50.0.116 and I've seen this on only a few of many HP laptops, both during and after initial encryption. I was advised by Sophos to try adding the AllocMode=1 registry value before installing the Sophos kernel, which I also found documented here: http://downloads.sophos.com/readmes/readsde_5_eng.html, from which this was copied:
Hive: HKEY_LOCAL_MACHINE
Key: System\CurrentControlSet\Control\Session Manager
Value Name: AllocMode (DWORD)
Value: 1
We're testing adding this to computers that already have the kernel installed and also on those that don't. Since we have a very small sample size and the problem hasn't been consistent for us, it may be difficult to draw meaningful conclusions. Any additional experiences, suggestions, or details from anyone else who has seen this would be appreciated.
Thanks!
The AllocMode registry entry will only be helpful before you install SafeGuard. If the entry is added in after the Safeguard kernel has been initialized, it will have no effect. The allocmode entry changes the way the kernel gets installed in the first place.
Going forward, it solved all of our delayed write failed messages we had on Lenovo machines. We ended up rebuilding ones that were already affected, as we were not confident in the state of the data on them any longer.