Hello this bug has happened to me. I simply turned on microprofiler during a play test via the esc menu. Now everytime I open studio I get this
This bug is definitely not resolved, if you mess with microprofiler on a public game, it will haunt your Studio for days. Switching it off with Ctrl+Alt+F6 shortcut is both faster and seemingly makes it go away for good.
I’ve been using the shortcut, I am still being haunted by the microprofiler ghost.
Try spamming it a bit (turning profiler on and off), maybe even turning off with mouse then using shortcut a couple of times. I think that’s how I did it. If that doesn’t help, well… it’s a spooky season, enjoy your Studio ghost 
I spoke too soon and was using my laptop. My main PC is still haunted by the Microprofiler… 
its insane how this is still a bug in 2023
I had this problem. Turning off in play test esc menu seems to have resolved it. (fingers crossed)
Same, I had the issue where although GlobalBasicSettings_13.xml>OnScreenProfilerEnabled is set to false, it still shows microprofiler everytime studio launchs/playtest starts
Using a program on windows called “Everything”, I found that there is 2 files while searching “GlobalBasicSettings”. There was GlobaBasicSettings_13 and GlobalBasicSettings_13_Studio (both located under %localappdata%/Roblox). I found in the studio one that OnScreenProfilerEnabled was set to true. Setting that to false fixed my issue.
I have to warn that setting OnScreenProfilerEnabled to false while studio is open will not work, even though Windows allows you to do it (it resets it to true once studio closes). You need to fully close studio and then set OnScreenProfilerEnabled to false.
Sorry to bump the thread, first of all I wanted to THANK YOU for this solution, since that microprofiler has been bothering me for a very long time and it’s a real pain when you need to test multiple clients locally.
This is hopefully related, but I was wondering if maybe you or someone else knows which setting or setting flag controls the top toolbar visibility. Because for me it repeats the microprofiler issue - something happened and now it ALWAYS starts hidden, so I have to double click any menu item to expand it.
Very annoying. I asked for permission to post bug reports like a month ago and still have no access.
I wish Roblox would work on UI persistence more, it would save all of us so much time.
Sometimes my client settings resets, it can be happened after update or random, idk, but i have issues with microprofile too
Hopefully you solved this before I posted this response,
Anyways this is the button to toggle the UI to be constantly opened.
Or you can double click any tab like “Home” to do that.
OMG, thank you very much. Apparently it does not save the state when toggled with double-click (which was my habit after opening Studio), but does with that tiny button.
It’s 2024 now, and this bug still exists
Manual setting
it can indeed solve the problem, but it is uncertain whether it will reappear after the next automatic update
A little bit insane that this is STILL a bug as of July 22, 2024
Same here, I thought I was the only one to have this bug. It’s extremely annoying
Still a problem, micro profiler appears on studio boot up… Thankfully navigating to the xml via ctrl+r that Premium_Gym posted managed to be a scuffed yet viable fix.
Just as a follow up to this, if you close the MicroProfiler via the Escape menu or key combination it will set the settings file. There is an issue if you just use the MicroProfile Mode menu and set it to “Off” this doesn’t alter the file so it will restart once you restart the application. We will fix this but this is the workaround for this.
Using the Escape menu and the key combination doesn’t fix it for me… I’ve had the MicroProfiler automatically open for several days now, with no way to close it. I also can’t find the “GlobalBasicSettings” xml file to manually fix it.
You need to look for a GlobalSettings_13.xml or GlobalBasicSettings_13.xml file in these directories:
Mac:
~/Library/Roblox
Windows:
Users\<YOUR_USER_ID>\AppData\Local\Roblox\
We have fixed this bug:
