Windos 11 problems

Bug Reports
1

problems with windos 11
I have upgraded to windos 11 and bootstrap opens in the taskbar, but it does not OPEN. Any help?

2

Try this. Go into the program folder for Bootstrap Studio, you will have to show hidden folders to see AppData directory. You can do this on the View tab in the Windows files explorer and check Hidden Items.

“C:\Users\YourAccount\AppData\Local\Programs\bstudio\Bootstrap Studio.exe”

Right click “Bootstrap Studio.exe” and then click Troubleshoot Compatibly and try to set it to a previous versions of Windows.

Next try to launch Bootstrap Studio and see if it works.

3

hello, thanks but it doesn’t work in any of the compatibility ways.

4

Try reinstalling it and see if that does it, usually that’s the first thing to try. :slight_smile:

5

I have the same problem on windows 10. Hover on the bootstrap studio icon in the taskbar and wait for it to maximize a bit above, and then right click on it and select maximize.

6

The problem is solvable as mihaipetrus658 wrote.
This problem is also observed when the bootstrapstudio has been started on a different display than the main one, and then that display is missing on the next start.

7

I have the same issue, probably due to removing one of my screens. Reinstalling or adding a new second screen hasn’t worked. It functioned properly before, so compatibility isn’t the problem. Now, I’m unable to move the window at all. I am stuck. Cannot access the application.

8

I know this is crazy, but if you install a program called AutoIT v3 (only available for windows)

After installing, create a new script on your desktop

Use WinMove("Bootstrap Studio", "", 0, 0) then run it using F5 or save and right click script then run script x64

This is how I’ve been able to get the screen back into my main monitor

Edit: This will only work if you run Bootstrap Studio and not open a .BSDesign file because it’s looking for the Window name.

You can also right click and compile it to an exe and uninstall AutoIT once your done, and just run the exe if you continue experiencing the issue. (Which you will, because I’ve had to keep it as an exe)