Direkt zum Inhalt

My Acronis Managed Machine Service Mini Service Will Not Start

Thread needs solution

So I have been using this product since 2006 or so.  This is the only release that I can't quite get to run correctly.  The active protection seems to work but I really cannot tell because so many of the module, including updates do not work.  So in my troubleshooting efforts, I checked all of my acronis services and found that the mmsminisrv service will not start on my computer (error 1053).

I have tried:

  • Uninstalling my antivirus
  • Turning off the firewall while troubleshooting
  • Removing the file from C:\ProgramData\Acronis\BackupAndRecovery\MMSData\DML and restarting the service
  • Taking ownership of C:\ProgramData\Acronis\*.*

Contacting acronis support is unproductive.

I believe that this service is preventing a whole lot of other things from starting correctly in the protection module.  I cannot even load or save any settings.  Downloading new protection files won't work either.  Check out the upload to see that I cannot even add exclusions to the program anymore and don't know if my exclusions from Acronis 2020 made it into the 2021 release.  I downgraded to 2020 for awhile but thought:  I am paying for upgrades and should not have settle for a product that does not function the way it used to (which was flawless).  In general I liked the cryptomining protection in 2020, but think this new antivirus addon is unnecessary bloat.  I have antivirus protection already.

Finally, the computer with the problem does not appear in my online dashboard, but another computer on this license does (my son's).  

Anhang Größe
Screenshot 2021-01-18 165309.png 120.39 KB
0 Users found this helpful

You might try this:

Open and Admin PowerShell prompt and type: SFC /scannow

This will run Windows System File Checker which will check your Windows System Files for corrupt files.

The 1053 error is a timeout error in which the Service Control Manager does not receive an answer from the service in a proper time period which is less than 30 seconds.  When this occurs the SCM shutdowns the service preventing starting or stopping the service.  This is at times due to an error in Windows System Registry.  The System File Checker should fix the error.  If errors are reported corrected run the command again and repeat until no more errors are reported.