Just thought of sharing this.
I saw this weird looking volume drive in Defrag and was checking online for answers.
\?\Volume{7f09d586-c44d-0a20-cba4-677432426601}\
Strangely its caused by MSFS as there is an actual forum discussion here:
I checked Event Viewer and it shows that windows actually tries to defrag it but cannot and gives an error. Its supposed to disappear after reboot!!!
Strange!!
Bug report it to Zendesk if it’s keep causing errors.
It is related to the xvd volume drive that’s engaged through the rolling cache and preload scenery actions. XVD is MSFS.
Here more explanations:
https://forums.flightsimulator.com/t/multiply-entries/215395
Actual there are problems of left hidden entries that must be deleted manually.
Regarding XVD entries and volume entries.
@Jummivana Status is set as: Bug solved. It isn’t.
(Multiply left hidden entries Device Manager XVD MSFS)
If defrag actions get into problems with the XVD drive it’s mandatory to push it again out over Zendesk to get rid of the entries and problems via an update MS or MSFS.
@OxbowSuperset12 similar problems could happen if you have a virtual RAM drive engaged.
So check this first.
If not that’s the case please report it via:
Thanks. Already Reported it
Nice 
Perfect.
Small tip if you want to delete many devices at ones (there can be 100’s). Use Devmanview from Nirsoft shift/select and uninstall devices. Just be sure to not select a active one.
@Cygnifick Thanks. Will have a look at it.
@WatchfulLand959 I also have Xvd listed, like you mentioned.
Do I just right click and uninstall XVD ?
And how to check if it’s not Virtual RAM drive ?
Sorry, this is a liitle too advanced for my knowledge 
Yep i got the same. Noticed immediately after installing msfs (ms store non-custom address)
Never seen this happen before. I was all “panic! Hackxers!”… then remembered i had just installed msfs which makes absolute perfect sense
The Xvd is the active virtual drive for rolling cache and preload scenery from MSFS in normal status. This is totally ok. No RamDrive.
If you click in the device manager “hidden entries”. It will show left entries of the Xvd.
This must be deleted manually at current state.
Oh my, there must be 50 XVDs. I will now delete them. Thanks
Don’t delete all of them. I had 1, deleted it and the game could no longer be found. Had to reinstall.
Yeah, I left the one that was not hidden intact.
Flew the sim after I read your post, everything appears to be fine!!
Phew!!! 
Does it actually stop defrag from working? If it just gives log errors you shouldn’t need to bother. I have a ton of hidden devices and it never caused me any troubles.
I don’t need defrag because of NVME normally. I don’t think it stops or cause problems running defrag.
Ram Drives are another thing, if the configuration is not set right it will cause defrag problems. But that’s not MSFS related.
I deleted left hidden device entries periodical and would say it improve performance and at the end it’s sorted clean.
Added your post to the list of useful posts here:
No it doesn’t stop defrag or trim of other drives but Event Viewer showed that Defrag tried to defrag the weird volume and caused error :
The storage optimizer couldn’t complete retrim on \?\Volume{7f097486-c44d-0a20-caa4-777120426601}\ because: The operation requested is not supported by the hardware backing the volume. (0x8900002A)
Furthemore there were 50+ XVD’s listed!!!
So just to avoid errors I followed @WatchfulLand959 suggestion
Solution. But must be fixed due MS.
Dear folks, quite a number of you say that it is out of the scope of your knowledge.
Why do you touch that ?
Is it causing you errors or any other stuff that directly point at the Xvd volume ?
(and this ^^ detail is important)
Just leave it alone.
Enjoy life and enjoy the simulator.
If the developer says “hey people, you know we identified a problem, yall should go there and manually delete this and that” - then allright.
Otherwise…
Look, I see people experiencing totally bizarre issues with the simulator and “Microsoft or Asobo did it”.
Then after they hire me, when I remotely connect to sort things out, I am welcomed by both the massacred Windows and the simulator on it…poor little souls both somehow doing their best attempting to repair themselves via the automated built-in mechanisms… 
“Wtf, how did this happen, how did X got there and…okay I see the logs…okay, so why did you do it ?? - Well, you know, I went there and I saw Y for the first time…but I don’t know what “there” actually is and I also don’t have a clue what is that Y I’m seeing, so I asked Google and I read somewhere that I should delete it…so I deleted that folder and removed the Y, so I gained 5fps, runs smoother or whatever, etc.”…
Just…don’t touch anything, please.
PC “owners” and Windows users must be aware of this dev madness. It is not a good practise to create thousan of hidden volumes for nothing. I think this is a problem of Xbox app and all gamepass service games installed. On each load, more and more Xvd and his respective volumes are created in “our” drives instead of only preserve one per game installed, being kind and respectful enough to clean the rest of them properly. At the end, lack of information of what they do in “our machines” plus lack of true tech support are pushing us trying to solve the problems by ourself. I dont know what is happening but I feel, looking all Microsoft problems and crazy development in the last times, they are loosing north dangerously. When one machine’s piece fails, the responsability may be in that dev department but when all pieces are failing, the problem must be upstairs. Xbox app is a ■■■■, MFS2020 is a ■■■■, windows store is a ■■■■… all are Microsoft services and software running over Microsoft OS!!! ¿¿¿???. It is incredible that ANY game service from other companies are working years light better than that. But the big problem is not the bugs. The really BIG problem is the absense of responsability, respect and real feedback whit the “community”. SFC, DISM and reinstall all OS from scratch seams to be the only generic solution for almost everything. I’m coming from one of that after a MFS2020 update fail. The only solution was a CLEAN reinstall of Windows 10 to make possible a *!## game wants to be intalled again. This is not rasoneable for a supposed at the tech peak company and unfortunally the “dont touch anything” advise (till your system cracks for one or another reason due to garbage acumulation…), is not valid when nobody cares of the things they broke or “forgot” hidden in the device manager expecting stupid users and costumers doesn’t taking account or even care. SO MICROSOFT: Thousans of XVD hidden volumens are invading our device manager. FIX IT. CLEAN IT. TAKE CARE OF THAT or almost publish a tech note advising about that, becoue at the end it will be a problem to solve with another… CLEN WINDOWS 10 reinstallation!!!.
Just… FIX IT and be respectfull with us, MICROSOFT
