Well, that worked for about 20 minutes which is about 10 minutes more than I usually get. And I have done it a couple times back to back after restarting and it does seem to hold the mouse cursor in game for longer. But definitely not a permanent fix. But thank you for your good explanation of how to do it.
Hopefully we will get a fix for this major issue soon enough.
I hope in the next hotfix. Its on every flight yet. Last month I habe no issues. Frustrating
What means BUG LOGGED in the headerline ???
My personal work around, which has been working all night was this.
1.Turn on Xbox like normal with the Xbox controller.
2.Start the sim up.
3.Press any button on the controller to start when prompted.
4.When at the main menu I set the controller down and leave it on.
5.Plugged in all my Peripherals ie: mouse, keyboard, HOTAS.
6.Give it a second, then itāll prompt to keep all three as default. Which I clicked default. But all my preset settings that I set were still functional.
Now this was repeated a few times. With each time giving me 1 hour-ish of no issues. That is the longest time I have had without the mouse cursor glitch. At that hour mark I restarted my sim and console to see if it was repeatable. And at no point did I loose the mouse cursor.
And just to be sure. I started my sim up with all three peripherals plugged in and used the mouse to enter the press any bottom page, and also made sure the controller was off during this, and there it was, about 9 minutes before the cursor froze.
Went back to the method described and no mouse cursor loss.
So, this may or may not work for all. But I say give it a try. Shoot, it might not even work for me indefinitely. But hereās to hoping all this is moot and MS/Asobo get this major issue fixed.
Happy simming. 
Thanks for your detailed workaround description. Iāve tried it by following each step, but for me this is not working. My mouse freezes again after 2 minutes while the plane is parked /prepared for taxi.
Couple of days ago, I had a lucky day and it was working perfectly fine without a mouse freeze - at least for a mid-range flight from Munich to Crete.
I still keep fingers crossed that this bug will disappear with next SimUpdate 
Yeah some days no issues. Its very randomā¦
Workaround has been posted before but doesnt work for everyone and also if it does work then at random it still happens
Well going by the patch notes they posted for Sim Update 6 it looks like this again wont get fixed as its not in the patch notes at all, itās beyond crazy that there is still no fix in sight for this.
I didnāt see a ref to a mouse fix either and I read through the whole SU6 bugs fixed list.
We need to get more people to register a zendesk ticket much like the Hotas issue got traction and is being addressed. There is a Sim Update 7 due later this year so maybe it will happen in it. However if they are only going to be working on issues reported on Zendesk then we all really need to elevate this issue via a ticket on there as Iām not sure voting on this thread matters as much (or at all) as official tickets.
Trouble is, that there are likely only a subset of us XBox users who are using a mouse.
I still donāt have an email back about my ticket yet.
I theoreticaly have the setup of Gamepad , Keyboard, Thrustmaster Hotas One and mouse and have the mouse issue. Also a sometimes weirdly behaving Hotas One. I fly witrh the Gamepad and use only the throttle of the Hotas One.
But because of the issues I am only using Gamepad and Keyboard now.
Instead of having a mouse malfunction, I just donāt use one at all.
On Series S.
But it is in the Patch notes ?
-User should no longer get stuck in the Freelook view and be unable to bring the cursor back up on Xbox
or is this something different ? sounds for me like exactly this problemā¦
I read freelook as in infinite pan cockpit view. If it is I have no idea what the issue was re mouse there. Most of the mouse freezing problems (not all) seem to happen for me on the flight planner/world map UI. I had another one tonight. Even tried plugging in a 2nd mouse but to no avail. It would be good to know more about what they are referring to in those release notes though.
Something completely different
It is random. Sometimes at menu, others at map, and others during flight.
Also the mouse cursor does not change the icon, like on PC, indicating that you are over a control.
It should be fixed.
If the mouse vanishes or freezes, switch the Xbox off using the button on the console. Give it 5-10 minutes (maybe a little longer) and restart the console from the machine. From the dashboard, select MSFS and it should load using the āquick resumeā function, allowing you to recommence your flight from where you left it whilst also regaining control of your mouse. Seems to be the only workaround Iāve found and it has worked several times - itās not perfect but better than restarting a long flight if you can avoid it.
Its not fun to fly. What does Bug logged mean?
In the absence of a solution, I may have a clue for mouse problems with the cursor disappearing on XBox. I experienced recently a very strange behaviour 
.
Until now, I never had this mouse problem with my installation/setup.
But, I changed something ā¦ and the problem appears 
.
Itās very weird and I canāt seem to understand why it does.
Here is my experience:
My peripherals were previously connected thru an old USB hub (usb2) having an integrated 90cm cable (the one with the green plug and silver cable on the photo). I bought a new hub (usb3 - 60 cm integrated cable) and also an extension cable (2m good quality). I also made some tests with another old extension cable (90cm).
The disappearance of the mouse cursor is easy to reproduce in my case, as it always occurs in the same place: When I create a flight and navigate the map.
I play with the mouse (axes) and the wheel (to zoom), here, itās easy, because I have not yet started a flight at this time.
When the bug happens, the mouse cursor disappears, but the zoom function with the wheel still works (proof that the mouse ādriver/managerā is not completely dead).
When I connect the USB hub (the old model or the new, the one with four buttons) directly to the front socket of the Xbox, I never encounter a problem.
But if I add an extension cable (either 90cm or 2m), sooner or later the mouse cursor disappears (and the wheel still works for zoom).
Strange, isnāt is ?
Iāve also try to remove the extension cable, reconnect the USB hub, then restart the console (press whiteXBOX, restart). Then launch again MSFS - and got a quick resume - and Oh surprise, 
the mouse was working again with MSFS 
.
So I cannot explain this behavior to myself. It seems that the length of the cable (or the quality of the USB connectors ?) are causing the mouse to malfunction. In principle, it shouldnāt interfere, or itās all or nothing.
Is it a problem with signal delay, or attenuation? I would not know how to say it.
But what Iām sure is that I made several tests and it was systematic: the fact of adding an extension cable created the problems.
And since rebooting the Xbox, while keeping the memory copy (quick resume) restores the operation of the mouse, I will tend to believe that the problem is indeed related to the Xbox part, rather than MSFS.
This is very surprising behavior, and in my case the solution is for the moment not to use a USB extension cable.
If you are using long USB cables, try to shorten them if possible and see if the problems go away.
Not sure the issue is cable or hub related 100%. The problem is random in nature, happens most of the time on the flight planner map - I think because that is where most of the mouse UI type things are present including zoom in/out, clicking, selecting dropdown menus etc.
In my case I use a wireless mouse & KB with single wireless dongle into front of XBox and most of the time Iām ok, but 2-3 times a week mouse cursor movement goes and I just have the scroll and right click funtions. But no cables are involved.
On a side note I do have a 3m extension for the HOTAS and Iāve never had any issues of loss of control with the HOTAS using the extension cable.
I think this issue is a FS2020 UI issue. I am however unsure why certain types of hardware / usb hubs / usb ports cause it to occur more frequently than others.
Iām sure I saw someone reference a powered USB v an unpowered one, but I donāt think that has helped many people here either, once the cursor goes it goes until FS2020 is rebooted or as some are reporting now the XBox is rebooted and FS2020 is quick resumed (I havenāt tried this myself yet).
To me itās quite random. Would be great to have a fix or at least a workaround that doesnāt involve rebooting XBox or FS2020.
Yes, the problem seems to be related to a loss of link, or too much latency.
I donāt have access to the XBOX SDK (which is obviously restricted to accredited developers and subject to NDA), but Iām pretty sure it works like Windows, with message queues.
There must be a piece of code that is standard for the Xbox (and thatās why there are mouse settings in the consoleās main menu) and another piece in the simulator.
I suspect that in some circumstances the messages sent by the Xbox system are too fast, or too slow - which happens with large cables, or in a disturbed / saturated āwirelessā environment. And in this case, MSFS should lose messages and then be unable to resume further.
If this is what happens, it is reassuring because the solution will be in an MSFS patch. On the other hand, for this kind of problem, the difficulty is to diagnose where the problem is located in the code. Itās not necessarily easy to reproduce, and therefore to test.
But I agree 
: on the XBox everything should be wireless 
(except may be, the peripherals requiring external power like force-feedback). Life is better without wires, too bad that the joysticks still use the historic āfuseā USB connector. We want a keyboard, mouse and joystick that directly connect wireless to the Xbox (and donāt use an additionnal dongle) - but we can dream 
may be, one day .
You could be right regarding XBox SDK etc but it is their software on their O/S on their platform so it should work right?
The biggest trouble right now is not knowing if they even acknowledge it as an issue. I think it may be low priority as there are older PC bugs/more popular bugs and possibly only a subset of users are maybe using a mouse. We do all need to Zendesk the issue to boost visibility though. Otherwise in 6 - 12 months time weāll still be on this thread lamenting the absence of a fix.
