MSFS 2020 Microsoft Store – WASM Error – Package files have not been copied yet
Hello. I am using MSFS 2020 Microsoft Store/Xbox version and purchased Miltech Mission Hub through the in-game Marketplace.
Every Mission Hub mission gives me:
“WASM Error – Package files have not been copied yet. Cannot start scenario.”
I have already performed a complete cleanup and reinstall of Mission Hub, deleted the WASM/Mission Hub folder, restarted the PC, repaired Gaming Services, verified write permissions and verified the InstalledPackagesPath.
My InstalledPackagesPath is:
C:\Users\varga\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages
The Community folder is writable but remains empty when I try to start any mission.
Could you please confirm whether the current MS Marketplace version of Mission Hub for MSFS 2020 has the latest WASM fix, and provide the current build/update if my Marketplace version is outdated?
Thank you.
Miltech Simulations @MiltechSimulationsHello Alejandro,
Have you attempted these steps?
Mission hub, unable to load mission due to WASM errorNote that for MSFS2020 the path is a little different:
MSFS2020 Steam
%appdata%\Microsoft Flight Simulator\Packages\miltechsimulations-missionhubMSFS2020 Microsoft Store
%localappdata%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\miltechsimulations-missionhub- GJ @Galactinator
Hello, I have the exact same problem as described above.
Windows 11 does not seem to allow me to change read and write permissions on the folder and immediately reverts them back to read only.
From what I have learned so far it appears that quote:
"Access restrictions in Microsoft Flight Simulator 2020 (MSFS2020) depend on the installation source. For the Microsoft Store version, the main application files are locked in a virtual disk format within the WindowsApps folder and cannot be accessed or modified by users without breaking game integrity; only the Official and Community add-on folders (usually on a secondary drive) are fully writable."I have been trying just about anything to get windows to apply read and write permissions to the folder you mentioned:
MSFS2020 Microsoft Store
%localappdata%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\miltechsimulations-missionhubNothing seems to work, the permissions always immediately revert back to read only.
Of all I could read and learn about the issue, so far the above explanation seems to make the most sense to me.
However, sadly i have not even been able to change permissions in the community or official folders:
suchas:
...\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\miltechsimulations-missionhubthis folder also immediately reverts back to read only permissions whenever I try to change them.
I'm at a loss and am wondering if I need to go ahead and completely uninstall and reinstall FS2020 and the Miltech Missionhub but I very much doubt even that would resolve the issue.
I suspect it probably has something to do with Win11 management of account permissions, but so far I have not been able to find any useful information that helps me resolve the problem.
Miltech Simulations @MiltechSimulationsHave you tried changing the permissions to Read and Write, and deleting the Mission Hub folder entirely after that?
Deleting the folder will force the sim to re-generate and re-copy the files, but Read/Write permissions should be kept.
- GJ @Galactinator
Yes, and it's not just the Missionhub folder that won't change permissions apparently it's all the FS2020 folders that are somehow 'protected' by Win11, as I wrote not even the missionhub folder placed in the official folder will let me change permissions either.
- Miltech Simulations @MiltechSimulations
It seems as if you don't have full administrator permissions over your PC. You'll need to take ownership over the folders on Windows: https://www.youtube.com/watch?v=DwbGrFAZHbY
Unfortunately, Mission Hub requires folders to be writable, as several files are copied and created on the AppData folders on your system.
- GJ @Galactinator
It's not that, I do have full ownership and admin rights on (all) the missionhub folder(s) and windows applies the read/write permissions, but only to then revert them back to read only immediately.
I now deleted the folders and uninstalled and then reinstalled FS2020 completely (even in a different game folder), but it did not resolve the problem.I also disabled the inheritance on the folder (which it did not revert).
I am the admin of the folder, I am the owner of the folder, I set just about everyone and everything on my computer to have full control over the folder. All these (security) settings persist, yet still the folder immediately reverts to read only.Maybe Miltech should look into a way of running the Missionhub with a separate (customer named/selected) folder that is not located within the virtual disk of the FS2020 game, if that is possible.
It would also be nice if you could at least check and reply to the original posted question whether the marketplace version really does have the update with the latest WASM fix or not.
Also it seems very odd to me that the missionhub, like all other packages, was installed correctly, by the game, the folder was created, content was written to it, but then the Missionhub itself can't copy and/or replace/update additional files (even though it repeatedly and immediately says the file was updated to version 1.0.2. in a green message after telling me the mission can't be started because of the WASM error)Thanks
- In reply toGalactinator⬆:Miltech Simulations @MiltechSimulations
Unfortunately MSFS is entirely sandboxed for security reasons, and we only have access to the folders contained inside the %appdata% installation path in MSFS. In any case, We may have a drag-and-drop solution for you: instead of letting MSFS build and copy files, I'll send you the ones that my installation of Mission Hub has built directly. We are soon moving to a "hardcoded" approach that just installs these pre-compiled files, instead of letting MSFS compile them and encounter such permissions issues.
Please send us an email to contact@miltechsimulations.com and confirm if you are on FS20 or 24.
- GJ @Galactinator
Thank you very much, I appreciate the help!
The more I read and learn about the problem, the more I understand it must be a somewhat common Windows problem that seems to occur in various forms and caused by various issues.
None of the instructions I found so far resolved it and apparently even a completely new clean windows install apparently does not always fix it, so it seems I will have to keep reading and contact Microsoft support.
Luckily in my case, so far I have not (yet) experienced any actual problems from this issue other than the mission hub not functioning correctly.Thanks again!