Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error starting process (CreateProcess, 00000740, uiAccess="true")! #3345

Open
AlexRzk opened this issue May 4, 2024 · 0 comments
Open

Error starting process (CreateProcess, 00000740, uiAccess="true")! #3345

AlexRzk opened this issue May 4, 2024 · 0 comments
Labels
bug The issue describes a bug. It does not mean the bug has been reproduced by a developer.

Comments

@AlexRzk
Copy link

AlexRzk commented May 4, 2024

Operating System

Windows 11 - 22H2, build: 22621.3447

x64dbg Version

Sep 11 2022

Describe the issue

I tried to disassemble an executable file. But when I run it, this error appear: Error starting process (CreateProcess, 00000740, uiAccess="true")!
I already searched on the web how to resolve it but i keep failing. First i tried to disable all the UIAccess controls like Elevate only signed applications and all that stuff but it keep giving me the same error.
After that i also tried to move my x64dbg folder to the "C:\Program Files" folder.
Finally i used Ressource Hacker (as administrator) to modify the manifest and change the line uiAccess="true"/>
The first version of manifest was this one:
level="asInvoker"
uiAccess="false"/>

Now it looks like that:
level="asInvoker"
uiAccess="true"/>

But now a new error appear even before seeing the x64dbg UI: A referral was returned by the server.

Any though about that, I tried to resolve this error alone but its not working thanks for all the help.

Steps to reproduce

  1. Open x32dbg.exe
  2. Open a .exe file

Attachments

FirstErrorWhileOpeningEXE
MySecurityParametersSorryForFrench
modifyingMyX32DBGManifest
ReferalErrorAfterTheManifestModification

@AlexRzk AlexRzk added the bug The issue describes a bug. It does not mean the bug has been reproduced by a developer. label May 4, 2024
@AlexRzk AlexRzk closed this as completed May 5, 2024
@AlexRzk AlexRzk reopened this May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue describes a bug. It does not mean the bug has been reproduced by a developer.
Projects
None yet
Development

No branches or pull requests

1 participant