jon

Thanks, Samrae. I did go back and look at the free upgrade to 4.9.0.1, but it was not a good solution for us. All of our macros worked, but MEP would not load on start-up and required admin privileges, which is not feasible in our scenario. Moreover, some of our macros did not work consistently. So far, MEP v 6.x is working as expected.

Update: Simply upgrading to the latest version (6.1.3.1) seems to have fixed the problem, along with similar issues where hotkeys were not activated within a specified application scope. I'm glad to have finally found a solution (albeit a costly one), but I must say that it's very strange that v4.7.1.1 did not work with Windows 10, considering that support for this version didn't end until well after Win 10's release.

Thanks for the swift reply. It's not feasible for us to run MEP with admin privileges, because this macro has to function for all users. Still, I tried terminating MEP and restarting it as an admin, but the test macro still didn't work. I also tried running it in various compatibility modes. It seems odd to me that I would be the only one having this problem, but all of my google searches have turned up nothing. I'm wondering if there might be something wrong with my device configuration. Are you able to activate a macro using Process Event on NOTEPAD.EXE in Windows 10?

I have a macro that should trigger when a given process starts. It works fine in Windows 7, but not in Windows 10. Even a simple script that should show an alert when Notepad.exe starts will not work in Windows 10. I've spent all morning Googling why this might be the case, but I've found no explanation so far. I'm running Macro Express Pro 4.7.1.1 and Windows 10 with the most recent updates. I should mention that the macro does not work on earlier versions of Windows 10, either. Any help or suggestions would be greatly appreciated!