Windows 10: SendKeys not working on Windows 10

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.

 

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.

 

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 *Smile ), 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.

 

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

 

SendKeys are locked in Win 10 and 8.1 by the UAC.
If you need to use Sendkeys you may want to try Disabling it in the Registry :
HKLM>Software>Microsoft>Windows>CurrentVersion>Policies>System>EnableLUA=0.

 

SendKeys does not work, but it appears the API function SendInput does.

If you're in VB6, copy/paste this code into a module:

Private Type KEYBDINPUT
wVk As Integer
wScan As Integer
dwFlags As Long
Time As Long
dwExtraInfo As Long
End Type
Private Type GENERALINPUT
dwType As Long
xi(0 To 23) As Byte
End Type
Private Const INPUT_KEYBOARD = 1
Private Declare Function SendInput Lib "user32.dll" (ByVal nInputs As Long, pInputs As GENERALINPUT, ByVal cbSize As Long) As Long
Private Declare Sub CopyMemory Lib "kernel32" Alias "RtlMoveMemory" (pDst As Any, pSrc As Any, ByVal BYTELEN As Long)

' Overrides VBA.SendKeys, which throws Permission Denied error in Windows 10
Public Function SendKeys(ByVal Text As String)
Dim n As Long
For n = 1 To Len(Text)
SendKeysA Asc(Mid(Text, n, 1))
Next
End Function

' Send keycode
Public Function SendKeysA(ByVal vKey As Integer)
Dim GInput(0) As GENERALINPUT
Dim KInput As KEYBDINPUT

KInput.wVk = vKey
GInput(0).dwType = INPUT_KEYBOARD
CopyMemory GInput(0).xi(0), KInput, Len(KInput)
Call SendInput(1, GInput(0), Len(GInput(0)))
End Function