Hello，各位卡饭的小伙伴们，
感谢你们的提醒，让我注意到这个bug，老实说我在上卡饭之前并不知道SEP中文版有这个隔离区的bug，感谢你们的帖子让我注意到了这个问题。
我在自己的Lab环境中复现了这个问题，联系研发确认了这个问题的存在，目前研发已经开始着手修复，且发现这个问题出现在所有的中文版本SEP中，属于历史遗留问题，经过N多个版本迭代到现在，研发人员表示这个遗留代码处理起来需要非常小心，因此需要一定的时间来修复。
我截取了最新的回复，供大家参考：
--------------------------------------------------------------
After troubleshooting I figured out that the VBIN created itself now writes incorrect Filename so while restoring the file it is not able to get the correct filename hence it is not able to restore it. I used Qextract4 tool to extract the VBIN created in the Quarantine folder and it extracted file but with exit code 1 which means it failed to extract incorrectly. Here is the output: C:\test\Quarantine\22680000>QExtract4.exe /x /f:C:\test\Quarantine\22680000\67FFE032.VBN /lsum.log /g =================================================================== QExtract4 v1.0.11.0 - (November 26 2018)
Copyright (c) 2014-2018 Symantec Corporation. All rights reserved. THIS IS FOR SYMANTEC INTERNAL USE ONLY!
It is PROPRIETARY and CONFIDENTIAL property of Symantec Corporation. =================================================================== `Command line /g acknowledges usage restrictions`
PASS`C:\test\Quarantine\22680000\67FFE032.VBN`Sep 12.1`???`VID 15861`size ???`status 0`Eraser remediation`FileRemediation```
`Exit code is 1` C:\test\Quarantine\22680000> This proves the issue is there since beginning. VBIN file created was having Chinese characters in the description which is not stored correctly.
Likewise there could be other fields which might be written to VBIN. I need to test the VBIN creation code now. Since this is legacy code it is very much critical to handle so it is taking time to fix it. Will now work on VBIN creation logic. -------------------------------------------------------------------------
最后，我会定期更新关于这个Bug的修复进展。
| 
发表于 
