I'm trying to make a program that utilizes the Microsoft Biometrics API with a fingerprint reader. So far I've gotten to the point where I can scan the finger and get data from that.
But the only problem is that I can't run the program and make the scanner work without Administrator Rights. This is a problem for the application I'm making as the tablet it's supposed to run on is not supposed to run as Admin while this happens.
Is there any way to get around this?
I found out that the answer to this is No. It's impossible.
Related
I cannot find any definitive information anywhere but the System.Windows.Forms.SendKeys class appears to have been blocked / disabled / depreciated in Windows 10.
I wrote a demo program that monitors the users keystrokes and if a user enters a known code it will pop up a form and then go off to a document database and return various strings (company names / addresses / contact lists etc) and replace the typed code with the retrieved string. SendWait is used to send the retrieved strings to whatever program typed the code.
I built the program on the companies Windows 7 desktops but when I ran it on my personal Windows 10 system it didn't work. A lot of reading later and I feel like a complete idiot but I cant let them take this project any further knowing that they wont be on Win7 forever.
So my question is has this sort of functionality definitely been disabled in Windows 10 or is there another way or method I would be able to use to achieve this behavior of inserting text into running programs.
Any help appreciated.
I found this Forum-Thread:
https://www.tenforums.com/software-apps/49635-sendkeys-not-working-windows-10-a.html
SendKeys is Blocked in W10. In W8.1 it still works.
There are other anoying things, like not allowing App to Read or Wright to Drive C. The "file" is there but W10 "hides" it or simply not allowing to access it.
There are Netwok problems also, not allowing App to work on LAN environement.
Well, my opinion is that W10 behaves like Malware to user PC. Useless.
They had no solution.
It looks as if Sendkeys works with some apps and not others. I can automate an older app by sending it keystrokes but newer apps like Chrome don't respond. The inconsistent behavior has seriously messed up scripts that worked fine under Win 7.
I have not found any official documentation that says that Sendkeys has been deprecated so the inconsistency looks to be a Windows 10 bug.
I am having trouble with System.SystemSounds.Beep.Play() not making any sound for a particular user. It seems to be working for everyone else (a fairly large user base with generally 24/7 use) but simply does not make any sound for a particular user.
What I would like to know is if this method has any particular idiosyncrasies that I should be aware of, particularly if they could cause this issue (but really even if they couldn't too)? Has anyone else run into something like this that might point to this being a non-programming issue?
Some extra info that might help: (or might be more confusing)
It does not appear to be a corrupt .NET install because it appears for a particular user across machines.
The user is using the same Active Directory profile for all these machines when they have the issue
Another user can log into the machine and use the exact same executables to get sound successfully
The particular location where the user is has Windows XP machines, though not all users do (some use Windows 7)
You may want to check this link:
http://www.howtogeek.com/howto/windows/turn-off-the-annoying-windows-xp-system-beeps/
make sure that the beep sound is not disabled for the user.
Are the system beeps still on his computer? check C:\Windows\Media, because Beep.Play(); should work fine.
Some other possible problems just to be sure:
The speaker volume isn't at 0%?
The speakers are installed correctly?
Check Windows Control Panel - Sound
Sound event reference must to be set.
For example:
default beep -> Windows Background.wav
Is there any debug/prepossessing param or any option under Windows 7 and visual studio to prevent from other processes hooking to my process?
I am writing a game for Windows, under Visual Studio, and was wondering if there is a way to disable user to hook to the game's process?
No, that's not possible. Even if you could somehow disable hooking, the user could still attach a debugger to your process and do anything they wanted. That's by design, of course: it's how you debug the problem when you write it.
Once a user has installed a program on their machine, assuming they have sufficient privileges, they have full control over that program. Trying to limit it programmatically is a fool's errand.
The solution to this program is not to be found with code. You need to investigate the built-in Windows security model, like creating limited user accounts; ask more questions about that on Server Fault.
The short answer is no.
On a Windows machine (like most other machines) a user with sufficient privileges will always have the ability to inspect and or modify the contents of your game process's address space.
That said, what sort of user(s) and or attack(s) are you looking to defend against? What assets are you looking to protect? Once you've identified these, you can start thinking about how to design your application such that attackers would have a more difficult time getting at what they want.
I'd start with reading up on Threat Modeling. Good luck!
Disabling is not possible. What you want to do is detecting byte patches, hooks or even just reading in the games memory region. But you better give up, because its not worth the time.
I have previously posted a question about this but I did not get an answer that suited my needs, so maybe I need to be more specific?
I am trying to make my program instantly start up when the person logs in. It is a computer locking device so I need it to start as soon as possible. I know this is possible because anti-virus programs do this. Such as ESET or Avira.
I currently have my program entering a key into the registry to enable it to start up when the user logs in. But I need it to be much more efficient to maximise security.
Any help would be appreciated,
Thanks.
Actually, most anti-virus programs run as a windows service. If you need instant on then that's the only way to go.
The part you see starting after log in is simply the UI for those services.
Is there a way to make Windows Mobile not use the main phone app? I have my own phone app that I want to handle phone transactions for a business device.
My app works fine (detects the call and can hang up), but the main phone app still wants to allow the user to answer a call normally. I can try to hide the incoming call window or programmatically press the ignore key, but that is a bit clunky.
Basically, I need a way to make the built in phone app not know about incoming calls.
Any advice would be appreciated!
In case it matters I am using a Symbol MC70 running Windows Mobile 5.
Thanks!
EDIT: Thanks to djhowell's answer to this question I now know that the offending app is cprog.exe. But apparently it is hard to kill because services.exe keeps bringing it back.
First of all, you should not do it. Replacing system dialer will create you more troubles than you can expect.
If you still want to do it, there is no nice way to do it, even if you opt to use RIL directly. So, there is a trick in which you create a dummy cprog.exe (which does absolutely nothing), and put in the root folder . After the phone boots, that program will be started instead of the native one that is located in the \Windows folder. Then no program will be listening for incoming calls.
I would recommend asking Symbol (actually Motorola), they may have insight into your problem. I work with MC3090's and they were helpful before.