Jump to content

Search the Community

Showing results for tags 'code integrity check'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Site Related
    • News & Updates
    • Site / Forum Feedback
    • Member Introduction
  • News
    • General News
    • FileSharing News
    • Mobile News
    • Software News
    • Security & Privacy News
    • Technology News
  • Downloads
    • nsane.down
  • General Discussions & Support
    • Filesharing Chat
    • Security & Privacy Center
    • Software Chat
    • Mobile Mania
    • Technology Talk
    • Entertainment Exchange
    • Guides & Tutorials
  • Off-Topic Chat
    • The Chat Bar
    • Jokes & Funny Stuff
    • Polling Station


  • Drivers
  • Filesharing
    • BitTorrent
    • eDonkey & Direct Connect (DC)
    • NewsReaders (Usenet)
    • Other P2P Clients & Tools
  • Internet
    • Download Managers & FTP Clients
    • Messengers
    • Web Browsers
    • Other Internet Tools
  • Multimedia
    • Codecs & Converters
    • Image Viewers & Editors
    • Media Players
    • Other Multimedia Software
  • Security
    • Anti-Malware
    • Firewalls
    • Other Security Tools
  • System
    • Benchmarking & System Info
    • Customization
    • Defrag Tools
    • Disc & Registry Cleaners
    • Management Suites
    • Other System Tools
  • Other Apps
    • Burning & Imaging
    • Document Viewers & Editors
    • File Managers & Archivers
    • Miscellaneous Applications
  • Linux Distributions


  • General News
  • File Sharing News
  • Mobile News
  • Software News
  • Security & Privacy News
  • Technology News

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 1 result

  1. Google decided to temporarily disable the Code Integrity feature activated in Chrome as users report more "Aw Snap!" crashes caused by incompatible software on the system. The issue was initially identified on systems with outdated versions of Symantec Endpoint Protection (SEP) and was pinned to incompatibility with the Renderer Code Integrity feature from Microsoft that had been just enabled in Chrome 78. Three more apps cause Chrome to snap Both Symantec and Google provided solutions to this problem (use the latest SEP release or disable the code integrity protection in the browser) but "Aw Snap!" crash reports kept coming. However, new apps have been found to be incompatible with Microsoft's security mechanism in Chrome. The mechanism prevents binaries that are not signed by Microsoft from being loaded by the browser. "We have confirmed that in addition to the known incompatibility with specific versions of Symantec Endpoint Protection, some additional software applications may be causing “Aw, Snap!” messages in the latest Chrome M78 release." In an update on Tuesday, Google informs that "Aw Snap!" crashes also happen on systems running PC Matic and Palo Alto Networks' Traps security products, as well as the Print Audit Infinite tool for tracking document printing across the local network. Feature disabled temporarily The new crash reports determined Google to turn off the code verification feature in its browser until compatibility with other software products is improved, says Craig Tumblison, Chrome support manager. This decision is to give some time to developers with products causing this sort of disruption to find a way to fulfill their functions without injecting code into Chrome. Google intends to re-enable the feature in mid-November. Users of software products causing this problem are recommended to contact the app developer to find out when a fix will be available. Users are advised to keep their software up-to-date to avoid this problem. Source
  • Create New...