Stand-alone app fails on some Windows 11 computers

[Wenjie Wu]

feedback from users:

Open standalone executable MicroBlocks(1.2.5) on the following computer then it will exit(collapse) immediately.

‌ The same software works well on this computer

‌ MicroBlocks also runs fine on a Windows 11 computer at Citilab, so this problem may stem from system settings, virus control software, a corrupted download, or some other issue specific to the user who reported this. Need more data to determine if this is a MicroBlocks problem and, if so, what. ‌

[John Maloney]

Thanks for reporting this. The questions is, why is it failing?

The computer that it fails on is Windows 11. I have not tested MicroBlocks on Windows 11, but I have gotten reports that it works on Windows 11 computers.

Can you think of what might be making it fail on this particular Windows 11 computer? That computer has an AMD processor -- do think that matters? Or perhaps it has different security settings that don't allow unsigned applications to run? Is there any sort of error log that might offer some clues?

As a work-around, you could suggest that the user use MicroBlocks in a Chrome or Edge browser.

Thanks!

[Wenjie Wu]

As a work-around, you could suggest that the user use MicroBlocks in a Chrome or Edge browser.

I have given this suggestion.

I have no further information at the moment, I will post here once more information is gathered.

‌

[John Maloney]

I thought of something else to try. Could you ask the user to try running the MicroBlocks Windows app from the Pilot release (1.2.28)?

https://microblocks.fun/downloads/pilot/packages/microBlocks%20setup.exe

I recently made a change to the GP virtual machine to fix a font issue and, in the process, I also statically linked a library that it depends on. There is a chance that linking that library will fix the problem.

If MicroBlocks still crashes and the user is comfortable typing geeky commands to the terminal, you might ask them to get a list of library dependencies by opening a Terminal and running:

objdump -p ublocks-win.exe | grep DLL

I'm not sure where Windows puts the .exe file. Do you know? If need be, that file can be downloaded and unzipped from:

https://microblocks.fun/downloads/pilot/standalone/ublocks-win.zip

I'm not sure if that will tell us anything useful, but it is worth a try if the user is willing.

But perhaps the 1.2.28 version will work for them...

[Wenjie Wu]

Thank you for writing such a detailed guide, I will try to use this guide to communicate further with them.

[Wenjie Wu]

Synchronize user test information:

I thought of something else to try. Could you ask the user to try running the MicroBlocks Windows app from the Pilot release (1.2.28)?

The same problem as the previous one: can't open, it may not be an error caused by this reason.

you might ask them to get a list of library dependencies by opening a Terminal and running:

This is too difficult for users, no further testing

‌

[John Maloney]

I'm sorry that the 1.2.28 IDE did not help.

I understand about not asking the user to do complex debugging.

Another possible explanation involves security settings. It could be that Windows 11 has a setting like MacOS that only allows signed apps to be run. We are not currently signing the Windows app. But the signing process is complex and requires a signing certificate so I don't want to deal with that unless it is necessary -- and it isn't clear that signing the app would solve this problem.

For now, we can suggest that this user and other Windows 11 users who encounter this issue to use MicroBlocks in the Edge or Chrome Browser.

Meanwhile, we can collect more information about this problem. Ideally, we'll be able to reproduce it ourselves or find a technically inclined user who can help us by doing some experiments. Someone at Citilab mentioned running MicroBlocks on Windows 11. I may be able to get them to help with some experiments.

[John Maloney]

I did a bit of Googling and it looks like there are other apps that do not open on Windows 11. Here's one troubleshooting guide:

https://softwarekeep.com/help-center/fix-problems-with-apps-from-microsoft-store

[Dariusz Dorożalski]

You may try few steps:

1. "Run as admin" from context menu

2. Run ublocks from command prompt (Win+<R> cmd <Enter>) there may be detailed description of the problem (I/O permission, missing files...)

c:\work\tmp>ublocks-win.exe
SDL2 headers: 2.0.12; lib: 2.0.12
Goodbye!

3. Let OS to run app compatibility mode wizard (context menu)

As a last resort, there are Win11 Dev VMs available: https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/. 21GB from an overseas server, so for my location, it takes a few hours to complete the download.

[John Maloney]

Thanks for these suggestions.

José from Citilab just tested on a Windows 11 machine. Both the stable and pilot release versions of the MicroBlocks standalone app worked for him.

[John Maloney]

Note: Cannot reproduce on other Windows 11 computers, so it could be depend on settings, anti-virus software, or other variables.

[Wenjie Wu]

Thank you for your advice!

I may have access to these problematic computers in a few days, once I get a chance to try it, I'll try to gather more information and feedback here.

[John Maloney]

That would be great. Thank you!

[Wenjie Wu]

I may have access to these problematic computers in a few days, once I get a chance to try it, I'll try to gather more information and feedback here.

‌

@John Maloney I met with the users today and located the problem!

Problem occurs when MicroBlocks stand-alone app is in Chinese directory. Just rename the directory to English and it will work well.

‌

[Wenjie Wu]

By the way, a user reported a new problem:

Duplicate a block, then can't put it at the end of the script.

‌

[John Maloney]

Thanks for figuring out the problem. A work-around might be to use the Windows installer to install MicroBlocks. I think should install MicroBlocks in "Program Files", which might avoid the issue of Chinese characters in the file path.

Marking this closed but feel free to reopen if needed.