Hello,

I believe Support and I have pinpointed the policy in question you are testing with. One of the variables is ‘$exepathandname’ which appears to be referencing a non-existent file (with a ‘/’ in it) rather than the pure file name.

There are some additional backend logs indicating this is an issue as the script appears to exit with an error about being unable to find the file specified.

I imagine if you transplant the literal command you have in this OP you should see some success, but support didn’t see a Worklet with that exact install command. Let me know if you have any follow up questions and we can tackle it together.

Regards,

Mark

I have two examples to get this deployed out either with winget or .exe powershell install. Both of these pushed the packages in question.

I dont think I grabbed the exact package you were looking for with winget but here is the complete list of options:
 

Regards,
Mark

Hello,

Thanks for the replies.  My initial tests were using the command exactly as I demonstrated, further tests I was experimenting what path I should use to reference an MSI uploaded with the worklet because so far the worklets had been failing.

I’m interested in all of the logs you mention - all of which are logs that the end user cannot see, but would find extremely useful.  On a completely different note I think it would be most helpful if these logs, or the output, or some debugging info was made available in some way via the console.

I will go back to re-running the worklet, but from here I’rm not sure what I can try as I have no output as to why it is failing.

Cheers,
Mark

what path I should use to reference an MSI uploaded with the worklet

Any files uploaded to the Worklet are downloaded into a dynamically generated directory, along with the powershell script. You can reference them locally since its in the same directory as the script.

Which is what I thought!

For reference, this approach seems to be working…

Start-Process -FilePath "dotnet-hosting-6.0.36-win.exe" -ArgumentList "/install", "/quiet", "/norestart", "/log c:\log.txt" -Wait