Jeff L. said: Hi Jeremy, I'm going to do my best to get this situated for you. There are a couple of ideas I have in mind to try and isolate this problem. 1. Let's try the cleanest Chrome we can get. It is possible to get a very clean testing environment in Chrome using a command-line switch. This option in Windows is --user-data-dir=/dev/null (To use this, right click on a shortcut to Chrome on your Desktop, select Properties, then add the option (with a space before it) in the "Target" field after the last quotation mark. It'll look something like this: "C:\Users\username\AppData\Local\Google\Chrome\Application\chrome.exe" --user-data-dir=/dev/null Run Chrome with that option, and see if this resolves the issue. 2. If that fails, let's try running it in a Sandbox. Install Sandboxie: <a href="https://www.sandboxie.com/DownloadSandboxie" rel="nofollow">https://www.sandboxie.com/DownloadSandboxie</a> There is fairly good documentation in the installer. I would recommend installing the Shell Extensions so that you can easily run the shortcut you created above with a right click. Regardless of how, run Chrome (with the null user profile) within Sandboxie. Things might act a bit weird, but if it works here this will help isolate the problem. 3. Whether Sandboxie works or not, note that information and then try running in Safe Mode. Assuming you're using Windows 10, follow the steps here to reboot your computer into Safe Mode with Networking : <a href="https://support.microsoft.com/en-us/help/12376/win" rel="nofollow">https://support.microsoft.com/en-us/help/12376/win</a>... Run Chrome and see if this resolves the issue. Please post your results and I'll continue to help as possible. I switched over from Chrome Beta to regular Chrome to test this, just as an FYI. 1: Solution one did not help fix the problem. 2: Sandboxie refused to work for me. It kept throwing up the following error which I was unable to find solutions for online (save for downloading a beta of Sandboxie? But I'm not sure there is one currently) The app tried to direct me to a link on the Sandboxie site that was a 404, so whatever fixed it might have been removed. SBIE2101 Object name not found: , error OpenProcess (C0000022) access=001FFFFF initialized=1
SBIE2101 Object name not found: , error OpenProcess (C0000022) access=001FFFFF initialized=1
I'll post an update with 3 in a second. I'm going to be testing it now. Update! 3: Did not work either. Included in this I tried using the "--user-data-dir=/dev/null" resolution presented earlier while in Safe Mode to no avail.