Files Panel looks strange and path line is searching

Hello, I just installed Matlab R2025b

Its takes about 55 sec to open (bare Matlab, no addons), which is pretty long.

After opening there is a rotating "search ring" in the path at the upper line and no files in the File Panel. The searching ring runs forever. Also "open" button is not working, as no folder explorer appears. Please have a look in the enclosed picture. After reinstall the problem remains. Does Matlab needs any permissions? How to grant them under Windows10?

[Stephen23]

Do you have OneDrive or DropBox or similar synchronised folders?

[Dmytro]

no, I don't. Before Installation of the R2025b, I uninstalled R2023a. Maybe there is some conflict with licence file-

[Torsten]

Does your computer meet the system requirements for R2025b listed here

https://uk.mathworks.com/support/requirements/matlab-system-requirements.html

?

[Dmytro]

Yes, I have Intel i7-6700HQ, 32 Gb Ram

[Torsten]

If you can't find the reason for failure, you should contact MATLAB support:

https://uk.mathworks.com/support/contact_us.html

Answer 1

[Oliver Jaehrig]

What exact operating system do you use? I mean which Windows 10 build?

[Dmytro]

[Oliver Jaehrig]

@Dmytro This seems to explain it. We are aware of similar issues when using unsupported Windows 10/11 operating systems.

Your build shows that it is actually a LTSC build from 2018. The system requirements show that you would need:

https://mathworks.com/support/requirements/matlab-system-requirements.html

Windows 11 (version 23H2 or higher)

Windows 10 (version 22H2)

I recommend to upgrade your Windows 10 build where MATLAB would work as expected.

Here you can find a table with all Windows 10 builds where you can also find 1809:

https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update)

[Dmytro]

Dear Oliver, this could explain, but it is strange, as I worked with R2023a for few years and here I have only the basic bare Matlab

[Oliver Jaehrig]

@Dmytro It can happen, that releases actually work on unsupported operating system, but it simply means this setup was never tested internally and not verified, so if anything unexpected behavior occurs, support can be very limitted.

I was involved in investigating similar issues which we started to see in R2025a (and newer) and as far as I know, all of these are occuring on unsupported Windows OS builds.

If you can reproduce this when using a supported OS, please contact our Technical Support department for further investigation.