User Profile
Aditi_Narvekar
MicrosoftJoined 5 years ago
User Widgets
Recent Discussions
Re: MSIX application, unable to stop automatic start-up on Windows 8.1
The above answer should work. Although if you can't modify the package and reinstall, it might be easier to post-install delete the startup task that was installed. https://github.com/microsoft/msix-packaging/blob/master/MsixCore/msixmgr/StartupTask.cpp describes how the startup task is parsed when installed via msixmgr, youshould be able to open task scheduler and find and disable the task. In task scheduler, navigate to folder Microsoft\Windows\MsixCore and find the relevant task to disable.2.3KViews0likes0CommentsRe: double clicking msix in File Explorer gives Invalid value for Registry error
It sounds like the Microsoft.DesktopAppInstaller app may not be installed or is broken. Can you try running Get-AppxPackage *install* to check the status of Microsoft.DesktopAppInstaller app. You can repair the app from apps settings page12KViews0likes1CommentRe: MSIX Hero - access to the path is denied
DavDef thank you for your question. MSIX hero looks like it's a third party tool, so troubleshooting that might be something you'd have to bring up with the owner of that tool. If you're interested in using Microsoft's tool, we do have a tool called Msixmgr which can help you create the VHD also. Azure has documentation on it- Using MSIXMGR tool - Azure | Microsoft Learn2.2KViews0likes2CommentsRe: Shared Package Container and AppModel API
TIMOTHY_MANGAN So a couple of things: this code can be run outside of any package or container. it is non-UWP C++ code calling into the cppwinrt API. this code can be called in a "simple" win32 C++ program that consumes cppwinrt. this cppwinrt API surface is for querying and modifying the SPC definition, but, it does not provide "live" diagnostics of the container (e.g. it does not tell you which packages are actually currently in the SPC)1.2KViews0likes1CommentRe: Shared Package Container and AppModel API
TIMOTHY_MANGAN There is an API for that yes SharedPackageContainerManager Class (Windows.Management.Deployment) - Windows UWP applications | Microsoft Learn One of our engineers has shared a snipped of code that might help get you started TEST_METHOD(GetContainer) { auto id = CreatSimpleContainer(L"container", { L"family1_8wekyb3d8bbwe", L"family2_8wekyb3d8bbwe" }).Id(); auto manager = winrt::SharedPackageContainerManager::GetDefault(); // Get container auto container = manager.GetContainer(id); log(L"Container name: ", container.Name().c_str()); log(L"Container id: ", container.Id().c_str()); VERIFY_ARE_EQUAL(container.Name(), L"container"); VERIFY_ARE_EQUAL(container.Id().size(), 36u); auto members = container.GetMembers(); VERIFY_ARE_EQUAL(members.Size(), 2u); VERIFY_ARE_EQUAL(members.GetAt(0).PackageFamilyName(), L"family1_8wekyb3d8bbwe"); VERIFY_ARE_EQUAL(members.GetAt(1).PackageFamilyName(), L"family2_8wekyb3d8bbwe"); }1.2KViews0likes1CommentRe: MSIX packaging using Quick Create Best Practices
You can create a virtual environment for MSIX packaging projects using Quick Create. Do you have any specific questions regarding the tool? Docs here- https://learn.microsoft.com/en-us/windows/msix/packaging-tool/quick-create-vm At this time we don't have a roadmap to publicly share out. You can read more about integrating MSIX with ADO here- https://techcommunity.microsoft.com/t5/windows-it-pro-blog/msix-packaging-extension-is-now-available-in-the-azure-devops/ba-p/2037333 .This blog post has links to documentation and how to get the tool.543Views0likes0CommentsRe: ms-appinstaller in Windows 2019 and Windows 2022
The fix to enable the ms-appinstaller protocol handler was rolled out to Windows 11 Insider Preview Build 25147 for the Dev Channel. Updates are being shared in the blog here: https://techcommunity.microsoft.com/t5/windows-it-pro-blog/disabling-the-msix-ms-appinstaller-protocol-handler/ba-p/31194797.5KViews0likes0CommentsRe: MSIX Package with service fails to immediately install the service.
Yes, the service doesn't get executed until the app runs. You said "the service ends up not installed immediately, which is confusing and inconsistent with other packages.". Can you clarify what other packages you're comparing between? MSI and EXE don't have this experience.1.2KViews0likes0CommentsRe: MSIX AppAttach FSLogix Profile issue between packaged app versions
Nick-S thank you for your question. The AppData root folder should be package family name based, so it works across different versions. Here it looks like FSLogix persisted app data in a version based folder. Looks like an FSLogix issue for me. One solution might be for you to change the app data folder name to exclude version number.2.3KViews0likes1Comment
Recent Blog Articles
No content to show