After Windows 10 update, turning on bank mode causes Avast Browser to freeze

Immediately after this most recent Windows 10 update installed, I’m no longer able to use bank mode. When I click on the bank mode icon to turn it on, the window changes and it looks like bank mode is launching, but the screen stays white, and the spinning circle appears and then spins indefinitely. I can browse just fine outside of bank mode, but I’d really like to use bank mode again. Any ideas as to what happened to my system (Avast in bank mode was running just fine before the update) and how to go about fixing it?

Thank you! :slight_smile:

Which version of ASB…?

I am experiencing a similar issue. Subsequent to installing the Secure Server update, I cannot open Bank Mode. When I click the highlighted Bank Mode, nothing happens.

Here is the product info:
Avast Secure Browser is up to date
Version 65.2.491.182 (Official Build) (32-bit)

Any assistance is greatly appreciated!

Hi, just tested it, bank mode works for me. Are you also running W10…?

I am running Windows 10 Home / Version 1709

OK, I forwarded it.

I’m running Program Version 18.4.2338 (build 18.4.3895.325) on Windows 10 Home 1803 OS Build 17134.81 5/27/18.

Thank you!

Hello,

am sorry to hear about your problems. Please can you write here some details?

  • does Avast AV report “You are protected”?
  • when you launch Secure Browser normally, is there AvastNM.exe process running? (If you are using Avast Passwords in the browser, you should see 2 AvastNM.exe processes)
  • can you launch Bank Mode via Avast tray icon menu?

Thank you

I have been forwarded from Bank Mode will not start. Yes Avast AV reports you are protected. Don’t know how to check for AvastNM.exe processes. Don’t know what you mean by Avast tray icon menu. Sorry.

Right click the Avast icon in your system tray and you’ll see this

https://screencast-o-matic.com/screenshots/u/Lh/1528136819354-85058.png

Hi Dave,

Please see the attached pic below for how to see AvastNM.exe processes and attach a screenshot of what you find. The reason for asking for this is because if Avast Secure Browser is running at all, it will show in Task Manager.

Same problem here, no bank mode access in the ASB since the Win 10 update a week or so ago. Additionally, Avast fails every time while attempting to check for updates via the About Avast SafeZone 4.58 page.

-Avast reports as protected.
-Avast can be started from the system tray.
-multiple Avast processes running as shown within Task Manager, including AvastNM.exe

Win10 Home Edition v10.0.17134 Build 17134
Avast Free Antivirus v18.4.2338 Build 18.4.3895.325
Virus Def v18064-8

-gcs01

The question asked was “Can you start Bank Mode from the system tray”
The update function in Safe Zone Browser isn’t working yet.

Okay secure browser running but not AvastNM.exe

Yes itopens a window from this. Seems to be a new set up, no bookmarks etc.

That would be a negative. Actually, Bank Mode can be opened via the system tray, opened as confirmed in the lower right, but it is a blank screen…same as trying to open it directly from within ASB.

-gcs01

What do you mean by “blank screen” ???
This is what you should see:

https://screencast-o-matic.com/screenshots/u/Lh/1528249606917-37519.png

I see just what you show there minus the browser. A white or gray screen. Bank mode info, lower right. Switch back button, lower left. White/gray screen otherwise.

-gcs01

Maybe it’s time for a clean install of the Secure Browser ???
Download the installer from here, https://www.avast.com/en-us/secure-browser
Download the Secure Browser Removal tool from here, https://download.avastbrowser.com/avast_secure_browser_uninstall.exe
Save your Bookmarks via the Book Marks Manager if you have custom bookmarks so you can import them when you re-install.
Run the removal tool, reboot, run the installer import your favorites if you saved them.
Let us know if that’s solved the problem.

What does that do to the Password Manager and saved passwords?

So are there only a handful of us who have run into this problem immediately following the late-May Win10 update?

-gcs01