"The setup file you specified cannot be accessed" about microsoft-win32-content-prep-tool HOT 16 CLOSED

I had this issue to... was kinda dumb. I did a reinstall of windows and forgot to show file extensions. The name of the file was application.msi but the tool couldn't access the app because it actually was named application.msi.msi.

from microsoft-win32-content-prep-tool.

I was having this same issue. I signed for GitHub to state a resolution because I could not find one anywhere on google. Instead of opening an elevated command prompt and running the tool via command line just right-click the tool and run as administrator. The tool will then open in a command prompt window and you can enter the location for the source directory, file name, and output directory. This was not in the SOP I was following to create a win32app for intune. This is my one and only contribution to society. Have a Great Day!

from microsoft-win32-content-prep-tool.

It seems a lot of people have trouble running Intunewinapputil.exe. It may not be totally clear that the file specified with the -s parameter should be in the directory specified with the -c parameter. Also is it a good practice to NOT copy intunewinapputil.exe in the working directory, but place it somewhere in the search path. Doing so makes it easy to change the current directory without worrying how to call the executable. I get that these concepts tend to be forgotten since the demise of MS-DOS.

from microsoft-win32-content-prep-tool.

Hi @mpolow38,

Can you provide me with the command that you are using? Here's a sample that should work:

C:\temp\Intune> IntuneWinAppUtil.exe -c .\orca -s orca.msi -o .\ -q

Where the source file orca.msi is located inside the source folder .\orca.

from microsoft-win32-content-prep-tool.

Hey Nik, thanks for replyin'. Here is what I tried:

C:\intune>IntuneWinAppUtil.exe -c .\intune -s CiscoJabberSetup.msi -o .\ -q

And this is what I got back when trying to do that:

ERROR The setup file you specified cannot be accessed.

Jabber MSI is located in the same intune source folder, running as admin cmd

from microsoft-win32-content-prep-tool.

I am have the same issue. Was there ever a resolution for this issue?

from microsoft-win32-content-prep-tool.

from microsoft-win32-content-prep-tool.

I'm getting the error: ERROR The setup file you specified cannot be accessed.

I've run several commands and still end up with the same error
In PS:
E:\IntunePackages> .\IntuneWinAppUtil.exe -c .\IntunePackages\Source\68.12.49241 -s googlechromestandaloneenterprise64.msi -o .\q

I've also tried from command line as Administrator:
IntuneWinAppUtil.exe -c E:\IntunePackages\Source\68.12.49241 -s googlechromestandaloneenterprise64.msi -o E:\IntunePackages\Google68_12_49241 -q

Each time I get the same error:
Error The setup file you specified can not be accessed.
Some help on the proper command would be great.

from microsoft-win32-content-prep-tool.

I'm having the same issue when trying to package the Zoom MSI installer. I've checked all of our AV, running IntuneWinAppUtil as Admin, running CMD as admin and giving it the args. All give the same error. I also tried a different .exe entirely and no change.

Please specify the source folder: ZoomSource
Please specify the setup file: ZoomInstallerFull.msi
ERROR  The setup file you specified can not be accessed.

EDIT: Found it was how I was placing the msi file in the wrong folder.

from microsoft-win32-content-prep-tool.

Hey @mpolow38, looking at your example it seems that you are already in the intune directory.
The path specified for the -c and -o should be an absolute path or a relative path of the current directory.
Looking at your command line it seems like your folder structure is like this:

Incorrect:

E
└─ intune
    │ IntuneWinAppUtil.exe
    │ CiscoJabberSetup.msi

and I was able to replicate your issue (see image below)

Correct:

E
|  IntuneWinAppUtil.exe
└─ intune
     |  CiscoJabberSetup.msi

Note that I am running the IntuneWinAppUtil.exe from E: and not E:\intune.

@WVDHERE it seems like you are also in the same situation

from microsoft-win32-content-prep-tool.

Hey @mpolow38, looking at your example it seems that you are already in the intune directory. The path specified for the -c and -o should be an absolute path or a relative path of the current directory. Looking at your command line it seems like your folder structure is like this:

Incorrect:

E
└─ intune
    │ IntuneWinAppUtil.exe
    │ CiscoJabberSetup.msi

and I was able to replicate your issue (see image below)

Correct:

E
|  IntuneWinAppUtil.exe
└─ intune
     |  CiscoJabberSetup.msi

Note that I am running the IntuneWinAppUtil.exe from E: and not E:\intune.

@WVDHERE it seems like you are also in the same situation

resolved . Thank you

from microsoft-win32-content-prep-tool.

I tried everything mentioned above and I still get the error. Is there something else I can try to make it work?

from microsoft-win32-content-prep-tool.

For anyone else experiencing this, for me the tl;dr is: backticks.
my structure:

C
└─ intune
    │ IntuneWinAppUtil.exe
    │ GoogleChrome
    └─ Output
         | Source
        └─ googlechromestandaloneenterprise64.msi

So explicitly I would run:

Start-Process C:\Intune\IntuneWinAppUtil.exe -ArgumentList "-c C:\Intune\GoogleChrome\Source -s googlechromestandaloneenterprise64.msi -o C:\Intune\GoogleChrome\Output"

And this works. But as soon as I pass these directories which don't have spaces into -ArgumentList as variables, e.g.

Start-Process C:\Intune\IntuneWinAppUtil.exe -ArgumentList "-c $sourceFolder -s googlechromestandaloneenterprise64.msi -o $outputFolder"

It would fail with this error above. This seemed unusual since there aren't any spaces in the folder paths. If I passed C:\Intune\IntuneWinAppUtil.exe as $IntuneWinAppUtil to Start-Process it would still fire off okay. So it was just in the arguments list.

In the end, this was the solution for me:

Start-Process "$($deploymentFolder)\$($intuneWinAppUtil)" -ArgumentList "-c `"$sourceFolder`" -s googlechromestandaloneenterprise64.msi -o `"$outputFolder`""

I have other scripts which accept the variables with paths in -ArgumentList without quotes (providing there are no spaces in the path). I don't know what is different and why this utility doesn't accept these variables without quotes where other tools do (msiexec is one I can think of immediately that takes these variables like a champ). But I guess I'll keep this as my standard practice now in the future in case other tools end up being the same.

from microsoft-win32-content-prep-tool.

I did a right click of the application in my case notepad ++, went to properties, and then to the bottom circled area in attached picture. There was an option to unblock the application. After this, the path worked perfectly.

from microsoft-win32-content-prep-tool.

It seems a lot of people have trouble running Intunewinapputil.exe. It may not be totally clear that the file specified with the -s parameter should be in the directory specified with the -c parameter. Also is it a good practice to NOT copy intunewinapputil.exe in the working directory, but place it somewhere in the search path. Doing so makes it easy to change the current directory without worrying how to call the executable. I get that these concepts tend to be forgotten since the demise of MS-DOS.

^ Thank you!

from microsoft-win32-content-prep-tool.

Note: the path in the setup -s param is relative to the input -c param
My paths were
C:\Temp\in
C:\Temp\setup\setup.msi
C:\Temp\out

The correct command is:
intunewinapputil.exe -c "C:\Temp\in" -s "..\setup\setup.msi" -o "C:\Temp\out" -q

from microsoft-win32-content-prep-tool.