Jump to content

cant update

Recommended Posts

i cant update malwarebytes,i did notice my home page went back to defaults.

i am not sure why this happened i dont think its down to malware,it mabye a mistake on my end however i am really not sure,ive been working hard to disifect my daughters laptop and got a bit exhaused doing so and may off made a mistake,still dont think i did.

i did notice somthing about m/bytes useing i.e and changeing the settings hence mentiong the home page point,i am not sure if any changes where made to i.e.

also read about ceratin process blocking m/bytes but i cant find any.

(will inc log off process just in case)

i unistalled m/bytes and reinstalled to no avail

i was thinking about unistalling then removing the folder or useing revosetup to remove all traces off m/bytes but this is a last resort as this program is pretty powerfull and may not be a good idea,if i can sort this out without re-installing (just formatted) revosetup

i would obviosly prefer

log off runnng process;

Process PID CPU Description Company Name

System Idle Process 0 98.46

Interrupts n/a Hardware Interrupts

DPCs n/a Deferred Procedure Calls

System 4

smss.exe 368 Windows NT Session Manager Microsoft Corporation

csrss.exe 436 Client Server Runtime Process Microsoft Corporation

winlogon.exe 460 Windows NT Logon Application Microsoft Corporation

services.exe 504 Services and Controller app Microsoft Corporation

WRConsumerService.exe 664 WRConsumerService Webroot Software, Inc.

svchost.exe 680 Generic Host Process for Win32 Services Microsoft Corporation

svchost.exe 752 Generic Host Process for Win32 Services Microsoft Corporation

svchost.exe 788 Generic Host Process for Win32 Services Microsoft Corporation

svchost.exe 844 Generic Host Process for Win32 Services Microsoft Corporation

svchost.exe 936 Generic Host Process for Win32 Services Microsoft Corporation

vsmon.exe 956 TrueVector Service Check Point Software Technologies LTD

spoolsv.exe 1400 Spooler SubSystem App Microsoft Corporation

svchost.exe 1632 Generic Host Process for Win32 Services Microsoft Corporation

SpySweeper.exe 1708 Spy Sweeper Engine Webroot Software, Inc. (www.webroot.com)

SSU.exe 1100 Spy Sweeper SSU Webroot Software, Inc. (www.webroot.com)

alg.exe 1196 Application Layer Gateway Service Microsoft Corporation

lsass.exe 516 LSA Shell (Export Version) Microsoft Corporation

explorer.exe 1360 Windows Explorer Microsoft Corporation

soundman.exe 1816 Realtek Sound Manager Realtek Semiconductor Corp.

zlclient.exe 1824 ZoneAlarm Client Check Point Software Technologies LTD

SpySweeperUI.exe 1832 Spy Sweeper Client Executable Webroot Software, Inc.

ctfmon.exe 1840 CTF Loader Microsoft Corporation

firefox.exe 672 Firefox Mozilla Corporation

procexp.exe 3100 1.54 Sysinternals Process Explorer Sysinternals - www.sysinternals.com

any help would obviously be appricated.

Link to post
Share on other sites

I was hoping this would help me figure out why my MBAM wouldn't update when I right-clicked the systray icon and selected "Check for Updates", but updated fine when I did it from within the application itself. :(

I'm having a similiar problem. I usually connect through Wifi on my laptop, but connected through dialup at work. I updated Malwarebytes via my dialup connection, and now it will only update through that connection. When I try to update via my WIFI connection it cannot connect to the internet and will not update. I used dialup, and it connected fine.

Any ideas?

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
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.