Windows 10: Failed to set plaintext hotkey

Started getting this error today. I've run chkdsk with the f switch. It doesn't tell you if it found any problems, but after rebooting the situation is the same. Advice, please. Thanks.

:)

 

S60/S^3 authenticated smtp server problems - Unable to send message

Thank you for your concern, again.



We have tested it throughly now and found the reason: there is smth wrong with CRAM-MD5 authentication (the technical part went over my head). The server and client could not resolve the auth method, thus authentication failed. We had never noticed it before
as all the other clients decided to fall back to plaintext authentication when CRAM-MD5 failed and passed the problem point. Also, what confused me was it that it accepted mail for domains which were hosted in the same server, even when authentication failed.
Apparently RFC does not require fall back to plaintext (instead it declares "the client MAY fall back to plaintext") so that's why your client does not have such a feature. However, most of the e-mail clients do that in case of failure.



The ISP administrator reconfigured the server so it now authenticates in secure way whatever happens.



So: THE SYMBIAN CLIENT IS OK sorry

 

Store OpenVPN credentials in the Credential Manager

I use OpenVPN. In order to connect, I have to enter a username and password. I know that credentials can be stored in plaintext, but I would like to store them securely. FWIW, OpenVPN is also installed as a service. Is there a way that I can store the
login credentials in the credential manager so that it can connect without me having to enter the password? Barring that, is there some way that I can set the integrity level of the plaintext file holding the credentials so as to limit access to it?

 

From what I can tell, this originates from the JoeJoe's freeware utilities, ArsClip. If you don't have the latest version (12/13/17) you might want to upgrade and see if that helps. Otherwise, you might have to uninstall that application until a fix comes through.
HTH,
--Ed--

 

Thanks, Ed. I didn't suspect that since WINKEY+X is a normal shortcut to a menu in Win10. But I think you're correct.

 

Hint: the ArsClip at the upper left-hand corner of the error message window -- thanks for including that BTW -- is what clued me in. Otherwise, I would've made the same assumption you did. Hope you get things fixed up without too much fuss or drama. Keep us posted on your outcome, please!
--Ed--

 

I haven't had that particular error message pop up lately, however I'm still having problems with icons in my task bar ignoring the right mouse click. Even the folder icon refuses to show me the file explorer. The left click on the search icon does nothing. But the right click does work. That's the only task bar icon that responds to a right click.

No click, left or right, works on the windows icon. Rebooting hasn't fixed this, but it only started acting this way within the last week. Malware Bytes doesn't find any virus. There shouldn't be any programs installed recently but I can't get to the control panel to check it out. Guess I could run chk dsk repeatedly. Is there a better switch than "f'" to use for this purpose?

 

Hey larrdonline,
If you haven't already, boot into safe mode and see if you can un-install that ArsClip to see if that fixes the issue.
Boot into Safe Mode on Windows 10 Performance Maintenance Tutorials

Otherwise, run the following commands ... see what/if they find/fix things

Open Command Prompt as Administrator

Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /RestoreHealth
sfc /scannow


Note: They can take 10~15 minutes each to run, so be patient *Smile

 

Let us know if you run into problems with DISM reporting itself unable to find the necessary files in its default source -- that is, with using the /source attribute properly. This can pose interesting challenges of all kinds.
Please keep us posted!
Best wishes,
--Ed--

 

At this moment it appears the problem was having ArsClip auto start with Windows. Since I use it during every session it seemed helpful to just have it start with the system boots but that appears to be what's been messing with my right click menu. If I run the program after booting it works fine and there is no problem with right click. Thanks for all the help and suggestions.

 

Easy fix then, and all you need to do is run the program when you want to use it. Seems like a reasonable workaround to me. Hope you feel the same way.
--Ed--