This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(76.8, 49%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWR%3C/text%3E%3C/svg%3E)
We are intending to update an existing application that we have deployed in Intune. Those who get the application have it set as "Available." What we did was we overwrote the MSI with the latest MSI, intending to push it out that way.
Because the application likes to nag for updates and we have no local administrator rights on these PCs for most users, we changed the command line parameter to "/quiet /AutoUpdateDisabled=Yes"
When attempting to deploy the saved/updated app (it's an MSI LOB app), we get the following failure message: "Error code: 0x8001011F. This operation returned because the timeout period expired."
I also attempted to create a brand new instance of the app, and make the app Required, as opposed to Available, and receive the same error message.
Why do we receive this error message, and how can we get the app installed? The last version of the app/MSI did not have these issues.
Any update on this? Getting the same with GitHub Desktop MSI with command line:
msiexec /i "GitHubDesktopSetup-x64.msi" /quiet /norestart ALLUSERS=1
Any update on the following? I'm getting the same for GitHub Desktop msi for command line arguments:
msiexec /i "GitHubDesktopSetup-x64.msi" /quiet /norestart ALLUSERS=1
I can't recall exactly what I had done, other than I know I ended up making a new app in Intune for the new version with those paramters I had posted. The Command Line Arguments field was set to: /quiet AutoUpdateDisabled=Yes
So in your case, it would likely be /quiet /norestart ALLUSERS=1 if you're following similar process and creating a new Intune app.
@Wes Reinke Thanks for posting in our Q&A.
For this issue, the error code and message are not enough to find the cause. It is needed to check some logs. With Q&A limitation, Q&A is not the good channel for such log analysis issue. So, it is suggested to create an online support ticket to get more help. Here is the support link:
https://learn.microsoft.com/en-us/mem/get-support
Thanks for your understanding and hope everything goes well with you.
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.