SOLUTION? “Class not registered” when trying to open Chrome in Windows 8.1/10

Recently I have been seeing an increased incidence of this particular issue on newer Windows 8/8.1/10 machines.  It occurs when the user attempts to launch Chrome via any shortcut on the Desktop, taskbar, or elsewhere, or when opening any file or protocol (URL, etc.) associated with Chrome.  The only permanent “solution” is to create a direct shortcut to the Chrome.exe executable in the %PROGRAMFILES(x86)%\Google\Chrome\Application directory and then launch it from there.  However, this doesn’t fix the problems with trying to open .HTML files and URL links from other applications, which still trigger the error.

Lots of suggestions abound across the internet regarding ways to temporarily correct this problem.  Most of them center on the deletion of the Chrome Classes registry keys affiliated with the file/protocol associations, but these are only temporary; the problem resurfaces each and every time Chrome updates itself, which happens a lot.

Instead, there seems to be a much easier solution.  Bear in mind that I have only thus far tried this on one machine, but it worked immediately, and it jives with other research I’ve done on related subjects.  Please let me know in the comments if this solution also works for you.

The fix?

  1. Uninstall Java (all versions).
  2. Uninstall Chrome.
  3. Reboot.
  4. Reinstall Chrome.

This corrected the problem completely on my user’s machine.  It may or may not work for you; if it doesn’t, try one of these other solutions:

  1. Open regedit.
  2. Delete (if present) the following registry keys:
    1. HKEY_CURRENT_USER\Software\Classes\Wow6432Node\CLSID\{5C65F4B0-3651-4514-B207-D10CB699B14B}
    2. HKLM\Software\Classes\Chrome
    3. HKLM\Software\Classes\ChromeHTML\open\command\DelegateExecute
  3. Reboot.


  1. Open Default Programs and set a different browser temporarily to default (for example, IE).
  2. Open Chrome and choose to set it as default when automatically prompted.

Hopefully this helps someone else struggling with this problem.

Solution: “Only part of a ReadProcessMemory or WriteProcessMemory request was completed”

If you’re encountering this error, you should first know that it refers to a memory access problem of some type.  The vast majority of scenarios where it occurs are during program installs or executions from an optical drive, and that’s what most of the internet offers as a solution.   To fix those problems, the solution is well-known.

When I ran into this problem, I was unfortunately more interested in everything not related to CD/DVD media.  Instead, it was occurring each and every time I attempted to execute an application on my client’s PC.

I checked the usual suspects, including file associations, IFEO (Image File Execution Options), and plenty of other items.  But in the end, it was a likely culprit: the client had previously had Kaspersky Internet Security installed (not a bad program by any means), but in an attempt to remove it, the process apparently failed.  This left some of its drivers behind, including some filesystem filter drivers which were preventing the execution of applications until Kaspersky okayed them.  Of course, since it wasn’t installed, that never occurred, and instead this message appeared.

To fix the problem, I ran a cleanup utility from Kaspersky’s web site and checked for stray drivers using a deep system scanning utility.  Following that, everything was peachy.