Cannot find "Mixed Reality Link" app in the Microsoft Store! HELP!
I recently had to re-install windows 11 fresh due to my PC getting corrupted by Microsoft's 24H2 Feature Update which was annoying enough, but now I am trying to re-install all my apps and I am trying to re-install the Mixed Reality Link software, however for some reason, I cannot find the app in the Microsoft Store https://aka.ms/mrlink : All I see when doing a search is: Why can't I find the app now and how can I get this back so I can link my Meta Quest 3s? Is there some issue with the Microsoft Store? Please help! Thank you!!Win 10 MS Store Unable to Update Apps
Issue: MS Store shows all apps need updating and are in "pending" status. Active download stay at 0% or error out. Troubleshooting: 1) Reset app. 2) Ran troubleshooter. 3) Terminated store app processes, repaired, and reset. 4) Let MS tech remote attempt to fix (deleted store app and reinstalled.) I am currently in the MS Insider program and did not know about it until attempting to troubleshoot my broken MS Store client. I had a MS tech remote in and attempt to resolve it but none of their attempts worked and they put the fault on the Insider. I do not know what to do and have followed the basic troubleshooting for the app and really need this remediated as it is impacting my telework and all of my out of date apps are blocked from loading,
Microsoft Store Doesn't Work...
I can't download ANYTHING from the Microsoft store. Whenever I try to download anything I get the 80072F8F Error. I can't seem to download anything relating to Microsoft either I Can't install the latest version of the Minecraft launcher, nor can I download the Xbox app both give the same Error (80072F8F). I've done basically everything that it says to do online, I've restarted my pc, reinstalled the Microsoft store via PowerShell, Checked for corrupted files, Checked my Date And Time and some other things. I'm REALLY frustrated with this so if anyone could help, or tell me to do something I haven't already done that'd be great! And if this isn't the place to post this could you redirect me to somewhere that can help me? Thanks!Unable to build APPXUPLOAD from .NET 9.0 / C# / WinForms project
Hi! We were advised by Microsoft Visual studio Developer community to create this issue on GitHub. But it was wrong direction. So, you're the third instance where we're trying to solve it. We hope that it is relevant to this section. Please, let us know if not. The corresponding threads can be found https://developercommunity.visualstudio.com/t/Unable-to-build-APPXUPLOAD-from-NET-90/10892325 and https://github.com/dotnet/winforms/issues/13377. --- The essence We’ve met this problem during the project (C#, WinForm) migration from .NET Framework 4.8.1 to .NET 9.0. Steps to see the problem We’ve migrated the project, compiled it and tested its functionality. Here we’ve found out that we are now required to publish the app with the .pubxml profile to make a single and not self-contained .exe instead of .exe-.dll-.json-.json… whatever this supposed to be. Using the publishing profile we’ve obtained the single-file executable that we’ve tested on Win10-x64 and Win7-x86. Both tests have been passed. The installation of .NET 9.0.4 desktop redistributables is not the problem for our aims. It is even better to not to “take” it with the executable. We’ve removed the .NET Framework project and added the .NET 9.0 project to the .wapproj dependencies without other changes. After this we get 3 warnings (fig. 1) about compatibility. After that we can get two results: The builder can create a 100Mb bundle for 450Kb executable or (if single file option is enabled) 100Mb the-entire-OS-in-one-file executable. So, we literally can build package. But it will completely ruin the user (who downloads the app from Microsoft Store) experience. Not to mention that such an installation size is simply inadequate for the goals and objectives of the product. With another project (we've tried it too) the builder can refuse to build the code during to non-existing errors (like missing ‘using’ directive). Exactly the same code has been successfully built during the publishing process 10 seconds ago. Our thoughts: there is some problem in the .wapproj file and/or in the MSIX builder. Because all warnings and errors come from the step before zipping .MSIXs into .appxbundle. --- How to reproduce directly Use this project to build a single-file-exe: https://github.com/user-attachments/files/19913854/TestProject_NET9.zip. This is the partial copy of our actual product without our own sensitive assemblies. It’s free for testing (available on GitHub). Add the new MSIX/APPX packaging project, connect the .NET 9.0 project to it. We can only provide our sample of .wapproj, without certificates and thumbprints, just to check its properties and verify its integrity: https://github.com/user-attachments/files/19913870/ScreenShooter_MSIX.zip. Try to publish the bundle. Tried workarounds Creating new .wapproj: no effect Clearing all building directories and caches: no effect Updating NuGets: no effect Other notes Also when builder tries to do its work we can see about 900 warnings about possible compatibility problems for basic methods from System, System.Windows.Forms and other assemblies. So, now we can still publish Android apps, APKs, Windows MSI packages, EXEs. But we cannot build apps for Microsoft Store. Which is not funny at all. --- So, how can we fix it? We’ve lost 6 hours in search. But found nothing useful. Thank you in advance, RD AAOW FDL
Can't install "Mixed Reality Link (Preview)": "Get" button greyed out
Hi there! Today I tried to install to install the "Mixed Reality Link (Preview)" app from the Microsoft Store. Even though my PC meets the system requirements, the "Get" button is greyed out. It seems that more people are having the same issue (https://techcommunity.microsoft.com/blog/mixed-reality-link/mixed-reality-link-coming-very-soon/4355631) when trying to install the app (from https://aka.ms/MRLink or https://apps.microsoft.com/detail/9pcnzpd0zw44 ). On my first try, I had Bluetooth disabled, and the page said my PC didn't meet the requirements. I enabled Bluetooth and restarted Microsoft Store, and even though later it said it meets the requirements (as per the screenshot above), the "Get" button is still greyed out. I already visited the following pages, but could not find any information that could help me solve this issue: https://www.meta.com/blog/quest/meta-quest-v72-update-remote-desktop-hand-tracking-keyboard-more/ https://techcommunity.microsoft.com/blog/mixed-reality-link/mixed-reality-link-coming-very-soon/4355631 https://aka.ms/MRLinkGetHelp / https://support.microsoft.com/en-us/windows/about-windows-mixed-reality-link-4155d287-182d-4003-b189-b42a4e357fc5 https://www.meta.com/help/quest/articles/in-vr-experiences/oculus-features/mixed-reality-meta-quest/ Any tips? Thanks!
InstallAppXPackages not working (Microsoft Store, MSEdge Apps, AppX)
Running FSLogix version: 2210 hotfix 3 (2.9.8784.63912) The problem: Microsoft Edge "Apps" and apps installed through Microsoft Store (such as "TypeClipboard") do not persist after logoff on dedicated machines (assigned user always logs into same machine). Workaround: User must reinstall Microsoft Edge "Apps" and apps from Microsoft Store every time they sign-in with a new Windows session. Attempted solution #1: InstallAppXPackages=1 The outcome of attempted solution: Seems to be 100% ineffective, problem remains unresolved. I do confirm the `AppData\Roaming\FSLogix\AppxPackages.xml` file is being correctly written within the Profile Container. Attempted solution #2: Exclude `AppData\Local\Packages` with Copy=0 Attempted solution #3: Exclude `AppData\Local\Packages` with Copy=3 Outcome of attempted solutions 2 and 3: Ineffective, problem remains unresolved. Solutions 2 and 3 reversed. Solution 1 still in effect at time of writing. Machines OS: Windows 10 22H2 ADMX configuration is as follows: Logging\Log Keeping Period = 3 Profile Containers\Container and Directory Naming\Flip Flop Profile Directory Name = 1 Profile Containers\Container and Directory Naming\Volume Type = VHDX Profile Containers\Enabled = 1 Profile Containers\Install Appx Packages = 1 Profile Containers\Is Dynamic = 1 Profile Containers\Locked Retry Count = 3 Profile Containers\Locked Retry Interval = 15 Profile Containers\Reattach Count = 3 Profile Containers\Reattach Interval = 15 Profile Containers\Size In MBs = 76800 # 75 GB Profile Containers\VHD Locations = \\contoso.lan\FSLData # DFS share used Profile Containers\Roam Identity = 1 # Workaround for Microsoft 365 re-auth issue, environment lacks true SSO configuration Profile Containers\Keep Local Directory (after logoff) = 1 # Applicable to assigned dedicated machines only Profile Containers\Redirection XML Source Folder = \\contoso.lan\FSLCfgDedi # Applicable to assigned dedicated machines only Profile Containers\Reboot On User Logoff = Reboot only on any FSLogix Profile logoff (3) # Applied only to test machine for time savings during troubleshooting Redirection XML being used here: <?xml version="1.0" encoding="UTF-8"?> <FrxProfileFolderRedirection ExcludeCommonFolders="33"> <Excludes> <Exclude Copy="0">AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Logs</Exclude> <Exclude Copy="0">AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\PerfLogs</Exclude> <Exclude Copy="0">AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\WebStorage</Exclude> <Exclude Copy="0">AppData\Local\Publishers\8wekyb3d8bbwe\TeamsSharedConfig\meeting-addin</Exclude> </Excludes> <Includes> <Include>AppData\Roaming\Microsoft</Include> <Include>AppData\Local\Microsoft\Office</Include> <Include>AppData\Local\Microsoft\Credentials</Include> </Includes> </FrxProfileFolderRedirection> Things that DO work: Profile Container in general (creates in SMB repo if not exists, mounts, stores user data, dismounts on logoff) Persistence of Microsoft 365 authentication and user customizations (OneDrive, new MSTeams, Office apps, Outlook) Persistence of general application customizations Persistence of pinned Taskbar and Start Menu items Redirection XML setting ExcludeCommonFolders=33 Redirection XML excludes and includes Writing this post feels like preaching to the choir / beating a horse vibe after having done a lot of Googling on this.
