guard32.dll kills Chrome 45

A. Since updating to Chrome 45, guard32.dll causes it crash on startup
Can you reproduce the problem & if so how reliably?:
Yes. Every time I start Chrome 45 it immediately stops working.
If you can, exact steps to reproduce. If not, exactly what you did & what happened:
1: Start Chrome 45
2: It stops working.
One or two sentences explaining what actually happened:
After updating from Chrome 44 to Chrome 45, Chrome crashes on startup.
One or two sentences explaining what you expected to happen:
That Chrome 45 starts without crashing.
If a software compatibility problem have you tried the advice to make programs work with CIS?:
Couldn’t find any help for this.
Any software except CIS/OS involved? If so - name, & exact version:
Chrome 45.0.2454.85
Any other information, eg your guess at the cause, how you tried to fix it etc:
According to the windows event log the crash is caused by guard32.dll which belongs to CIS
Any Chromium browser that is based on a version before 45 works fine.
I’ve completely uninstalled (and i mean completely) and reinstalled Chrome 45. Didn’t help.

B. YOUR SETUP
Exact CIS version & configuration:
Comodo Firewall 8.2.0.4674
Modules enabled & level. D+/HIPS, Autosandbox/BBlocker, Firewall, & AV:
Firewall using Custom Ruleset, nothing else.
Have you made any other changes to the default config? (egs here.):
Just using the Custom Ruleset
Have you updated (without uninstall) from CIS 5, 6 or 7?:
No.
Have you imported a config from a previous version of CIS:
No.
OS version, SP, 32/64 bit, UAC setting, account type, V.Machine used:
Win 7 64bit, UAC disabled, admin, no VM.
Other security/s’box software a) currently installed b) installed since OS, including initial trial security software included with system:
a=Avira AntiVir b=none

jurrasstoil please attach the diagnostics file (instructions on how to do this provided here) and the KillSwitch Process List (instructions on how to do that provided here) and put the resulting file in a zip file. Both should then be attached to your post.

After you do this i can forward this to the devs. Thanks

Same here with guard32.dll

Nombre del evento de problema: BEX
Nombre de la aplicación: chrome.exe
Versión de la aplicación: 45.0.2454.85
Marca de tiempo de la aplicación: 55df881b
Nombre del módulo con errores: guard32.dll
Versión del módulo con errores: 8.2.0.4674
Marca de tiempo del módulo con errores: 55c148a3
Desplazamiento de excepción: 000269c9
Código de excepción: c0000409
Datos de excepción: 00000000
Versión del sistema operativo: 6.1.7601.2.1.0.256.1
Id. de configuración regional: 3082
Información adicional 1: 3f2e
Información adicional 2: 3f2e04a7da90d2064f3f1d4896cbcc2e
Información adicional 3: 61a1
Información adicional 4: 61a10864808d39750fbd819b57eb4ab9

Chromium team are tracking this issue as https://crbug.com/527496 if someone from Comodo could get in touch with us, that would be helpful.

Will

I split, moved and merged the remarks and questions that are not relevant for a bug report to Comodo Firewall crashes Chrome 45 [merged].

For all users suffering from this problem use the following workaround. Add chrome.exe to Detect shellcode injections for the time being. For questions and remarks that are not pertinent for a bug report please post them in the above topic. Off topic comments will be split and merged with the above topic.

Hello everyone.

I just learned there is a required format for reporting, so here I go:

A. THE BUG/ISSUE (Google Chrome crashes)

Can U reproduce the problem & if so how reliably?:
Yes, I can reproduce it every time I want. 100%
If U can, exact steps to reproduce. If not, exactly what U did & what happened:
1:I run chrome.exe.
2:It offers me to restore some tab.
3:No matter what I do, it always crash.
If not obvious, what U expected to happen:
It is obvious.
If a software compatibility problem have U tried the conflict FAQ?:
This is a new issue.
Any software except CIS/OS involved? If so - name, & exact version:
Chrome, 45.0.2454.85
Any other information, eg your guess at the cause, how U tried to fix it etc:
This is what is showed in error window:

EventType : BEX P1 : chrome.exe P2 : 45.0.2454.85 P3 : 55df881b
P4 : guard32.dll P5 : 8.2.0.4674 P6 : 55c148a3 P7 : 000269c9
P8 : c0000409 P9 : 00000000

I became worried after my desinstall-reboot-reinstall failure program procedure. It keeps offering to restore some tab and than crash.
So I went to Chrome forum and they told me:
Suggested workaround: In Comodo CIS, go to Defense+ → HIPS → HIPS Settings → Detect shellcode injection [Exclusions], and then add chrome.exe to the exclusion list.
So I did intented to do what they said, but my Comodo HIPS is not even enabled. Anyway I added chrome.exe to exclusions.
Then I tried to run chrome again and it crashed just like it was crashing before.
I rebooted and tried again. Same result.
Then I desinstalled chrome, reboot machine, closed Comodo, reinstalled chrome again and ran it with Comodo closed. It keeps crashing exactly the same way.

B. YOUR SETUP

Exact CIS version & configuration:
8.2.0.4674 - Comodo Internet Security Active
Modules enabled & level. D+/HIPS, Autosandbox/BBlocker, Firewall, & AV:
HIPS: DISABLED, Autosandbox: DISABLED, File source tracking: ENABLED, BBlocker: couldn' find it, where it is? Firewall: ENABLED in safe mode.
Have U made any other changes to the default config? (egs here.):
Added chrome.exe to HIPS exclusions, but it didn't help.
Have U updated (without uninstall) from CIS 5 or CIS6?:
No.
    if so, have U tried a a clean reinstall - if not please do?:
    I said no.
Have U imported a config from a previous version of CIS:
No, this is my first Comodo experience!
    if so, have U tried a standard config - if not please do:
    
OS version, SP, 32/64 bit, UAC setting, account type, V.Machine used:
Win XP-32bits, SP3
Other security/s'box software a) currently installed b) installed since OS, including initial trial security software included with system:
The other securiy thing installed and working is the windows firewall, and that is all.

C. ATTACH REQUIRED FILES
I will attach diagnosis zip file.

Same here.

System Information: 32-bit Windows 7 Home Premium with SP1 and a bunch of other fixes and updates.
Chrome´s Problem Signature Report (original report is written in Brazilian Portuguese a.k.a. PT-BR or Localization code 1046). I kind of translated it back into B.E. (Basic English):
Problem Signature
Problem Event Name: BEX
Application Name: chrome.exe
Application Version: 45.0.2454.85
Application Date/Time Stamp: 55df881b
Failure Module Name: guard32.dll
Failure Module Version: 8.2.0.4674
Failure Module Date/Time Stamp: 55c148a3
Exception Shift: 000269c9
Exception Code: c0000409
Exception Data: 00000000
Operating System Version: 6.1.7601.2.1.0.768.3 (Windows 7 Home Premium)
Localization Identification 1046 (PT - BR)
Additional Information 1: 07f5
Additional Information 2: 07f51b143980772b1f9901826abf6c32
Aditional Information 3: afcb
Aditional Information 4: afcbfb75d4678547c30c5dde35547b86

I have also attached the report (translated).

I have applied the workaround suggested by Google Chrome and posted here by VirusCollector (thank you very much for that) and now Chrome is up and running on my PC.
Just as an additional piece of information the only other way I was able to have Google Chrome to run was uninstalling C.I.S… Even if Chrome is installed first and confirmed to be running properly, after C.I.S. (A.V. and Firewall) is reinstalled the crash problem returns in its full glory.

Jose Pinho

[attachment deleted by admin]

CIS Diagnostics here.

[attachment deleted by admin]

Hello Guys,

Please kindly note that we will be doing a hotfix release on Monday to fix this bug.

For your kind attention please.

Kind Regards
Buket

For all people looking for a solution:

The problem has Comodo’s undivided attention. In the meanwhile there is nothing you can do other than applying a temporary fix for your customers. :-\

If you have questions or remarks I urgently suggest to post them in Comodo Firewall crashes Chrome 45 [merged]. Posts not pertinent to a bug report will be moved to that topic.

Will the fix be issued for Comodo Endpoint Security at the same time or will that follow at a later date please ?

Since this bug has comodos attention and is being addressed im going to move this to resolved. Comodo has reported that they are going to release a fix on monday 9-7. Thanks everyone for your reports.

No further reports are necessary