I am seriously at the end of my wits here. Microsoft of all companies should be better than this.
When I initially tried to update, it said I needed ~2GB at the default location (Packages folder). The installer would complete to 100% and then start over. Then I tried to install in a different location, but this time it said I needed ~120GB (almost like it’s reinstalling the whole game). After desperation, I attempted to just download the 120GB “update” in the new location in hopes the game would work after that and it STILL hangs up on the same “fs-base-0.1.211.fspatch.003”. I’ve tried everything including the obscure NetLimiter trick. I have the game on Steam and when I open the Xbox App, the game IS NOT ON THERE. I am signed into the same Xbox account on both apps. I tried reinstalling MSFS but I’m not even sure where the game is installed exactly. When I uninstall from Steam, it just removes the installer, not the game.
I seriously have no idea what else to do. If anyone has a solution that worked from them for WORLD UPDATE 7, please share. So far I’m only seeing some people get lucky which is seriously unacceptable for a game this expensive.
They have tested it, because the vast majority here have encountered no issues this time. But I agree, the process should be simplified. Just one installer app from which we can install the core sim and optional content. Mix this with MarketPlace 2.0 and I thing we will see a lot of happy simmers here. Shelve the shoddy Store and Xbox app.
I don’t have it on Steam. But if you tell it to use a different location then the 120GB is normal, because it will download a whole new copy.
I’ve never had it get stuck on a file but I’ve seen other people with the issue and they fixed it by closing the installer, then going into the folder where it’s trying to install that file. Delete the file it’s getting stuck on and then you run the game again. It’ll realise that file is missing and reinstall it.
Pointing your installer to a different location though is going to trigger a full new installation because the new location is empty.
For a fresh install you do have to install the world updates again. Go into the market place and grab World Update 7 to save a step if you haven’t already. Then in the content manager you’ll have to re-install the world updates and whatever other add-ons you had.
That wouldn’t of helped too much in my case. Prior, steam was on C and MSFS used the D drive for additional content.
My MB won’t boot from an NVME and it was my OS C:\ drive. I’ve since moved Steam over to a dedicated SSD. I also don’t have native NVME support on my MB or any PCI-e slots left.
With Moore’s law being completely shot and 2022 supply chain issues, replacing what I have would be a mad fortune. These are weird computing power times.
Maybe I misunderstand you, so sorry if I do. But when I pointed the installer to my dedicated D-drive (nvme) the core part still installed on the bootable c-drive.
So I think I don’t understand the relationship to a bootable drive.
My original Steam library was on my C drive. It was the only drive I had.
When I got MSFS I popped in a SSD I had when MSFS said it had no space left. So all the MSFS content downloads went there. The original Steam content and other files were going to C.
After the last update the C drive filled up to near 100%. So I was speculating that is why my install crashed out.
I’ve since made the 1TB SSD drive 100% dedicated to MSFS.