SendKeys not working on Windows 10

It does work very well on the 2 10 pro x64 machines I use and I can't see any legal problems with that

Mystere said:

Wow.

First of all. The Calculator in Windows 10 is a Universal app, unlike the old calculator. You cannot use SendKeys with it. Nothing you can do will fix that. It has nothing to do with UAC, there simply is no Win32 message passing between Desktop and Universal Apps. Further, Universal apps don't work at all without UAC because they depend on the UAC subsystem to function.

Hi Mystere,
Thank you for the info.
Now I understand why the Calculator is not working, that is a sort of System Wide incompability related to Win32.
The Real World, that is what am facing and talking about with the OS I was given, it is simply Blocking in Several ways my own App.
Even the TCP/IP networking gets Blocked.
For my App to Work I must disable the UAC.
I am tied down with UAC, what ever I choice, there things in one way or the other Stops work.

What ever MS is thinking and implementing "Security" (UAC, SecurePaths, Virtualization) it turns in Real World that my App is getting Prevented to work and there is no "Security" Reason envolved to prevent it. In the Other side, as I see around, the Real Malware W10 can not Stop it.
So, now I am questioning the Logical Sense of that Security of just blocking user´s.

W8.1 has a lot of that "Security" things but I can disable them and everything still works.
So far I can see, W8.1 will be my last Windows Version.

There are a lot of people like you who refuse to understand that Win32 is slowly going away. It's being migrated to WinRT (ie Universal apps). You're going to need to find other solutions to your problems if you want to work in Windows 10. It's not going away, and Microsoft isn't going to change their mind. Win32 will further and further become less relevant with each new release of Windows 10 (of which another is coming next month).

"What Microsoft is thinking" is the fastest way to transition everyone from Win32 to WinRT, just like they did with Win16 to Win32 (despite the fact there is still some 16 bit apps out there even today).

Microsoft's solution for people that absolutely need compatibility is probably virtual machines in the future. Kind of like XP Mode in Windows vista.

Mystere said:

There are a lot of people like you who refuse to understand that Win32 is slowly going away. It's being migrated to WinRT (ie Universal apps). You're going to need to find other solutions to your problems if you want to work in Windows 10. It's not going away, and Microsoft isn't going to change their mind. Win32 will further and further become less relevant with each new release of Windows 10 (of which another is coming next month).

"What Microsoft is thinking" is the fastest way to transition everyone from Win32 to WinRT, just like they did with Win16 to Win32 (despite the fact there is still some 16 bit apps out there even today).

Microsoft's solution for people that absolutely need compatibility is probably virtual machines in the future. Kind of like XP Mode in Windows vista.

That are clear words. From your last post I was already thinking that MS is letting Win32 out of the game.
Win32Help is also not working in W10 and MS did not provide a FIX as they did with W8.1
I am not happy with W10, for many reasons, alone that story around of "Take Onwership" of files and folders is something that is not nice.
Well, thank you for Info, everybody should know what is going on.
Buying me a new Developer Enviroment it costs a lot of money and I even do not know if it will work and for sure I will spend many hours to get it compiled again.
Let´s see if MS will suceed against the Win32 Croud.
EDIT: In the past, MS did the same dirty game with Windows NT, nothing new from MS.

KiloOne said:

I went back to W7 and so far so good, but what a job to get back to W7. It took hours to figure out how to get rid of W10 message that said I had to remove an Administrator account I had made in W10 before it would let me revert (I removed it but kept getting the same message!!!).

Finally found this (EDIT: But it seems to have been removed since I put this link here, solution was to delete the Administrator folder in the Users directory): https://www.tenforums.com/user-accounts-family-safety/22521-need-delete-elevated-administrator-account-windows-10-a.html

The link is deleted.
If you still have problems with Built-In "Administrator" account, I have the commands to enable or disable it.
My working PC will never see W10 and if it lands there by means of "Brute Force", I have a Image of the PC so that in question of few minutes I have W8.1 back.
Do you have made a System Image before Upgrade to W10? If you have it, go ahead and restore it, it is easiest way and secure way to have W7 back.

Adalwar said:

The link is deleted.
If you still have problems with Built-In "Administrator" account, I have the commands to enable or disable it.
My working PC will never see W10 and if it lands there by means of "Brute Force", I have a Image of the PC so that in question of few minutes I have W8.1 back.
Do you have made a System Image before Upgrade to W10? If you have it, go ahead and restore it, it is easiest way and secure way to have W7 back.

Have a just before image, but the Win 10 revert to 7 using windows.old directory did seem to leave some activity things that happened during 10 intact. Disabling that Administrator account did not work. W10 not again in my lifetime (I am old enough to say that :) ), but then again my wife said she just awoke one morning to Win10 on her laptop.

KiloOne said:

Have a just before image, but the Win 10 revert to 7 using windows.old directory did seem to leave some activity things that happened during 10 intact. Disabling that Administrator account did not work. W10 not again in my lifetime (I am old enough to say that :) ), but then again my wife said she just awoke one morning to Win10 on her laptop.

I did restore 2 times from a System Image and it works fine. One time , so far I recall, I even formated the System Partition at the time of restore, I am not sure of this, it is some time ago. But I have no things left from previous installantion.
In W8.1 you can disable the Automatic Updates. Also, there are some Tools around to prevent "Brute Force" update to W10.
I myself do not install any update since December 2015, I was having a lot of BSOD corrupting all my Partitions, I believe they were coming from the updates. At least , I removed all updates since 12/2015 and since more than 4 months no BSOD.
My system is working fine like it is, so way should I update if nothing is broken?
Unfornately seems that what is going on behind the scenes is an effort to "Bruce Force" programmers to move to the "Universal App´s" by means of not supporting/ locking Win32 App´s. If I am right on my assumption, that is a tremedus mistake, and W10 will die very quick.

Mystere said:

If you plan to use Windows 10, then i'd suggest giving up on SendKeys. It's not a maintainable solution.

You also don't mention what you're using to do your SendKeys implementation. If you're using .NET (C# or VB.NET) and you aren't trying to send between different privilege contexts, then there is an app.config entry that might help, read the note on the SendKeys class

SendKeys Class (System.Windows.Forms)

I am also having similar issue with my program which was working windows 7 and not in windows 10. My requirement is to keep my machine not to get screen locked, so i am keep on sending NUMLOCK on every 5 seconds to keep it alive. So with this requirement, how can i replace sendkeys to something else? Please point if you see any solutions

Antoops said:

I am also having similar issue with my program which was working windows 7 and not in windows 10. My requirement is to keep my machine not to get screen locked, so i am keep on sending NUMLOCK on every 5 seconds to keep it alive. So with this requirement, how can i replace sendkeys to something else? Please point if you see any solutions

@Antoops

Why not simply disable the screen saver? That seems like a far more logical solution. However, if that's not an option for some reason, you can always just use the SetThreadExecutionState method to temporarily disable it. (this is a p-invoke function, so no native .NET api). You can read more here:

SetThreadExecutionState function (Windows)
Disabling the Screensaver Programmatically