![]() Renaming the file back and rebooting resulted in the same boot failure requiring renaming it again from the iso repair environment. After getting back into Windows the Sophos endpoint showed service failures due to Sophos Endpoint Defense Mini-Filter (SophosED) stopped that didn't resolve after manually updating or rebooting. Renaming that file as Jak pointed out has fixed the Windows boot failure. Startup repair attempt from the 2008 R2 iso environment failed but the log from that indicated Boot critical file \windows\system32\drivers\sophosed.sys is corrupt. Same failure attempting boot into safe mode or repair from the OS boot menu. Boot attempts resulted in Status: 0xc0000225 Info: The boot selection failed because a required device is inaccessible. ![]() Ran into boot failure for the same reason on a Server 2008 R2 圆4 (not sp1) ESXi vm running Sophos Central Endpoint Agent 2.6.0 BETA.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |