In all cases, Chrome will continue to work as a browser. At the same time, they also announced that Chrome will no longer be updated on Mac OS X 10.6, 10.7 and 10.8 platforms. Read Chrome Ends Support for Windows XP and Vista.Ĭonsider this as just one more way to encourage you to move off outdated and unsupported platforms.īut don’t think that Google is picking on Windows. Update: Looks like there’s an easier way to resolve this problem if you do not want to unregister ctfmon! Thanks to Jack Boling, all you need to do is to go to the properties of the Chrome shortcut and ‘ click on the Compatability Tab and check Turn off advanced text services for this program’.Google has announced that their Chrome browser will not be receiving updates in the future if you are running Chrome on Windows XP or Windows Vista. Just that, it’s Google Chrome and I just have to get it installed on my work notebook! LOL! Anyway, I hope that this has been helpful to you too if you happen to stumble on my site when looking for a fix to this temporary problem.
It’s Google that needs to get this fixed in the next few beta releases. Of course, Microsoft’s not to be blamed here. Repeat steps 1 through 3 for the Msctf.dll file. In the Run dialog box, type the following command: Regsvr32.exe /u msimtf.dllĤ. Run Regsvr32 /U on the Msimtf.dll and Msctf.dll FilesĢ. Now according to Microsoft, ‘Ctfmon.exe monitors the active windows and provides text input service support for speech recognition, handwriting recognition, keyboard, translation, and other alternative user input technologies.’ Sounds to me like something I don’t need at all (thankfully!)Īnd apparently, all you need to do is to unregister a couple of dlls, reboot and you’ll then be able to enjoy using Chrome! Yup. In fact, it tells you how to remove Ctfmon.exe entirely.īut before removing it, you might want to check and see if you really need the process or not. Again, that merely requires you to check out the Microsoft’s support site and the instructions are all spelled out there. So, all you need to do is to simply disable the process and Google Chrome would work just fine. Thankfully, someone found out that it was Ctfmon.exe that was causing Chrome to always fail for some reason. It seems like something in Windows is clashing with the Chrome process and is forcing it to close. Chrome would simply load and closes itself. The portable version which can be found if you searched for it in Google won’t run too. But it would mysteriously close the import settings dialog box nor would it uninstall itself. Countless searches showed quite a number too suffered the same problem as I did. Which is also why it’s so frustrating when I couldn’t get Chrome to work on my work notebook which is running Windows XP SP3. Pretty much everyone harping about Google’s Chrome these days.
0 kommentar(er)
