Home | Site Map | Cisco How ToNet How To | Wireless |Search | Forums | Services | Donations | Careers | About Us | Contact Us|

Malwarebytes failed to stop service win32 error code 1062

Permissions, Group Policy, IPSec, Virus, Spam, Spyware, Malware.

Malwarebytes failed to stop service win32 error code 1062

Postby chicagotech » Wed May 17, 2017 11:43 am

Situation: When attempting to upgrade Malwarebytes on a client, you may receive this message: failed to stop service. win32 error code 1062

Troubleshooting: 1. Uninstall old Malwarebytes.
2. Run Malwarebytes cleartool.
3. If you did 1 and 2, you may want to reboot the client.
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
chicagotech
Site Admin
 
Posts: 6751
Joined: Mon Nov 27, 2006 1:24 pm
Location: Chicago USA

Re: Malwarebytes failed to stop service win32 error code 1062

Postby chicagotech » Wed May 24, 2017 2:59 pm

If the clean tool doesn't fix the problem, try this.

Please have a look at the system requirements below, which need to be fulfilled on the target machine for the client push feature to work. I'm suspecting that something is missing on that machine.

The following prerequisites must be met for all Managed Clients (Endpoints) using the Malwarebytes Management Console:
• .NET Framework 3.5
• Windows Installer 4.0 or higher
• File and Printer sharing enabled
• NetBIOS enabled
• Network Discovery enabled
Regarding Firewalls:
The following is a list of ports that are commonly used for operation of the Malwarebytes Management Console.
Management Server Ports:
• 53: Domain Name Services (DNS) lookups
• 137: NetBIOS Name Resolution
• 139: NetBIOS Session Service
• 389: Active Directory (AD) authentication
• 443: Default Management Server port
• 18457: Default client communication port
Client Ports:
• 135: Process control related to file transfers to/from server
• 137: NetBIOS Name Resolution
• 445: File transfers from server associated with install, uninstall and simulations
• 18457: Default client communication port


(All ports are TCP)
If the normal push method does not work you can try pushing with WMI, please make sure port 135 as described above is allowed in your firewall settings on the clients.


Please note that I don't recommend to use the 'Client Push' feature for bigger environments or if the above requirements can't be fulfilled. The easier way to deploy clients on targets is by creating an 'Installation Package' through the Management Console and then deploying the executable through Group Policy, a software deployment solution or just by copying the file to the endpoint.
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
chicagotech
Site Admin
 
Posts: 6751
Joined: Mon Nov 27, 2006 1:24 pm
Location: Chicago USA


Return to Security

Your Ad Here

Who is online

Users browsing this forum: No registered users and 3 guests