HKEY_CURRENT_USER\SOFTWARE\System32 (Backdoor.Bifrose) -> No action taken.Ģnd MBAM Log: After Quarantine the suspect item: The first MBAM Scan results with Backdoor.Bifrose detected, and the second scan log, where it was placed in quarantine and everything looks fine. Still, at Mieke's suggestion that Bifrose might be still be present, I post here the HijackThis Log (after I quarantined the Backdoor.Bifrose through MBAM), and the two Logs from MBAM. I run, another MBAM Scan, and this time nothing was detected. After consulting Mieke, at the MBAM general forum I quarantined the item. The results detected Backdoor.Bifrose at the registry key HKEY_CURRENT_USER\SOFTWARE\System32. I understand that the main problem is that my new/changed data is not being duplicated during the times it is disabled, but is there any other problems that this would cause?įYI I'm running WHS on 1 gb of ram, Athlon XP 1800 CPU, and 3 seagate 250 gb SATA drives, and 1 seagate 250 IDE drive.As usual, today I run a quick scan on my pc with MBAM. So, I had the idea of writing a simple script and scheduling it to enable the demigrator service in the middle of the night and disable it in the morning. As many have found there is no way to change the priority on the demigrator.exe service.
It take 2 - 3 times longer to read or write to or from the server when storage is balancing.
CPU seems to be OK, at around 10% while it runs, but the disk activity is really bad.
I know that this isn't supported by MS, but is there any reason why it would be bad to disable the service at certain intervals, besides the obvious disadvantage of data not being duplicated while the service is disabled?ĭemigrator.exe seems to run quite frequently and it seems to really hog up the server while running. I have a question about the drive extender migrator service.
0 kommentar(er)
