How is Add-AppxProvisionedPackage Supposed to Work?

The Toolkit General Discussion
1

I’m completely confused by what I’m reading on the web and what I’m experiencing.

The documentation for Add-AppxProvisionedPackage states

The Add-AppxProvisionedPackage cmdlet adds an app package (.appx) that will install for each new user to a Windows image.

I have an ISE session open as my admin account (JT_Admin). I have another ISE session open as my non-admin account (JT_Useless).

As JT_Useless:
Get-AppxPackage | Where-Object {$_.Name -like '*Intel*Experience*'}
returns nothing.

As JT_Admin:
Get-AppxPackage | Where-Object {$_.Name -like '*Intel*Experience*'}
returns nothing.
Get-AppxPackage -AllUsers | Where-Object ($_.Name -like '*Intel*Experience*'}
returns nothing.
Add-AppxProvisionedPackage -Online -Package <pathtoAppx> -SkipLicense
provisions the app (I didn’t make note of the output and it’s gone now)
Get-AppxPackage | Where-Object {$_.Name -like '*Intel*Experience*'}
still returns nothing.

Back as JT_Useless:
Get-AppxPackage | Where-Object {$_.Name -like '*Intel*Experience*'}
shows that the application is installed for JT_Useless.

JT_Useless is not a new user. Why did he get this installed. Why didn’t JT_Admin? Is this the way this supposed to work?

1 Like
2

Hi JT-65,

Though I can see myself falling into the same situation as yourself some day, this site not the best place to ask.

Consider www.Reddit.com\r\windows

3

Thanks. I’ll try r/Windows. I’ve only ever tried r/Windows10 never had any luck…mostly because you can only ask technical questions on Mondays. Pfft.

4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.