Add-AppxPackage doesn't seem to have an -AllUsers switch Running it as my actual admin still works fineĪdd-AppxPackage -Path "C:\Program Files\Notepad++\contextMenu\NppShell.msix" Windows cannot install package NotepadPlusPlus_1.0.0.0_neutral_7njy0v32s6xk6 because it must be installed with an external location. Which is fine by design! even if I give him local admin (PS running elevated)Īdd-AppxPackage: Deployment failed with HRESULT: 0x80073CF9, Install failed. NOTE: For additional information, look for ded7a0ca-a991-000b-4a65-d8de91a9d901 in the Event Log or use the command line Get-AppPackageLog -ActivityID ded7a0ca-a991-000b-4a65-d8de91a9d901 PS C:\Users\user> Add-AppxPackage -Path "C:\Program Files\Notepad++\contextMenu\NppShell.msix"Īdd-AppxPackage: Deployment failed with HRESULT: 0x80070005, Access is denied. But my normal userĭoesn't have it still (rebooted - didn't have to as admin, was there instantly. So the GUI variant works, the /S variant as well (tested it) - but only for the account that is running it. My admin (which of course ran the interactive setup I debugged with) Seems like in a corp env with "non-admin users" and "admin accounts/installer services", only those get the context menu. Path : C:\Program Files\Notepad++\notepad++.exe Manually ran this as admin (Add-AppxPackage -Path "C:\Program Files\Notepad++\contextMenu\NppShell.msix") This rules out some issue with the /S method from my POV. We deploy via Uninstall + Install, so no "inplace upgrade" issue should be present ever.ĭebugging via GUI install - Uninstalling, wiping my config when asked, then installing new - still no context menu. I updated our deployment to the latest version - 8.5.4 - and deployed. I am currently starting to test W11 in our env.Ĭoming from 8.4.x I checked for context menu support, discovered it was added in 8.5.0.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |