Most of the time, users report receiving the Aw-Snap! error while they trigger the printing sequence in Chrome.
If you’re currently struggling with this issue, the following fixes might help. We have managed to identify a few methods that have been successful for users in a similar situation to resolve the issue. Please follow the methods below in order until you encounter a fix that works for your situation.
Method 1: Using the Ctrl + Shift + P shortcut (workaround)
If you’re looking for a quick fix that will spare you from going through time-consuming steps, using the Ctrl + Shift + P shortcut might just enable you to get around the issue. However, keep in mind that this should only be regarded as a workaround since it doesn’t fix the underlying issues that caused Google Print to malfunction. If this workaround isn’t effective or if you’re looking for some steps that will resolve the underlying issues, continue with the method below.
Method 2: Deleting the extra printers on Google Print
Some users have been able to resolve the issue without having to uninstall the browser by making sure the printers listed under Google Cloud Print are properly managed. As it turns out, whenever Google Cloud Print has more than one listed active printer it might create issues that will prevent users from printing directly from Chrome. To remedy this issue, you’ll have to delete the extra printers that you don’t use. Here’s a quick guide on how to do this:
Method 3: Deleting local browsing history then uninstall Chrome
Most users have been able to resolve the issue after uninstalling Chrome along with the local browsing history. Upon reinstalling the newest Chrome version available, most users have reported regaining the ability to print directly from Chrome. Here’s a quick guide to deleting the local browsing history, uninstalling Chrome and reinstalling it again: If this method didn’t work, start following the other methods below.
Method 4: Claiming Full Control over the Temp folder
Some users have been finally able to resolve the issue after tweaking the permissions of the temp folder (within the AppData update). Apparently, giving yourself full control over the temp folder will restore the ability to print directly from Google Chrome. Although this is purely speculation, it’s widely believed that a WU update has modified the permissions for already-installed browsers. Note: This method seems to be effective for users that are able to print from Internet Explorer but are prevented from printing on Google Chrome, Firefox, and any other 3rd party browser. Here’s a quick guide to claiming Full Control over the temp folder in order to restore the printing ability in Google Chrome: If the method hasn’t managed to resolve your issue, move down to the final method.
Method 5: Repairing the Print Spooler driver
If all the methods above have been a bust, there’s a high chance that the print spooler driver or another Windows component tasked with handling a printing chore has become corrupted and unusable. This is most certainly the culprit if you notice that you’re PC is unable to print from anywhere else (any 3rd party app) than on Microsoft’s channels. As some users have pointed out, it’s very likely that certain files located in SYSWOW64 need replacing. If that’s the case, you’re the best chance of resolving the issue without having to reinstall your OS is to trigger a system repair. To trigger a system repair, we’re going to use System File Checker – a Windows utility that scans for system file corruption and replaces the corrupted files. Here’s a quick guide on how to trigger a System File Checker scan to fix the printing problem on Google Chrome:
Method 6: Resetting Chrome to Default Settings
Some users reportedly got around this issue by resetting Chrome back to its default settings. We will be doing exactly that in this method. In order to do that: Note: Also, download the following apps and install them. XPX Essential NET 3.0 NET 3.5
Check the Google Chrome Version and the Last Time Chrome UpdatedFix: Can’t Uninstall Google ChromeGoogle Confirms The Aw, Snap! Bug in Chrome 78, Here’s How You Can Fix ItThis site can’t be reached error on Google Chrome (Fixes)
