Is the faulty symlink always MpEvMsg.dll, or is this just an example?
In case it's always MpEvMsg.dll:Of course this doesn't remove ZeroAccess, but fixes the SFC problem(?) Or is this not the whole story
- delete the symlink
- reinstall microsoft security essentials
It's always on MpEvMsg.dll but there are many other files. I can't go into any details on the security side of things I'm afraid as I haven't finished my training yet, I just wanted to give you guys a heads up if you see SFC failing with this error
My Computer
At a glance
Windows 8.1 Pro x64Intel i7 3770K @4.5GHzCorsair Vengeance 2x4GB DDR3 1600MHz Low Prof...Gigabyte Radeon HD 7850 (2GB GDDR5)
- Computer type
- PC/Desktop
- Computer Manufacturer/Model Number
- Build #1
- OS
- Windows 8.1 Pro x64
- CPU
- Intel i7 3770K @4.5GHz
- Motherboard
- ASUS P8Z77-V PRO
- Memory
- Corsair Vengeance 2x4GB DDR3 1600MHz Low Profile (White)
- Graphics Card(s)
- Gigabyte Radeon HD 7850 (2GB GDDR5)
- Sound Card
- Integrated on motherboard
- Monitor(s) Displays
- 23" LG LCD/LED IPS
- Screen Resolution
- 1920*1080
- Hard Drives
- Samsung EVO 128GB SSD
Seagate Barracuda 2GB 7200rpm
2x Seagate FreeAgent [500gb]
- PSU
- Corsair TX650W V2 (80+ Bronze)
- Case
- NZXT Phantom 410 White
- Cooling
- Corsair H100 Water Cooler
- Keyboard
- Microsoft Desktop 2000 Wireless Keyboard
- Mouse
- Microsoft Desktop 2000 Wireless Mouse
- Internet Speed
- 95 Mb/s Download 70 Mb/s Upload
- Antivirus
- MSE + MBAM Pro
- Browser
- Firefox



