If you are typing inside the Search bar, Cortana, Taskbar, Windows 10 apps, etc., and then everything seems invisible then read on as this post will guide you in fixing this issue. At first, you might think that something is wrong with your keyboard but it really has nothing to do with it. The problem actually lies with the apps from Microsoft Store. Thus, if you can’t type anything in any of the apps from Microsoft Store in Windows 10, refer to the options given below to fix them.
Option 1 – Ensure that ctfmon.exe is running
Ctfmon.exe is a Microsoft process in Windows 10 that controls the Alternative User Input as well as the Office Language bar. In other words, it enables end-users to control the computer using on-screen keyboard inputs, speech, and even pen for various languages. It would be better if you launch the program once by going to the C:/Windows/system32 folder. Doing so will ensure that whatever API is needed for the keyboard typing to work properly again. You also have to make sure that its startup status is not disabled. In addition, you can also try the following steps, alternatively.
- Open the Task Scheduler.
- Then go to Microsoft > Windows > TextServicesFramework.
- And on the MsCtfMonitor, right-click and enable the task.
- Now restart your computer.
This will ensure that all the text boxes will start to work again. And if the task MsCtfMonitor is missing from the list of tasks, you can import it with the XML file from basics.net. Then download and create a task to run it each time you log in to your PC.
Option 2 – Use the Windows Store Apps Troubleshooter
You might also try running the Windows Store Apps Troubleshooter as it can help in resolving issues with the Windows Store apps. This built-in tool can resolve most of the app-related problems. To use it, go to Settings > Update & Security > Troubleshooting > Windows Store Apps and from there, click the start the troubleshooter button. The Windows Store Apps Troubleshooter will scan the computer for any issues with the Windows store apps and will automatically fix them if it finds any.
Option 3 – Re-register all the Windows 10 UWP apps using PowerShell
- First, make sure to close all the running applications on your computer.
- Next, in the Start search, type in PowerShell and right click on the result, and select the “Run as administrator” option.
- After that, type the following commands to re-register the Windows 10 apps. Make sure to hit Enter on each line:
- reg delete "HKCUSoftwareMicrosoftWindows NTCurrentVersionTileDataModelMigrationTileStore" /va /f
- get-appxpackage -packageType bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + "appxmetadataappxbundlemanifest.xml")}
- $bundlefamilies = (get-appxpackage -packagetype Bundle).packagefamilyname
- get-appxpackage -packagetype main |? {-not ($bundlefamilies -contains $_.packagefamilyname)} |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + "appxmanifest.xml")}
Option 4 – Try to run the DISM tool
You can also run the DISM Tool as it helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth” which could help in fixing the problem.
- Open the Command Prompt with admin privileges.
- Then type in the following commands and make sure to hit Enter right after you type each one of them:
- Dism /Online /Cleanup-Image /CheckHealth
- Dism /Online /Cleanup-Image /ScanHealth
- exe /Online /Cleanup-image /Restorehealth
- Do not close the window if the process takes a while as it will probably take a few minutes to finish.
Option 5 – Run the System File Checker Scan
System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files. To run the SFC command, follow the steps given below.
- Tap Win + R to launch Run.
- Type in cmd in the field and tap Enter.
- After opening Command Prompt, type in sfc /scannow
The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:
- Windows Resource Protection did not find any integrity violations.
- Windows Resource Protection found corrupt files and successfully repaired them.
- Windows Resource Protection found corrupt files but was unable to fix some of them.
Same as Windows 10, Windows 11 also keeps track of date and time using an internet time server. But in a case that you need to change the date or time for any kind of reason here is a guide for that process:
Bypass TPM with changing installation media
The true cause is that there is no working Border Gateway Protocol (BGP) routes into Facebook's sites. BGP is the standardized exterior gateway protocol used to exchange routing and reachability information between the internet top-level autonomous systems (AS). Most people, indeed most network administrators, never need to deal with BGP.
Cloudflare VP Dane Knecht was the first to report the underlying BGP problem. This meant, as Kevin Beaumont, former Microsoft's Head of Security Operations Centre, tweeted,
"By not having BGP announcements for your DNS name servers, DNS falls apart = nobody can find you on the internet. Same with WhatsApp btw. Facebook has basically de-platformed themselves from their own platform."
Many people are very annoyed by this and with the fact that they cannot use their social media platforms but it seems that Facebook employees are in even bigger annoyance as it was reported that Facebook employees can't enter their buildings because their "smart" badges and doors were also disabled by this network failure. If true, Facebook's people literally can't enter the building to fix things.
Reddit user u/ramenporn, who claimed to be a Facebook employee working on bringing the social network back from the dead, reported, before he deleted his account and his messages:
"DNS for FB services has been affected and this is likely a symptom of the actual issue, and that's that BGP peering with Facebook peering routers has gone down, very likely due to a configuration change that went into effect shortly before the outages happened (started roughly 1540 UTC). There are people now trying to gain access to the peering routers to implement fixes, but the people with physical access is separate from the people with knowledge of how to actually authenticate to the systems and people who know what to actually do, so there is now a logistical challenge with getting all that knowledge unified. Part of this is also due to lower staffing in data centers due to pandemic measures."
Ramenporn also stated that it wasn't an attack, but a mistaken configuration change made via a web interface.
Both BGP and DNS are down, the "connection to the outside world is down, remote access to those tools don't exist anymore, so the emergency procedure is to gain physical access to the peering routers and do all the configuration locally."
Technicians on site don't know how to do that and senior network administrators aren't on site.
It seems that it will all be down for a couple of more hours before the issue is resolved. 