Solved Weird behavior when typing accents (`) and apostrophes (')

[st1led]

Hello everybody!

Since a few days I'm experiencing problems when typing accents (`) and apostrophes ('). This issue seems to be non-keyboard specific, as it occurs with several keyboards that I tried. Hence, I guess it's some settings in Windows that has gone mad. The physical keyboard layouts is the standard US layout (e.g.: http://www.goodtyping.com/teclatUSok.png). In Windows, I set the keyboard layout (Control Panel\All Control Panel Items\Language) to United States-International.

This layout should allow me to type special characters, as in the bottom part of this page: https://forlang.wsu.edu/help-pages/microsoft-keyboards-english-us-international/. In particular, I should be able to type cedillas and letters with acute/grave accents, as I always did til few days back. Since then, when I press the accent or apostrophe key, the keyboard immediately writes two accents or two apostrophes. This also happens with the quotation mark ("). The default behavior should be that to type a single apostrophe/accent/quotation mark, one should press the correspondent key and then the space bar.

Example: to write it's I would normally press i, press t, press ', press space, press s. This sequence outputs it''s, with a double apostrophe, that I have to manually delete. With accented letters the problem gets even worse: to type è, I would press ` and then e. If I do so, the output is (randomly?) most time ``e, some times e, ``è is also possible, and è happens if I'm really lucky.

Any ideas? I tried rebooting (of course, first thing!), uninstalling/reinstalling the keyboard drivers, changing layouts in the control panel, everything to no avail.

 

[David Bailey]

Any ideas?

Try this batch file-

View attachment dism.bat

Run it as Administrator.
It takes a while to finish.
You can leave it run in the background if you wish.

 

[st1led]

Thank you for your help! I run the bat file as administrator (took ~1 hour) and then rebooted, but it didn't seem to help. The log in the command line window reports:

C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]
The restore operation completed successfully. The component store corruption was repaired.
The operation completed successfully.

C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

C:\Windows\system32>pause
Press any key to continue . . .

It seems that there's something broken that sfc /scannow cannot fix. I also attach the CBS.log, but I'm not sure what's wrong. The log is very long, and I don't know what to look for exactly.

 

[axe0]

The files that 'cannot be fixed' in the cbs.log:
utc.app.json
telemetry.ASM-WindowsDefault.json

These are false positive as they are for the upgrade to windows 10.

 

[st1led]

For those interested, I finally managed to get rid of this issue. Inspired by a thread on Microsoft Community, I run several full scans with antivirus/antimalware tools and found out I was infected with a keylogger that Kaspersky either couldn't detect or failed to disinfect. After getting rid of that, the issue disappeared.