I was able to go into SEP - Change Settings - Centralized Exceptions,
click Configure Settings, and add c:\documents and settings\<username>
\Local Settings\Application Data\Google\Chrome\Application\chrome.exe
to the list.
However I had to reboot the machine to be able to open up chrome w/out
the error message.
On Sep 2, 3:52 pm, Google Chrome Help Owner wrote:
> Thank you all for reporting this issue! When this error happens does a
> window open at all to report the problem? (If so, please *do* send in
> the error report through that interface).
> Either way, we appreciated the repro steps (shout out to the post from
> Studley), and will look into this to see if Symantec indeed seems to
> be the issue. In the meanwhile, if there's anyone brave enough to
> tinker with their EndPoint settings to see if it resolves the problem
> - that would be extremely helpful as well!
> I'll check back in here when I have an update.
> Thanks!
> Ben
> On Sep 2, 12:38 pm, JohnnySLC wrote:
> > Yikes! Uninstall? Wow, I guess I'm never going to use Chrome.
> > On Sep 2, 1:37 pm, cuparyk wrote:
> > > We have a winner!
> > > I've removed (deinstalled) Symantec EP from my Computer and now it's
> > > working!
> > > But now I'm scared to use it.... ;-)- Hide quoted text -
> Thank you all for reporting this issue! When this error happens does a
> window open at all to report the problem? (If so, please *do* send in
> the error report through that interface).
> Either way, we appreciated the repro steps (shout out to the post from
> Studley), and will look into this to see if Symantec indeed seems to
> be the issue. In the meanwhile, if there's anyone brave enough to
> tinker with their EndPoint settings to see if it resolves the problem
> - that would be extremely helpful as well!
> I'll check back in here when I have an update.
> Thanks!
> Ben
> On Sep 2, 12:38 pm, JohnnySLC wrote:
> > Yikes! Uninstall? Wow, I guess I'm never going to use Chrome.
> > On Sep 2, 1:37 pm, cuparyk wrote:
> > > We have a winner!
> > > I've removed (deinstalled) Symantec EP from my Computer and now it's
> > > working!
> > > But now I'm scared to use it.... ;-)- Hide quoted text -
1. Programs & Features
2. Symantec End Point - right click - Change
3. Remove "Application and Device Control"
4. Reboot Windows
5. Chrome launched successfully.
Would love to hear when this is fixed to resume that setting.
> I'm using Vista, and the following worked for me. I did this as a
> diagnostic, obviously... disabling parts of your virus protection
> system to make a browser work is probably not to be considered a good
> long-term solution.
> In "programs and features" (formerly Add/Remove Programs), find
> Symantec and select "Change" then "Modify."
> Uninstall "Application and Device Control"
> Re-install SEP
> Re-start windows
> Chrome works.
> On Sep 2, 3:57 pm, jkerr wrote:
> > Confirmed, uninstalling fixes it.
> > On Sep 2, 2:38 pm, JohnnySLC wrote:
> > > Yikes! Uninstall? Wow, I guess I'm never going to use Chrome.
> > > On Sep 2, 1:37 pm, cuparyk wrote:
> > > > We have a winner!
> > > > I've removed (deinstalled) Symantec EP from my Computer and now it's
> > > > working!
Ran setup and had the same abnormally long install as described above
by Studley. But it also launched IE7's settings page, even though
Firefox is my default browser.
Have tried multiple install/uninstall events. Also tried to brute-
force the registry by doing a search-and-delete of all entries with
"chrome" in the description. That probably did not kill all of the
files and registry entries, but it made me feel better :^(
After the first failure, I tried doing the download from the Google
Chrome download page.
When I did the second uninstall, I got the silly dialog (something we
said?) and it launched IE7, which then locked up
So it turns out that Chrome REALLY IS a Microsoft killer, but that
probably isn't what you were hoping for...
You're probably on top of this one by now, but just in case, here's a
movie file which shows how the issue manifests itself after
installation. Nothing very sexy, quite similar to the screenshot which
lizdances posted.
> Thank you all for reporting this issue! When this error happens does a
> window open at all to report the problem? (If so, please *do* send in
> the error report through that interface).
> Either way, we appreciated the repro steps (shout out to the post from
> Studley), and will look into this to see if Symantec indeed seems to
> be the issue. In the meanwhile, if there's anyone brave enough to
> tinker with their EndPoint settings to see if it resolves the problem
> - that would be extremely helpful as well!
Can anyone find details of what function 74h in the windows kernel
does?
my (google) searches haven't come up with anything conclusive because
normally the functions are referred to by name not number!
I'm guessing as others have suggested it's a function todo with
process creation or setting lower security privileges. If we can find
out what the function is we might be able to recompile chrome without
those function calls, or replace them with something else that gets
the same job done but doesn't upset SEP..
> Not sure if this has been posted, but adding a centralized exception
> or disabling Endpoint does not seem to fix the issue.
> On Sep 2, 5:51 pm, hajihill wrote:
> > Dear Google Chrome Help Owner (if that is your real name),
> > No windows open to report the error. It looks as if the browser
> > interprets the issue as a page that will not display, due to that
> > separate thread not initializing when Symantec Endpoint Protection
> > blocks it.
> > Confirm on Andy C's solution, though; given above.
> > I am now happily able to reach Google using Google's browser. But, I
> > am still using Apple's phone. One thing at a time.
> > On Sep 2, 1:52 pm, Google Chrome Help Owner wrote:
> > > Thank you all for reporting this issue! When this error happens does a
> > > window open at all to report the problem? (If so, please *do* send in
> > > the error report through that interface).
> > > Either way, we appreciated the repro steps (shout out to the post from
> > > Studley), and will look into this to see if Symantec indeed seems to
> > > be the issue. In the meanwhile, if there's anyone brave enough to
> > > tinker with their EndPoint settings to see if it resolves the problem
> > > - that would be extremely helpful as well!
> > > I'll check back in here when I have an update.
> > > Thanks!
> > > Ben
> > > On Sep 2, 12:38 pm, JohnnySLC wrote:
> > > > Yikes! Uninstall? Wow, I guess I'm never going to use Chrome.
> > > > On Sep 2, 1:37 pm, cuparyk wrote:
> > > > > We have a winner!
> > > > > I've removed (deinstalled) Symantec EP from my Computer and now it's
> > > > > working!
> > > > > But now I'm scared to use it.... ;-)- Hide quoted text -
1.) Uninstalled Application and Device Control using the Add/Remove
Programs menu (as mentioned in other posts).
2.) Installed Chrome
3.) Went back and reinstalled Application and Device Control using the
same menu.
4.) Chrome works!
Hopefully there aren't any lasting security risks to doing this. It
looks like everything is back to normal with the same protections I
had before, though.
Confirmed! You have to uninstall Symantec EP (MR2) to make GC to work.
Since GC still in beta, I re-installed SEP and uninstall GC. I will
try to use it again on the next beta release.
I was getting the same error as everyone else here, the 0xc0000005
one.
I disabled SEP and reinstalled chrome, now (while SEP is disabled) I'm
getting "The application failed to initialize properly (0xc0000135)."
It is now this same message even with SEP enabled. Leaving SEP enabled
and uninstalling and reinstalling Chrome now always results in the ...
135 error for me.
I'm still looking around to see if i can find anything being logged
about what's going wrong.
This is with:
SEP 11.0.2000.1567
Defs:
-Antivirus and Antispyware Protection: Tuesday, September 02, 2008 r33
-Proactive Threat Protection: Wednesday, July 30, 2008 R1
-Network Threat Protection: Thursday, August 28, 2008 r1
Running in a decentralized enviroment.
Running on windows vista home premium SP1
So Far I havent been able to get an exception to work at all for the
chrome folder or chrome executable.
On Sep 2, 4:52 pm, Google Chrome Help Owner wrote:
> Thank you all for reporting this issue! When this error happens does a
> window open at all to report the problem? (If so, please *do* send in
> the error report through that interface).
> Either way, we appreciated the repro steps (shout out to the post from
> Studley), and will look into this to see if Symantec indeed seems to
> be the issue. In the meanwhile, if there's anyone brave enough to
> tinker with their EndPoint settings to see if it resolves the problem
> - that would be extremely helpful as well!
> I'll check back in here when I have an update.
> Thanks!
> Ben
> On Sep 2, 12:38 pm, JohnnySLC wrote:
> > Yikes! Uninstall? Wow, I guess I'm never going to use Chrome.
> > On Sep 2, 1:37 pm, cuparyk wrote:
> > > We have a winner!
> > > I've removed (deinstalled) Symantec EP from my Computer and now it's
> > > working!
> > > But now I'm scared to use it.... ;-)- Hide quoted text -
> I was able to go into SEP - Change Settings - Centralized Exceptions,
> click Configure Settings, and add c:\documents and settings\<username>
> \Local Settings\Application Data\Google\Chrome\Application\chrome.exe
> to the list.
> However I had to reboot the machine to be able to open up chrome w/out
> the error message.
> On Sep 2, 3:52 pm, Google Chrome Help Owner wrote:
> > Thank you all for reporting this issue! When this error happens does a
> > window open at all to report the problem? (If so, please *do* send in
> > the error report through that interface).
> > Either way, we appreciated the repro steps (shout out to the post from
> > Studley), and will look into this to see if Symantec indeed seems to
> > be the issue. In the meanwhile, if there's anyone brave enough to
> > tinker with their EndPoint settings to see if it resolves the problem
> > - that would be extremely helpful as well!
> > I'll check back in here when I have an update.
> > Thanks!
> > Ben
> > On Sep 2, 12:38 pm, JohnnySLC wrote:
> > > Yikes! Uninstall? Wow, I guess I'm never going to use Chrome.
> > > On Sep 2, 1:37 pm, cuparyk wrote:
> > > > We have a winner!
> > > > I've removed (deinstalled) Symantec EP from my Computer and now it's
> > > > working!
> > > > But now I'm scared to use it.... ;-)- Hide quoted text -
Faulting application chrome.exe, version 0.0.0.0, time stamp
0x48b8a514, faulting module chrome.dll, version 0.2.149.27, time stamp
0x48b8a4e1, exception code 0x80000003, fault offset 0x00002ff3,
process id 0xb54, application start time 0x01c90d5293b0a320.
> I was getting the same error as everyone else here, the 0xc0000005
> one.
> I disabled SEP and reinstalled chrome, now (while SEP is disabled) I'm
> getting "The application failed to initialize properly (0xc0000135)."
> It is now this same message even with SEP enabled. Leaving SEP enabled
> and uninstalling and reinstalling Chrome now always results in the ...
> 135 error for me.
> I'm still looking around to see if i can find anything being logged
> about what's going wrong.
> This is with:
> SEP 11.0.2000.1567
> Defs:
> -Antivirus and Antispyware Protection: Tuesday, September 02, 2008 r33
> -Proactive Threat Protection: Wednesday, July 30, 2008 R1
> -Network Threat Protection: Thursday, August 28, 2008 r1
> Running in a decentralized enviroment.
> Running on windows vista home premium SP1
> So Far I havent been able to get an exception to work at all for the
> chrome folder or chrome executable.
> On Sep 2, 4:52 pm, Google Chrome Help Owner wrote:
> > Thank you all for reporting this issue! When this error happens does a
> > window open at all to report the problem? (If so, please *do* send in
> > the error report through that interface).
> > Either way, we appreciated the repro steps (shout out to the post from
> > Studley), and will look into this to see if Symantec indeed seems to
> > be the issue. In the meanwhile, if there's anyone brave enough to
> > tinker with their EndPoint settings to see if it resolves the problem
> > - that would be extremely helpful as well!
> > I'll check back in here when I have an update.
> > Thanks!
> > Ben
> > On Sep 2, 12:38 pm, JohnnySLC wrote:
> > > Yikes! Uninstall? Wow, I guess I'm never going to use Chrome.
> > > On Sep 2, 1:37 pm, cuparyk wrote:
> > > > We have a winner!
> > > > I've removed (deinstalled) Symantec EP from my Computer and now it's
> > > > working!
> > > > But now I'm scared to use it.... ;-)- Hide quoted text -
Details
Product: Windows Operating System
ID: 26
Source: Application Popup
Version: 5.0
Symbolic Name: status_log_hard_error
Message: Unable to Load Device Driver : device driver could not be
loaded.
Explanation
The program could not load a driver because the program user doesn't
have sufficient privileges to access the driver or because the drive
is missing or corrupt.
User Action
To correct this problem:
Reinstall the program to restore the driver to the correct location.
If these solutions do not work, contact Product Support Services.
Explanation
The program could not load a driver because the program user doesn't
have sufficient privileges to access the driver or because the drive
is missing or corrupt.
User Action
To correct this problem:
Ensure that the program user has sufficient privileges to access the
directory in which the driver is installed.
Reinstall the program to restore the driver to the correct location.
If these solutions do not work, contact Product Support Services.
Currently there are no Microsoft Knowledge Base articles available for
this specific error or event message. For information about other
support options you can use to find answers online, see
http://support.microsoft.com/default.aspx
Sorry for all the replies that I'm posting to myself.
I've tried one more time installing Chrome with the exceptions for the
chrome folder /AppData/Local/Google/Chrome/ + subdirs along with
chrome.exe and chrome.dll specifically excluded. I'm still getting
my ...135 error now. However, from this install..... I noticed I get 2
files in my /AppData/Local/Temp folder...
chrome_install.log
File contents:
"[0902/201458:ERROR:setup.cc(282)] Return status of Chrome browser
registration 0"
and
chrome_shutdown_ms.txt
File Contents:
"29"
The contents of chrome_sutdown_ms.txt seem to change each time it
errors and I close it though, I had '22' one shutdown, '24' another
'21' the last time i looked.
Again this is with The following User Defined exceptions set to ignore
in SEP, and the computer has been restarted.
> Thank you all for reporting this issue! When this error happens does a
> window open at all to report the problem? (If so, please *do* send in
> the error report through that interface).
> Either way, we appreciated the repro steps (shout out to the post from
> Studley), and will look into this to see if Symantec indeed seems to
> be the issue. In the meanwhile, if there's anyone brave enough to
> tinker with their EndPoint settings to see if it resolves the problem
> - that would be extremely helpful as well!
> I'll check back in here when I have an update.
> Thanks!
> Ben
> On Sep 2, 12:38 pm, JohnnySLC wrote:
> > Yikes! Uninstall? Wow, I guess I'm never going to use Chrome.
> > On Sep 2, 1:37 pm, cuparyk wrote:
> > > We have a winner!
> > > I've removed (deinstalled) Symantec EP from my Computer and now it's
> > > working!
> > > But now I'm scared to use it.... ;-)- Hide quoted text -
I tried adding the exception in SEP and rebooted, all to no avail.
Still get the same error, still the same problem. Even exempted it
from Security Risk scans, still the same problem. Uninstalling SEP or
any piece of it is a non-starter for me, so I won't be attempting
that.
> I was able to go into SEP - Change Settings - Centralized Exceptions,
> click Configure Settings, and add c:\documents and settings\<username>
> \Local Settings\Application Data\Google\Chrome\Application\chrome.exe
> to the list.
> However I had to reboot the machine to be able to open up chrome w/out
> the error message.
> On Sep 2, 3:52 pm, Google Chrome Help Owner wrote:
> > Thank you all for reporting this issue! When this error happens does a
> > window open at all to report the problem? (If so, please *do* send in
> > the error report through that interface).
> > Either way, we appreciated the repro steps (shout out to the post from
> > Studley), and will look into this to see if Symantec indeed seems to
> > be the issue. In the meanwhile, if there's anyone brave enough to
> > tinker with their EndPoint settings to see if it resolves the problem
> > - that would be extremely helpful as well!
> > I'll check back in here when I have an update.
> > Thanks!
> > Ben
> > On Sep 2, 12:38 pm, JohnnySLC wrote:
> > > Yikes! Uninstall? Wow, I guess I'm never going to use Chrome.
> > > On Sep 2, 1:37 pm, cuparyk wrote:
> > > > We have a winner!
> > > > I've removed (deinstalled) Symantec EP from my Computer and now it's
> > > > working!
> > > > But now I'm scared to use it.... ;-)- Hide quoted text -
I was deperate to download Chrome and still after 5 hours of its
launch I am getting the same error. I have tried all possibilities
( what ever permissions I had, I tried).
I tried the EXCEPTIONS....dint work. ( with lot of effort to convince
my admin)
I cant uninstall... no permissions...:-(
I guess Ben is working on it... request to keep posted on SEP and fix
this.
I have been experiencing the same issue with Chrome giving the error
message at startup and failing to load any pages. Installed Chrome
with SEP installed and running on Windows XP Home. I'll wait for
updates from Google and/or Symantec, but it's good to know it's not
just something unique to my system.
> Not wanting to clog the topic, but I'm also having the problem after
> multiple install attempts.
> 1. Downloaded the ChromeSetup.exe
> 2. Ran the ChromeSetup.exe, which initialized the installation
> 3. Installer detected that I had Firefox 3 installed, and offered to
> import bookmarks, browser history etc.
> 4. A noticeable delay after the import had completed - nearly 30
> second
> 5. Chrome launched itself, and loaded two pages (both with the "sad
> folder" icon)
> 6. Manually restarted Chrome; from this point onwards, I received the
> "failed to initialize (0xc0000005)" error which you mentioned.
> I've tried various different install combinations; for instance, at
> the point where it prompts to import bookmarks, I've gone into
> "customize" and unchecked all of these options. However, I always get
> the same result... sad folders and on-screen exceptions :(
