Share via

Application Deployment returns Error Code 0x1(1) Incorrect Function (Action Failed)

Question

Wednesday, February 6, 2019 1:49 PM

we are receiving error 0x1(1) Incorrect Function (Action Failed) for many of the Application deployments in the SCCM 1802 , but by checking the machine status, sccm client status - we could see the machines are active with clients. 

Could you suggest on how to provide solution for such failed deployments

Regards, Shanker Kumar

All replies (4)

Thursday, February 7, 2019 9:08 AM âś…Answered

Hi Shanker Kumar,

0x1: Incorrect function.
      Source: Windows
So it's a windows error.

  1. Please confirm that the path of the Application installation has sufficient permissions, and the operation related files exist.
    such as:
        .Installed in the root directory of the C drive, but you do not have permission to complete the installation.
        .Or this application wants to modify the name of a file in the c:\windows\system32 folder, but this file does not exist, he will report the same error.

  2. Also check if there is any appLocker to prevent installation.
    https://social.technet.microsoft.com/Forums/en-US/b8973034-ce93-4ff6-9363-389326976e89/user-assigned-application-returns-error-code-0x1-1?forum=configmanagerapps
    Appenforce.log will tell you more information.

Here is an easier way to confirm it:
Do not deploy this application via SCCM, run the application directly on the client to confirm whether it can complete the installation.

Best regards,
Yuxiang

Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact [email protected].

Wednesday, February 6, 2019 2:29 PM

Just because a deployment failed doesn't mean there's anything wrong with the client agent so the fact that the status is active is more or less irrelevant.

You need to troubleshoot the deployment on the client itself although this error is from the command-line that you've supplied for the deployment type. ConfigMgr simply runs the command-line that you supply on the source files that you provide. If that errors out, all ConfigMgr can do is give you an error code. You need to troubleshoot your command-line.

You can validate that this was indeed the return code from the command-line by checking the appenforce.log on the client though.

Jason | https://home.configmgrftw.com | @jasonsandys

Tuesday, February 26, 2019 4:38 AM

Hi Yuxiang,

i am also having the same issue in infra not able to find any Permission and applocker policy's issues.

Manual installation is working as expected from remote share this is not happening for all the applications its happening for only few which are powershell based installations

Device policy's are up-to date no other issues found. could you please help me with solution for this. 

Thanks, 

Naresh.J

Naresh

Tuesday, February 26, 2019 4:06 PM

The answer is as above -- there's no magic answer here. You need to troubleshoot each command-line specified individually. Each command-line is also specific to the application that you are trying to install so what exactly is wrong could be different for each and is certainly completely independant from ConfigMgr.

Jason | https://home.configmgrftw.com | @jasonsandys

  • Last updated on