CoreyZ
asked on
Program won't launch in Windows 10 version 1703; consent.exe error in Windows log
We have a legacy application (Paradox) that worked just fine in Windows 10 versions 1511 and 1607. However, on any pc that has gone through the update to version 1703, this application no longer launches. If you just double-click on the shortcut or executable, the program flashes (can be tough to see), but doesn't actually open. If you right-click and select 'Run as Administrator', the prompt comes up to allow the program to make changes, and when you select 'Yes' the program flashes and doesn't open. A consent.exe error is entered in the application log. I have attached a screenshot of the error log entry, as well as included the details below.
I have tried completely uninstalling the program (including registry entries, then rebooting) and re-installing, but the same behavior is still seen. I did find one thread that was similar, but the solution involved Software Restriction Policies, of which there are none on the relevant pc's (thread is here: https://social.technet.microsoft.com/Forums/en-US/fb7eea4a-c2ac-4c84-a9e5-a6063b04f4a2/uac-prompts-not-working-in-windows-10-pro-1511-or-1703?forum=win10itprogeneral).
We have three pc's that have been upgraded to 1703, and all three display the same behavior. On any pc that is running 1607, the program works perfectly fine. Any idea what changed in 1703 that would cause this, and how to resolve it?
Thank you.
- Corey
Error:
Faulting application name: consent.exe, version: 10.0.15063.0, time stamp: 0xe0f856c4
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000409
Fault offset: 0x0000000000000000
Faulting process id: 0x2b40
Faulting application start time: 0x01d2f0114a49a910
Faulting application path: c:\windows\system32\consen
Faulting module path: unknown
Report Id: 9cae341d-23f0-4fab-98a4-ec
Faulting package full name:
Faulting package-relative application ID:
Win10_1703_consent_error.pdf
I have tried completely uninstalling the program (including registry entries, then rebooting) and re-installing, but the same behavior is still seen. I did find one thread that was similar, but the solution involved Software Restriction Policies, of which there are none on the relevant pc's (thread is here: https://social.technet.microsoft.com/Forums/en-US/fb7eea4a-c2ac-4c84-a9e5-a6063b04f4a2/uac-prompts-not-working-in-windows-10-pro-1511-or-1703?forum=win10itprogeneral).
We have three pc's that have been upgraded to 1703, and all three display the same behavior. On any pc that is running 1607, the program works perfectly fine. Any idea what changed in 1703 that would cause this, and how to resolve it?
Thank you.
- Corey
Error:
Faulting application name: consent.exe, version: 10.0.15063.0, time stamp: 0xe0f856c4
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000409
Fault offset: 0x0000000000000000
Faulting process id: 0x2b40
Faulting application start time: 0x01d2f0114a49a910
Faulting application path: c:\windows\system32\consen
Faulting module path: unknown
Report Id: 9cae341d-23f0-4fab-98a4-ec
Faulting package full name:
Faulting package-relative application ID:
Win10_1703_consent_error.pdf
Two tests, please:
-logon as another user and retry
-right click the exe and select run as administrator and provide Administrator credentials
-logon as another user and retry
-right click the exe and select run as administrator and provide Administrator credentials
ASKER
Ramin: Thank you for the suggestion. We do have Symantec Endpoint Protection, v12.1.6 (so different version). I disabled it with the same result.
ASKER
McKnife: Thank you for the suggestion. The user is a local admin on the pc, so when selecting to run as administrator no administrator credentials are needed. I did try logging in to the pc as a different user who is NOT a local admin, and when running as admin was prompted for administrator credentials. I got the same result (program did not open).
Will it hurt to reinstall the program for a test?
ASKER
McKnife: As stated in my original post, I already tried completely uninstalling and reinstalling the program, which made no difference.
Sorry, already forgot about that.
I wonder if it is normal, that consent.exe enters the log (which is what bring up that UAC dialogue) and not the application itself. Could you test if elevating other executables works (for example elevate cmd.exe)?
I wonder if it is normal, that consent.exe enters the log (which is what bring up that UAC dialogue) and not the application itself. Could you test if elevating other executables works (for example elevate cmd.exe)?
Did you try to reduce UAC and check the result ?
ASKER
McKnife: Yes, other executables such as cmd.exe work ok with elevated permissions. In fact, after running cmd.exe as administrator, I tried to run the program in question from the cmd prompt. No errors were thrown; in the cmd window it looked like the program ran ok. But same thing happened as running the program normally - it flashed very briefly on screen, but didn't open.
Ramin: I reduced UAC all the way to not notify, with the same result (except that when running as administrator no prompt to confirm elevation of permissions was returned).
Ramin: I reduced UAC all the way to not notify, with the same result (except that when running as administrator no prompt to confirm elevation of permissions was returned).
Next step should be to install it on a clean 1703.
ASKER
<<Unfortunately setting up a clean 1703 isn't an option right now. We may be able to set up Hyper-V and put Windows 7 on that vm and use that, but that will require another Windows license...>>
Edited: Actually, we have a brand new laptop with Windows 10 1703, and someone else already tried to install the software on that laptop. It installed just fine, but the same behavior is seen when trying to run - it just flashes but never opens.
Edited: Actually, we have a brand new laptop with Windows 10 1703, and someone else already tried to install the software on that laptop. It installed just fine, but the same behavior is seen when trying to run - it just flashes but never opens.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Apparently that's the case. Still puzzled on what MS did so that the program won't launch in 1703 when it worked perfectly fine in 1607. Nothing else changed on the couple of pc's upgraded to 1703.
I guess this question will have to be closed as unresolved. Thank you to mcknife and ramin for taking the time to try to help; we appreciate it.
I guess this question will have to be closed as unresolved. Thank you to mcknife and ramin for taking the time to try to help; we appreciate it.
Ok, if you feel we didn't help come to a conclusion (not solution, conclusion), then select your own last comment as solution in order to close this, it's ok.
ASKER
The actual issue is unresolved, and there appears to be no way for the program to run in Win10 1703. Option to run in VM is likely the route to use until the program is rewritten.
https://support.symantec.com/en_US/article.TECH240364.html