Problem with 1.34.16.0

Another update...

I tried running the NZ update again, and it still hung on the first file - the POI update. So I split the item in the Content Manager (list icon on the right end of each entry), then installed the three airports first. No problems there. Then I selected the POI entry and hit the install button. It looped one time on me, then when it restarted itself, it finally started loading, albeit rather slow. Not to jinx it, but at the moment, it seems to be running. I'm keeping an eye on it as I sit on the couch on my laptop.

Edit: It's still looping... :banghead: Guess I'll have to start a thread over on the official forum...
 
From the official site:

On Windows PC:
NOTE: This may cause the deleted content from Step 4/5 to need to be redownloaded/reinstalled.


Close Microsoft Flight Simulator.
Open File Explorer (Windows key + E) and navigate to the “Official” folder. Depending on your platform/install location, you’ll find the Official folder here:


On Windows PC (Microsoft Store/Xbox App):


C:\Users\YourUsername\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official or your custom location where you installed the simulator. You may also have one more sub folder called OneStore where you will find the files as well.


On Windows PC (Steam):


C:\Users\YourUsername\AppData\Roaming\Microsoft Flight Simulator\Packages\Official or your custom location where you installed the simulator.


If you installed Microsoft Flight Simulator from a disc:


C:\Users\YourUsername\AppData\Local\MSFSPackages\Official


Within the Official folder, delete any file that is not in a folder.
If you know the exact file name the Installation Manager indicates is stuck at decompressing, delete that file.


Within the Official folder, open the .fscontent folder and note the names of any files within (if the folder is empty, skip to the next step).

Return to the Official folder and delete any file folders which correspond to a file in the .fscontent folder.


Delete the .fscontent folder.

Relaunch Microsoft Flight Simulator and you’ll be prompted to update.
 
Expanding on all of the above. I just Uninstalled the entire POS, ran a Registry clean up, and am now at 50% Reinstalling. And yes, I do and did back up my Community folder. That alone took nearly two hours. It's not like I have not done it before. I'll take a flight and if it still CTDs, I'll know it's the dang Update and not some 3rd party App causing it. If it does, I'm done with MSFS 2020 until Asobo and MS fix it. Worst drug I have ever done, expensive, time-consuming, frustrating as Hell, and yet one can't live without it.

Cazzie
 
Deleting that .fscontent folder fixed my DC-3 Enhanced download. Once that folder was gone, smooth sailing on the download. Free Beer! j
 
Quite a frustrating update, with all the looping, deleting, etc. Reminded me of updates 2 - 3 years ago. I gave up last night, but went through more download-delete iterations today and finally got it to launch. I'm going to wait on the Content Manager stuff until the dust settles. I suppose 13 wasn't a lucky number for MSFS.

I'm not even sure I'll even notice most of the fixes/updates as they pertain to things I rarely use. Although, I do hope to see some improvements to turbocharged piston engines with the new sim variables for that.

- dcc
 
Having read the big thread on the MSFS forum (I cannot comment within it as they lifetime-banned me over a year ago for correctly calling an over-zealous moderator a bully), I will simply give this thought. If you have not opened up your MSFS since before the update, don't. Leave it until they officially come up with the complete and 100% reliable solution. It will save much frustration on your part.

This is a good weekend for going for a walk, watching a movie, spending more time with family, or reading a good book (or in my case as an author, working on my next one!).

There is life outside of MSFS, and this may be a pause for us all to remember that.

Have a good weekend gang!

- Kenneth
 
vipgroup said:
Having read the big thread on the MSFS forum (I cannot comment within it as they lifetime-banned me over a year ago for correctly calling an over-zealous moderator a bully), I will simply give this thought. If you have not opened up your MSFS since before the update, don't. Leave it until they officially come up with the complete and 100% reliable solution. It will save much frustration on your part. This is a good weekend for going for a walk, watching a movie, spending more time with family, or reading a good book (or in my case as an author, working on my next one!). There is life outside of MSFS, and this may be a pause for us all to remember that.Have a good weekend gang!- Kenneth
Click to expand...
"Pause" indeed :)
 
I just got mine installed .... all of it!

I've been at it all day long. #%@&**!!

I'd been over to the Official Forum https://forums.flightsimulator.com/ and here https://forums.flightsimulator.com/t/polls-sim-update-13-1-34-16-0-discussion/610522

None of those suggestions worked!

I remembered that we've had this ".fscontent" folder problem before and I looked up my old post about it. http://www.sim-outhouse.com/sohforu...ore-MSFS-troubles!/page2?highlight=.fscontent

Go down to the very bottom of the page and click on that picture I posted and do as it says (post # 33) .... delete ALL folders that were created by the install/update process (mine was today 9-29-2023)

It was 95 folders totaling about 45+ Gigabytes of stuff that I had to flush down the toilet! Remember to empty that Recycle Bin or you may not have enough disc space to install the update.

- Don
 
Hey guys, it's the ranter. I need to apologize to Asobo and Microsoft, because they were not the problem causing my CTDs. It was REX AccuSeason Advanced. How many of you have this App installed and are having CTD issues? If you are, it's a simple fix. Go into your Community folder and delete all files that have rexaccuseason on them. Then uninstall the App and delete the REX AccuSeason folder in your C: Drive. Also run a Registry cleaner and rid the Registry of all remnants of REX AccuSeason. This is not to blast the App, it worked fine in the last MDFS Version. But th new Version does not like AccuSeason, REX will have to come up with a fix, because it's a great program. However, if any of you are having CTD issues and have this App, it's your Huckleberry. I reinstalled MSFS and all was great until I installed REX AccuSeason, then I got CTDs again. Removed the files from the Community folder and did all above and my MSFS is doing great. Currently I just installed the Bijon Fall North/Spring South textures from the Marketplace and they're doing great. No CTD in three 30 minute plus flights so far, in fact no issues at all. Sometimes it does good to ditch the crap and do a fresh install. But AccuSeason was my nemesis here, not the Update, although the update was AccuSeason's nemesis.

Cazzie
 
Jeez, I'm glad to hear that. After all the hassle of building a new rig and then to hit CTDs with the update... Ugh.

Used to use all kinds of REX stuff on P3D. Bought their useless weather app on MSFS and decided to leave them behind.

Bijan was great for seasons, but he's gone AWOL (maybe he's on an island with the Boeing 247 guy, Jimmy Hoffa, and Amelia Earheart?), so I stopped using it out of fear that it was last recompiled about 8 sim updates ago.

At least seasons are coming in FS2024.
 
I had the thing happen too..It all started off like a normal update - this was at 9:am local time yesterday.
The install was finally complete at 11:pM last night.
The primary update installation was jank, with the loading bar going forward -stalling - then unwinding - then progressing again.
Then the content manager updates were jank - with the 'updates failed to install' messages - loading bars running forward and backward (looping) and on and on.
I cancelled all and closed MSFS the first attempt - restarted the PC -went to the Xbox site and checked for further app updates, and tried again - same sauce.
This time I just let it run - left the PC on and found other stuff to do. Eventually the main MSFS update dropped in and the sim opened so I could go to the content manager and try again to get the rest of the SU installed
Which one is this again ? 13!!? no wonder.
Anyway - I still had a number of 'failed to install' issues but updated the ones I could - then 'cancelled' the rest and closed MSFS - then restarted the PC and tried again.
This time I was able to get the remaining packages to install and then I ran a short flight just to make sure it was working - no CTD or other issues yet.

This is the first update since SU3 that gave me trouble. And I mean I checked internet connections and speed, reviewed all of my PC and antivirus settings, but when I checked the main forums it became obvious this wasn't an end user problem.
 
I too was stalled with the update. Help that worked for me is found in thread 21 posted by Tom Clayton. I followed instructions and all went well. Hope this helps.
 
Tried to use the close/delete/restart method this morning.

In the Official Folder there was only the OneStore folder and no files or folders to delete.

So it seemed there was nothing to do but to restart the update.

The Hercules decompress completed this time but stuck on another plane.

Repeated the close/delete/restart method a couple of times without success. Will wait for a new solution.

Tried the link by Tom Clayton, msg 21. Now the close/delete/restart message is gone from the OfficialBoard !

BTW How can I run the sim, while I seem trapped to update?
 
Also, if you fly the Asobo/AH DC-3 & have the Duckworks mod installed, you may get pink cockpit textures.
A DW fix via .to is being worked on.
T43
 
After my last post about starting a thread on the other board, my sim decided to cooperate. Sort of... I had to go through multiple iterations of looping with the Content Manager updates too, but at least now I don't have any more "update available" notices nagging me. Beyond that, not much has changed. I still get random CTD's. Yesterday's last effort was a flight from Asheville to Myrtle Beach that crashed as soon as I started to descend. This was in the DA62 with the "X" mod from the .to site. I've flown that plane successfully hundreds of times, so I have no clue why the sim would have crashed this time. I guess it just comes back to the true meaning of SNAFU...
 
You could almost think that this is a move to make people move over to MSFS2024 as fast as possible when it comes out.

No comments from MS/Asobo yet?

Priller
 
They seem to have gotten their sh . . . um, stuff together now (at least for me). All of my updates today downloaded and installed smoothly. I flew for a few hours this morning (I love Saturdays) without any problems at all.
 
Thanks for informing us Brian! That will be something for Sunday morning for me!

Priller
 
Tom Clayton said:
After my last post about starting a thread on the other board, my sim decided to cooperate. Sort of... I had to go through multiple iterations of looping with the Content Manager updates too, but at least now I don't have any more "update available" notices nagging me. Beyond that, not much has changed. I still get random CTD's. Yesterday's last effort was a flight from Asheville to Myrtle Beach that crashed as soon as I started to descend. This was in the DA62 with the "X" mod from the .to site. I've flown that plane successfully hundreds of times, so I have no clue why the sim would have crashed this time. I guess it just comes back to the true meaning of SNAFU...
Click to expand...

Tom, I have found that CTDs always lead to some 3rd Party software. Many will uninstall and reinstall MSFS, that is not necessary. Worst comes to worst, simply delete all the contents of your Community folder where 3rd Party Apps are stored, do a test flight with the Community folder clean. If no CTD, then your culprit was in there. My culprit was REX AccuSeason Advanced. The new Update did not like it and CTD'd every flight I took. If you have AccuSeason, that's your huckleberry.

Cazzie
 
You must log in or register to reply here.
Back
Top