Almost all applications were unable to start correctly

[REDACTED]

There is something weird going on that seems to be linked to Avast. It seems to have begun happening recently which started after something caused my system to be restarted and I was getting constant "the application was unable to start correctly (0xc0000005)" when trying to start most problems on this computer, which also was appearing a lot during the login to the desktop. On top of that, if I log into Owner instead of the desktop that I normally use, I get a white screen freeze when trying to switch back. After a few reboots, I was able to get back into my normal desktop. Since one of the fixes suggests disabling my anti-virus, I ended up disabling the shields of Avast to see if that works and it seems to have worked for now. Right now, I don't know what is causing this and hope someone can help me with a fix.

[Asyn]

- Which Avast..? (Free/Pro/IS/Premier)
- Which version..?
- OS..? (32/64 Bit..? - which SP/Build..?)
- Other security related software installed..?

[REDACTED]

- Which Avast..? (Free/Pro/IS/Premier)
- Which version..?
- OS..? (32/64 Bit..? - which SP/Build..?)
- Other security related software installed..?

Avast Free Antivirus
Version 17.3.2291 (build 17.3.3443.0)
OS Windows 10 Pro 64 Bit - Build 14393.953
Only other stuff that I have is a disabled Windows Defender and Malwarebytes' Anti-Malware version 3.0.6 installed.

[Asyn]

1. Download Avast Free Antivirus: https://files.avast.com/iavs9x/avast_free_antivirus_setup_offline.exe
2. Follow instructions: https://www.avast.com/uninstall-utility (Run this tool for all prior installed Avast versions..!!)
3. Reinstall Avast with the downloaded installer from point 1.
4. Reboot.

[REDACTED]

I tried all that, but it didn't fix the problem as I was still getting the same errors until I had to disable the Avast Shields to run things again.

[Asyn]

OK, wait for one of the guys with W10.

[CraigB]

Is Malwarebytes running realtime?

I'd suggest removing both Avast and Malwarebytes then upgrade to the next windows 10 version here https://www.microsoft.com/en-au/software-download/windows10

Once installed then you can safely install Avast again, Malwarebytes 3 has been having it's issues since they released it, personally I don't think it ready for prime time yet.

[REDACTED]

Is Malwarebytes running realtime?

No, I just checked and it is currently running Malwarebytes Free with a message saying "Upgrade to Premium to get Real-Time Protection from ransomware and other threats."

I'd suggest removing both Avast and Malwarebytes then upgrade to the next windows 10 version here https://www.microsoft.com/en-au/software-download/windows10

Once installed then you can safely install Avast again, Malwarebytes 3 has been having it's issues since they released it, personally I don't think it ready for prime time yet.

There is a new version of Windows 10 that Microsoft released recently?

[REDACTED]

Okay, I was beginning to uninstalled Avast and the Malwarebytes to do the Windows Update, and got this error message after the uninstall of Avast.

---------------------------
safezone installer 3.55.2393.596.0
---------------------------
Fatal error upon loading installer executable:

214:0, 254:0, 159:32, 259:0,

When reporting this error, click on this text and press Ctrl+C to copy it.
---------------------------
OK   
---------------------------

[REDACTED]

I'd suggest removing both Avast and Malwarebytes then upgrade to the next windows 10 version here https://www.microsoft.com/en-au/software-download/windows10

Once installed then you can safely install Avast again, Malwarebytes 3 has been having it's issues since they released it, personally I don't think it ready for prime time yet.

I just did this and upgraded to the next windows 10 version, but I'm still getting the same error messages when I try to start any programs and had to disable the Avast Shields again to get around it.

Windows 10 Pro version is now Version 1703 (OS Build 15063.13)

[REDACTED]

After doing some shield testing to isolate what shield it causing the problem, I found that it is the Behavior Shield that is causing this.