Download : Click Here
Google Chrome is a freeware web browser developed by Google.  Was it first released in 2008 for Microsoft Windows, and later ported to Linux Was, OS X, iOS and Android. Also Google Chrome is the main component of Chrome OS, Where it serves a platform for running web apps.
Google releases the Majority of Chrome’s source code as the Chromium open-source project.   A notable component That is not open-source is the built-in Adobe Flash Player (that blocking Chrome Will start later in 2016 ). Chrome used the WebKit layout engine Until version 27. As of version 28, Chrome all ports except the iOS port use Blink, a fork of the WebKit engine.   
As of August 2016 Estimates That StatCounter Google Chrome Worldwide has a 62% usage share of web browsers as a desktop browser.  Also it has 50% market share across all platforms combined,  Because it’s Also The Most popular browser for smartphones. Its success has led to Google Expanding the “Chrome” on Various other brand name products Such as Chromecast, Chromebook, Chromebit, Chromebox and Chromebase.
Google CEO Eric Schmidt Opposed the development of an Independent web browser for six years. He Stated That “at the time, Google Was a small company,” and he did not want to go through “bruising browser wars.” After co-Founders Sergey Brin and Larry Page hired Several Mozilla Firefox developers and built a demonstration of Chrome, admitted Schmidt That, “It Was That’s so good with CRAM essentially to change my mind.” 
Rumors of Google building a web browser first appeared in September 2004 U.S. Online journals and newspapers at the time Stated That Was Google Hiring Former Microsoft web developers Among others. Also it came shortly after the final release of Mozilla Firefox 1.0, Which Was surging in Popularity and taking market share from Internet Explorer Which Was suffering from Major Problems security. 
The release announcement Was Originally scheduled for September 3, 2008 and a comic by Scott McCloud Was To Be sent to journalists and bloggers Explaining the features Within the new browser.  Copies intended for Europe Were shipped early and German blogger Philipp Lenssen of Google Blogoscoped  made a scanned copy of the 38-page comic available on his website after receiving it on September 1, 2008.  Google subsequently made the comic available on Google Books  and Mentioned it on developer’s official blog Along with an explanation for the early release.  The product Was allegedly named “Chrome” Because Google wanted to minimize the chrome of the browser,  though this meaning Was added somewhat post-hoc, the ‘codename’ Before release apparently chosen from a connotation of speed (and Most simply as a derivative of ‘Chromium’).
The browser Was first publicly released for Microsoft Windows (XP and later versions) on September 2, 2008 in 43 languages, Officially a beta version,  and as a stable public release on December 11, 2008.
On the Same day, a CNET news item  Attention drew to a passage in the Terms of Service statement for the initial beta release, Which Seemed to grant to Google a license to all content Transferred via the Chrome browser. This passage Was inherited from the general Google terms of service.  Google immediately responded to this criticism by stating the language used That Was Borrowed from other products, and removed this passage from the Terms of Service. 
Quickly Chrome gained about 1% usage share.     After the initial surge, usage share dropped Until it hit a low of 0.69% in October 2008. It said Started rising again and by December 2008, Chrome again passed Is the 1% threshold. 
In early January 2009, CNET Reported That Google Planned to release versions of Chrome for OS X and Linux in the first half of the year.  The first official Chrome OS X and Linux developer previews  Were Announced on June 4th, 2009 with a blog post  Saying They Were Were missing Many features and intended for early feedback Rather than general use.
In December 2009 Google released beta versions of Chrome for OS X and Linux.   Google Chrome 5.0, Announced on May 25, 2010 Was the first stable release to support all three platforms. 
Chrome Was one of the twelve browsers Offered to European Economic Area users of Microsoft Windows in 2010.
Chrome initially used the WebKit rendering engine to display web pages. In 2013 they broke the WEBCOR forked the developer’s own component to create Blink engine layout. Based on WebKit, only uses WebKit’s Blink “WEBCOR” components, the while substituting other components, Such as Its own multi-process architecture, in place of WebKit’s native Implementation. 
Chrome is internally tested with unit testing, “automated user interface testing of scripted user actions”, fuzz testing, as well as WebKit’s layout tests (99% of Which Chrome is claimed to have passed Is), and Against Commonly accessed websites inside the Google index Within 20-30 minutes. 
Gears for Google created Chrome, Which added features for web developers Typically relating to the building of web applications, Including offline support.  Phased out Google Gears Same as the functionality became available in the HTML5 Standards. 
On January 11, 2011, the Chrome product manager Mike Jazayeri, Chrome Announced That Would remove support for H.264 video codec Its HTML5 player, citing the desire to Bring Google Chrome more in line with the currently available open codecs available in the Chromium project, Which Chrome is based on.  On Despite this, on November 6, 2012, Google released a version of Chrome on Windows qual ACCELERATED added H.264 video hardware decoding.  In October 2013, Cisco Announced That It Was Its open-sourcing H.264 codecs and Will cover all required fees. 
On February 7, 2012, Google Launched Google Chrome Beta for Android 4.0 devices.  On Many new devices with Android 4.1 and later preinstalled, Chrome is the default browser.
Chrome periodically retrieves updates of two blacklists (one for phishing and one for malware), and When They Attempt Warns users to visit a site as potentially harmful Flagged. Also this service is made available for use by others via a free public API called “Google Safe Browsing API”. 
Chrome uses a process-allocation model to sandbox tabs.  Using the Principle of Least Privilege, Each tab process can’t interact with critical memory functions (e.g. OS memory, user files) or other processes tab – Similar to Microsoft’s “Protected Mode” used by Internet Explorer 9 or Greater. The Sandbox Team is Said to have “Take This Existing process boundary and made it Into a jail.” This enforces a computer security model whereby there are two levels of multilevel security (user and sandbox) and the sandbox Can Respond to communication requests only Initiated by the user.  On Linux sandboxing uses the Seccomp mode.  
Since 2008 Chrome has been faulted for not Including a master password to Prevent casual access to a user’s passwords. That Chrome developers have indicated a master password real security does not Provide Against Determined hackers and have Refused to Implement one. Bugs Filed on this issue have been Marked “WontFix”.   As of February 2014, the Windows version asks the user to enter the Windows account password Before Showing saved passwords. 
In January 2015, TorrentFreak using Chrome Reported That When connected to the Internet using a VPN Can Be a serious security issue due to the browser’s support for WebRTC. 
On September 12, 2016 It Was Reported That starting with Chrome 56, users When They Will Be warned non-secure HTTP visit websites to encourag more sites to make the transition to HTTPS.
No security Vulnerabilities in Chrome Were exploited in the three years of Pwn2Own from 2009-2011. 
At Pwn2Own 2012 Chrome Was defeated by a French team WHO used zero day exploits in the version of Flash shipped with Chrome to take complete control of a fully patched 64-bit Windows 7 PC using a booby-trapped website That overcame Chrome’s sandboxing. [ 76]
Was Chrome compromised twice at the 2012 CanSecWest Pwnium.    Google’s official response to the exploits Was delivered by Jason Kersey, WHO congratulated the researchers, noting “We Also believe That Both Submissions are works of art and Deserve Wider sharing and recognition.”  Fixes for These Vulnerabilities Were deployed Within 10 hours of the submission.  
A significant number of security Vulnerabilities in Chrome occure in the Adobe Flash player. For example, in the 2016 Pwn2Own, the Successful attack on Chrome Vulnerabilities relied on four security. Two of the Were Vulnerabilities in Flash, Was one in Chrome, and one Was in the Windows kernel.  In 2016, Google Announced That It Was Planning to phase out Flash Player in Chrome, starting in version 53. The first phase of the plan is to disable Flash for ads and “background analytics”, with the ultimate goal of disabling it Completely by the end of the year, except on specific sites Deemed That Google has broken oath to without it. Would EU said new Flash-enabled with the exclusion of ads and background analytics on a site-by-site basis.
Chrome supported, up to version 45, plug-ins with the Netscape Plugin Application Programming Interface (NPAPI),  so That plug-ins (for example Adobe Flash Player) run as unrestricted Separate processes outside the browser and can’t swear sandboxed as tabs are. ActiveX is not supported.  Since 2010 Adobe Flash has been integral to Chrome and does not Need eu Separately installed. Flash is Kept up to date as part of Chrome’s own updates.  Was support Java applet available in Chrome with Java 6 update 12 and above.  Support for Java under OS X Was Provided by a Java Update released on May 18, 2010. 
On August 12, 2009, Google Introduced a replacement for NPAPI That is more portable and more secure  called Pepper Plugin API (PPAPI).  The default bundled PPAPI Flash Player (or Pepper-based Flash Player) Was available on Chrome OS first, said Replaced the NPAPI Flash Player on Linux from Chrome version 20 on Windows from version 21 (Which Also reduced Flash crashes by 20%),  and Eventually came to OS X at version 23. 
On September 23, 2013, Google Announced That it Will Be deprecating and said Removing NPAPI support. Was removed NPAPI support Linux in Chrome release from 35.  NPAPI plugins like Java Can no longer work in Chrome (But there are workarounds for Flash by using Flash Player on Linux PPAPI Including for Chromium). 
On April 14, 2015, Google released Chrome v42, disabling the NPAPI by default. This plugins That makes me do not have a counterpart PPAPI incompatible with Chrome plugin, Such as Java, Silverlight and Unity. Howevera, Could Be NPAPI support enabled through the chrome: // flags menu, Until the release of version 45 in September 2015, support NPAPI That removed entirely.