HOW TO FIX RESULT_CODE_KILLED_BAD_MESSAGE WHEN OPENING GOOGLE DRIVE DOCS | AW SNAP GOOGLE DRIVE

preview_player
Показать описание
#AWSNAP #GOOGLEDRIVE #CHROME

RESULT_CODE_KILLED_BAD_MESSAGE

Have you ever encountered this annoying message? What have you done to make this go away?

This happens when I access a document from google drive using Chrome or Edge. Here’s what I already tried.

From Google chrome help

Cleared cache
Removed all extensions
Updated Chrome
Reinstalled chrome
Restore defaults
Checked unwanted software which found none.

None of this worked

I then tried adding “no sandbox” parameters in Chrome target link and updated group policies with gpupdate.

Add --no -sandbox in chrome shortcut
Execute gpupdate /force in cmd
Disabled all non Microsoft services in msconfig
Restart and enabled microsoft services again
Restarted machine

But still no luck fixing this issue.

Only one option worked for me. This is to install Firefox and access google drive documents from there. Saved me a lot of time trying to figure out how to fix this error.

I still use Chrome as my main browser but thankfully we still have Firefox to save the day. It works every time.
Рекомендации по теме
Комментарии
Автор

Thanks for at least listing all the attempts that didn't work, but then giving a solution to use a different browser, is a bit like a mechanic saying, just buy a new car because I can't figure out this rattling noise.

m-w-copeland