Showing posts with label Windows 10. Show all posts
Showing posts with label Windows 10. Show all posts

Wednesday, February 28, 2018

Possible Fix for “Diagnostics troubleshooting wizard has stopped working” on Windows 10.

Here is a possible fix for when the Windows 10 Troubleshooter stops working: Check to make sure your Temp and Tmp environment variables are pointing to valid fixed drives.

[Note: Last I checked, flash drives and external USB drives did not work as a temp folder. Hopefully a future Windows 10 update will fix this oversight.]

Steps:
  1. Press Windows Key + Pause/Break to bring up the "Control Panel\System and Security\System" page.
  2. Select "Advanced System Settings" on the left side.
  3. Select "Environment Variables" at the bottom.
  4. See the "TEMP and TMP user variables"? Edit those to point to a valid folder on a fixed-drive, such as "C:\Temps".
  5. Do the same for the TEMP and TMP system variables. (You'll have to scroll down to find them.)

Friday, November 25, 2016

Solved: Windows 10 unable to type anything anywhere issue.

Recently, Windows 10 stopped letting me type anything in Search, in Start Menu, Cortana. Even calc.exe would not let me type!

Here is my story and the (so called) fix.

After much work and not wanting to do a clean reinstall, I was able to narrow it down to ctfmon.exe not running... (ctfmon is also known as CTF Loader, btw.)

I know from other fresh and clean Windows 10 installs that ctfmon does not appear to be running, so I am still confused on the why it allows this computer system to type.

If I kill the ctfmon.exe task, via Task Manager, then immediately again I am unable to type in anything metro-related. The old control panel search still works. Explorer still works. Everything works, except for new these new fangled Windows 10 apps.

If I run ctfmon.exe (Hint: you can press Win+R to run ctfmon.exe, or navigate in explorer to c:\Windows\System32), then typing immediately starts working again.

I still don't know why it stopped working or even why this fix works, but it does work [on my machine]! (Windows 10 Pro version 1607, if that helps anyone)