noels7

Hi Cavemanhead I had the same problem a 4 weeks ago as you are experiencing. Frustrating is a mild term for what I went through. Mine was a fresh install of Windows 11 and a download of premium deluxe version of MSFS which I own (receipt as evidence) Nothing I did solved the problem so after some research I deleted Xbox registration because after phone contact with Microsoft the result was that I was not a registered purchaser of MSFS. To overcome this problem I registered for a 1 month trial of MSFS Game Pass. $10.95 was the charge and it allowed me to d/load the version I had originally purchased. Everything tested out okay for a couple of weeks , went to Microsoft home page and cancelled game pass. Microsoft immediately refunded $10.95 into my bank account within a couple of hours (couldn't believe that as I live in Australia) MSFS since continually works without any problems. Apologies for such a long post but hopes this might help you noels7

Problem solved

I am unable to create desktop icon for FSCrew Product Manager Can anyone tell me where to create shortcut from. (file location). Any assistance would be appreciated. noels7

Hi Adamski Apologies for my delayed response. I have finally given up after 2 days trying everything from restoring 2 images (i am certain Button 4 was working as shown above), deleting Community folder,deleted Saitek profiles and then restored. Always the problem remains. The 2 irestord mages (25 and 29th Nov) produced a strange result. 29th image required a mandory update for MSFS but 25th did not. Don't understand why but MSFS at times is a strange animal. There are definitely no conflicts with Button 4 on the Flight stick. I have also done an insitu re-installation of Win 11 ( current updates ok). Problem remains. FBW has had several updates over the last 2-2.5 days ( including SimBride for 320 and FSTL injector) which have updated the same 2 times. Strange but with Community folder emtpy problem remains so FBW Fenix and PMDG 737 can be eliminatedas a cause. I have decided to use Mouse wheel click as an alternative to Button 4. Does the job but I preferred using Button 4 which had never posed a problem. noels7 Noel Southam

Hi Hopefully this is the correct forum for this topic. I have been using Saitek x56 since MSFS 2020 commenced and buttons (bindings) being used (my selections) with no problem until an update to the simulator yesterday. That update created havoc with my sim especially with with the bindings associated with Saitek x56. After many (and I mean many)hours spent, including Google, Avsim and FlightSimulator research I have managed to get all buttons, axis working correctly except the allocation of Button 4 on the flight stick. Screenshot_11436×681 105 KB Button 4 has always been titled "Cockpit and Outside Views (L,R,U,D) and gave me the ability to easily move around the cockpit and outside instead of using mouse click. I have tried everything regarding camera’s but, having somehow getting it to function yesterday on restart of MSFS today no such luck. Have I missed the obvious? Any advice/assistance would be greatly appreciated. noels7

sidnov From your response am I to assume that the Media Team have not issued an update recently and when could an update be expected. noels7

Watsi I note that you state that EFCS is now available in Experimental version. My installation of FBW has not shown an update for approx a week. Are there problems with your servers or other factors at play? Your advice would be appreciated. noels7

Problem now appears to be fixed. The problem was either a corrupt install of Macrium Reflect, corrupted data on USB rescue media flash drive or USB flash drive itself is faulty. Fresh install of Macrium, new rescue media on new USB appeared to fix problem. 12 hours wasted. noels7

Hi Fielder and The Moose Many thanks for your responses. Appreciated. I reverted back to image of 7 Jun . Updated 1.26.50 plus all other needed updates in Content Manager. Everything (aircraft, scenery, etc) appear to be working okay. I will now re-image (always use Macrium) and restore image that I created yesterday and see if that cracks the problem hopefully. noels7

vgbaron Many thanks for your response. Already tried that and problem still exists.

Reinstalled MSFS including update 1.26.50 and all updates in content manager yesterday. Everything tested and MSFS operating perfectly. This morning I attempted to start MSFS and got the following error : This app can’t open MSFS cannot open because it cannot be found. The storage device might be missing or disconnected. Is anyone else experiencing this problem at the moment. Any assistance/advice to rectify would be greatly appreciated. noels7

Similar problems I have experienced. Still awaiting response (sent 22 April 2022) Application Error 1 Log Name: Application Source: Application Error Date: 4/22/2022 9:18:00 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: DESKTOP-H9DAHAT Description: Faulting application name: FlightSimulator.exe, version: 1.24.5.0, time stamp: 0x00000000 Faulting module name: CoherentUIGT.dll, version: 2.9.5.0, time stamp: 0x619d1ccf Exception code: 0xc0000409 Fault offset: 0x000000000015dfb9 Faulting process id: 0x934 Faulting application start time: 0x01d855d902125aba Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe\CoherentUIGT.dll Report Id: 08a3905d-199b-42d5-bbd0-6ca4dfb200c6 Faulting package full name: Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2022-04-21T23:48:00.2969863Z" /> <EventRecordID>46380</EventRecordID> <Correlation /> <Execution ProcessID="2740" ThreadID="0" /> <Channel>Application</Channel> <Computer>DESKTOP-H9DAHAT</Computer> <Security /> </System> <EventData> <Data>FlightSimulator.exe</Data> <Data>1.24.5.0</Data> <Data>00000000</Data> <Data>CoherentUIGT.dll</Data> <Data>2.9.5.0</Data> <Data>619d1ccf</Data> <Data>c0000409</Data> <Data>000000000015dfb9</Data> <Data>934</Data> <Data>01d855d902125aba</Data> <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data> <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe\CoherentUIGT.dll</Data> <Data>08a3905d-199b-42d5-bbd0-6ca4dfb200c6</Data> <Data>Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe</Data> <Data>App</Data> </EventData> </Event> Application Error 2 Log Name: Application Source: Application Error Date: 4/22/2022 10:55:16 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: DESKTOP-H9DAHAT Description: Faulting application name: FlightSimulator.exe, version: 1.24.5.0, time stamp: 0x00000000 Faulting module name: d3d11.dll, version: 10.0.22000.527, time stamp: 0xf920f323 Exception code: 0xc0000005 Fault offset: 0x0000000000134e17 Faulting process id: 0x1ea8 Faulting application start time: 0x01d855e7519c6cb9 Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Faulting module path: C:\Windows\SYSTEM32\d3d11.dll Report Id: 59e2ba81-3383-45f2-83c7-e1e8d306471b Faulting package full name: Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2022-04-22T01:25:16.3731689Z" /> <EventRecordID>46429</EventRecordID> <Correlation /> <Execution ProcessID="9848" ThreadID="0" /> <Channel>Application</Channel> <Computer>DESKTOP-H9DAHAT</Computer> <Security /> </System> <EventData> <Data>FlightSimulator.exe</Data> <Data>1.24.5.0</Data> <Data>00000000</Data> <Data>d3d11.dll</Data> <Data>10.0.22000.527</Data> <Data>f920f323</Data> <Data>c0000005</Data> <Data>0000000000134e17</Data> <Data>1ea8</Data> <Data>01d855e7519c6cb9</Data> <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data> <Data>C:\Windows\SYSTEM32\d3d11.dll</Data> <Data>59e2ba81-3383-45f2-83c7-e1e8d306471b</Data> <Data>Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe</Data> <Data>App</Data> </EventData> </Event> Noel Southam noels7

Disregard

Thanks for your explanation, noels7 Noel Southam

Hi Bryan What have you done? I updated RAAS via Production Manager this morning. I never use Market Place to purchase Airport software. Free airports only from Flightsim.to, Paid from Orbx, NZAASimulations, axonos, Flightbeam, ,FlyTampa, Fsdreamteam, impulsesimulations (YPAD). On starting MSFS now all my airports are advising via RAAS that aircraft is on selected runway. RAAS is operating as expected. Auto start was never a problem for me. My commercial airports in Community folder are: ESSA,YMHB,YMML, YPPH, NZAA, KDEN, KLAS, YSSY,CYVR, YPAD, YBBN. Naturally (I believe) there are no airports in C:\Users\User\AppData\Roaming\FS2Crew MSFS RAASPRO\Airports. Could you explain what has happened to get(in my case) what changed with your update. Regards noels7 Noel Southam