I’ve rebooted three times and have tried to open my file in the IDE at least twenty times.
Get this fixed !!!
Do you have an open ticket, perhaps with an example project? I’m sure that there are those in our community who would be happy to weigh in. “Does not work” is a little vague. And on this forum you’re addressing “us” more than Xojo directly. 
1 Like
It starts spinning the wait wheel and never stops.
I’m hoping to get more people to stand up.
They will if they can reproduce it. I run the IDE on macOS, but I could certainly install it on my Win11 VM.
My questions would include version of Xojo ( I presume 2025r1), version of Windows, RAM and other specs, and of course whether plugins are in play. Also, is this specific to your project or will it happen with, say, a “Hello World.”?
What version?
Does a different/older version work?
Can you try without Network, e.g. Wifi off?
No such issues on Windows 11 here. Can you open the more complex Eddies Electronics from the examples?
What project type do you want to open, how old is it? When did you work with Xojo Windows the last time successfully?
You need to explain what Xojo version, what Windows version, and if you are using any plugins.
Windows 11 here, no plugins, no issues to open and run.
Are Xojo examples being loaded?
1 Like
There is a known issue on Windows with Web projects in the 2025r1 release.
#78767 - IDE Hangs when opening new web project on Windows 10
3 Likes
I am running it on win11 I have been using it from win 10. I have never had it hang for me. I remember one release really caused a slow down but never had a hang. I just completed a program that contacts 4 microprocessor units, gets data from each device, manipulates it, and displays the results with charts and gauges via tcp/ip. I use XOJO from several win 11 computers as well with no problem. It sounds like it may be something in your machine.
Thanks Tim. This case says it’s been closed. I’m using windows 11 with xojo 2025 r1.
The case is marked for a milestone after the current public release.
I’m not sure how much more I’m allowed to say.
Check to see if you have access to the Pre-Release channel.
1 Like
Thanks. How would I get access to the pre-release channel?
1 Like
With a Pro license as you appear to have, “Testers” should just appear in your categories popup.
I had the same issue, Windows 11. They had been working on it since January. R1.1 beta fixed it. I think the new release will be out next week.
Tim
I have the same issue frequently running any recent version of Xojo on Windows 11. Erasing the *.xojo_uistate file in the folder with the source code fixes it. Closing Xojo while still running the debugger is a pretty sure way to leave this file to sabotage the next time you open the project. There are also other times it gets left there too, but I haven’t bothered to try to document them. Its just easier to look for the xojo_uistate file and delete it. You have to restart Xojo after it is erased.
Hi Dean, what „same issue“ exactly? Is it fixed for you in Xojo 2025 r1.1 beta?
The issue I have is that the IDE does not load if I open a web project when a file with the project name and extension “.xojo_uistate” is present in the project folder. I have not tried it with the current beta. It happens on my Windows 11 computer on a project I only work on at home. I have not seen the .xojo_uistate extension on the old Windows 10 machine at work where I mostly work on API1 desktop apps.
I have the same issue frequently running any recent version of Xojo on Windows 11. Erasing the *.xojo_uistate file in the folder with the source code fixes it
That file “remembers” the state of the IDE when you last closed it.
Yes, deleting it resolves the issue that you have (and that I have from time to time also, but not recently). Also, before saving and exiting the IDE, display a method or an event. When code is last displayed, the .uistate file is not an issue, according to my own very limited experience. I suppose that the IDE gets lost somehow trying to show a page or a container upon a restart.
Xojo 2025R1 fixed the issue for me.
Tim