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.

Then:

  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: AppleSyncNotifier.exe – “CoreFoundation.dll was not found”

AppleSyncNotifier.exe….This application has failed to start because CoreFoundation.dll was not found. Re-installing the application may fix this problem.

This is the frustrating startup message you may encounter if you have iTunes installed and you’re like many, many other unlucky people out there.  The suggested solution on Apple’s website is to reinstall some other related iTunes components (Apple Application Support and Apple Mobile Device Support).  Unfortunately, this hasn’t fixed the issue on any machines I’ve seen.

Instead, the foolproof solution is to uninstall MobileMe.  Odds are you don’t use it anyway, and getting rid of it fixes the years-old problem that Apple still hasn’t resolved.

By the way, while we’re on the subject of terrible Apple software, their Bonjour program/protocol is equally guilty of such problems.  Open up your Application Event Log (Start > Run > type eventvwr.msc and press ENTER) and look around.  See if you aren’t one of the very many afflicted by the errors that Bonjour inexplicably adds to the log. If you are, you’ll have a hard time missing them: there are generally many thousands of them, relentless, back-to-back.

All of this Event Log activity from Apple’s program, by the way, is nothing good for your PC’s performance or reliability.  The Event Log service is not meant to record so many duplicate errors so regularly.

Apple might make great Apple products, but I don’t think I’m alone in saying that their PC software (for one thing) is absolutely nothing special.