Strange Vortex I/O error for a drive letter I don't have

[TennesseeTuxedo]

This started happening a few weeks ago (see attached png).  When I open Vortex, I get this strange error, "I/O Error (1005)" "Accessing R:\.GamingRoot".  I have no R drive, never have, nor have a folder that I know of called "GamingRoot".  It appears innocuous, I simply click "Ignore" to workaround and does not seem to cause any further effect.  I am currently using Vortex to manage Starfield, which is the game Vortex defaults to on open.  I didn't find this folder configured in any Vortex settings.  What could be the cause?

Apologies for sending this error message since it says right in it to not report it, but why would we get this when we open Vortex?  Vortex throws this error, is there any information as to why it does that?  Why would it report a drive I don't even have?  Kind of at a loss here.

[showler]

 

[TennesseeTuxedo]

Thank you, that answers that question!

 

I had just found in the logs too, something related to xbox (I'm running on PC).

Tue, 19 Dec 2023 05:58:14 GMT - debug: [gamestore-xbox] Not a valid xbox gaming path errno=-4094, code=ENOENT, syscall=stat, path=R:\.GamingRoot, nativeCode=1005, allowReport=false
 

 

[Pickysaurus]

Your Xbox game store is badly configured (which originally caused the error). 

The change in the Vortex beta just silently ignores this problem. 

[Jonnan]

Has this ever been fixed in general? I've been having the same issue with D:/.GamingRoot