Jump to content


  • Posts

  • Joined

  • Last visited


0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I switched from Win7 pro to Win10 pro at the end of last year. The version 1909 was installed. Since then the computer doesn't go into energy saving mode anymore. The screen gets dark, but the computer continues to run fully. But in the internet and in various forums I didn't find anything suitable. Also the option Suspend update for 7 days does nothing. Then I found out that the problem is caused by the Update Orchestrator service (UsoSvc service). As soon as this service is executed, the computer does not go into energy saving mode anymore. The service is always activated again when the computer is switched on. The reason is probably task scheduling: - Microsoft - Windows - UpdateOrchestrator - Universal Orchestrator Start - Conditions - Power: Reactivate computer to run the Task This setting cannot be deactivated by me because it is password protected. Since none of the workarounds described on the Internet work, I use the following procedure: After computer startup, call services and check if the UsoSvc service is active. If it is, stop it and deactivate the service in any case. Then it works for me without any problems, even if the computer is turned off in the meantime until the next day when the computer is turned on again. As far as I can tell, the problem has nothing to do with malware bytes.
  2. I found the problem on my computer. It is not MWB but Win10 1909 with the latest update, namely the UsoSvc service (Update-Orchestrator-Service). When the service is active, it prevents the system from going into sleep mode. If the service is stopped or deactivated, the energy saving mode works fine. I only recently switched to Win10, then came the MWB update, so I suspected MWB.
  3. For everyone's info: we don't need to do anything if ""studies" is enabled (Firefox Preferences -> Privacy & Security -> Allow Firefox to install and run studies). After activating it again all Add-Ons are back
  4. Hello to all who gave me some advice I set the properties to "Automatic (Delayed Start)" After several error-free system starts I thing that is a solution no more unexpected "normal at system start" scan and no DDA Driver and Real-Time Protection failure again. thanks
  5. Hello vbarytskyy Tried it three times with delay and it worked But the point is, it worked fine with MB 3.4.4 thank you
  6. Hello Malwarebyte Win7 x64 SP1 The fault occurs always after the computer is started after a complete shut down. The "normal at system start" scan entry is always shown again, and I think that is is the cause of the DDA Driver and Real-Time Protection failure. When I delete the "normal at system start" scan and restart the computer, MB starts and runs without problems. After a shut down and new start the problem is back again. This problem does not occur at my Win10 system
  7. Here are the logs, taken after DDA and Real Time Protection error normal scan at system start turnd up again FRST.txt Addition.txt mb-check-results.zip
  8. Here are the logs, taken after DDA error normal scan at systems start turnd up again mb-check-results.zip FRST.txt Addition.txt
  9. Hello Malwarebyte Win7 x64 SP1 After starting the computer I often get the message: Malwarebytes in unable to load the Anti-Rootkit DDA Driver (shows up after opening MB) and Real-Time Protection disabled, unable to switch it on I set up two scans (see below), Normal scan ist set to 21:45:00 (24 hours) that is PM time But some times after system start MB is trying to run two scans at the same time (see below). I dont know where it comes from. Possibly MB gets mixed up with AM and PM time. The second Normal is at AM time. after deleting the second Normal scan, MB is working properly for a while. This behaviour did not occur with MB 3.4.4 I already cleaned and reinstalled MB.
  10. Hello Malwarebyte Component 1.0.236 Win7 x64 SP1 AVIRA Antivirus Pro After starting the computer I often get the message "Malwarebytes in unable to load the Anti-Rootkit DDA Driver" I tried the solution "Never register Malwarebytes in the Windows Action Center" but the problem still persists. If the problem occurs the Scan Schedule shows the following If no problem occurs the Scan Schedule shows the following Sysopa
Back to top
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.