ED built on Win11 25H2 26200.9445 crashes File Manager

[Bespoken]

Just built an ED with Win 25H2 26200.9445 on 2 laptops. The File Manager, from the Tools menu, does not start. This was not tested when V5.9.2.2 was installed with the previous version of Windows (August 11 or 27 preview update), but was working with V5.9.2.0.

[admin]

Just built an ED with Win 25H2 26200.9445 on 2 laptops. The File Manager, from the Tools menu, does not start. This was not tested when V5.9.2.2 was installed with the previous version of Windows (August 11 or 27 preview update), but was working with V5.9.2.0.

Thanks for reporting the issue. Weird, we haven't made any changes to the File Manager recently. We'll try to reproduce it and fix the problem as soon as possible.

[admin]

Just built an ED with Win 25H2 26200.9445 on 2 laptops. The File Manager, from the Tools menu, does not start. This was not tested when V5.9.2.2 was installed with the previous version of Windows (August 11 or 27 preview update), but was working with V5.9.2.0.

Thanks for reporting the issue. Weird, we haven't made any changes to the File Manager recently. We'll try to reproduce it and fix the problem as soon as possible.

Testing confirms that in Windows 11 25H2 (build 26200.9445), in a WinPE environment created via WinRE, the program crashes whenever it calls the SHGetFileInfo API. The WinRE images Microsoft has recently shipped are consistently problematic. Yet another “masterpiece” from Microsoft.

Because SHGetFileInfo is called in multiple places in the program, it is not possible to work around the problem by modifying the code, and the only option is to wait for Microsoft to fix it.

[al3x]

Hi,

I moved the post to its own thread.

Not that helpful maybe, but in the meantime you can open Notepad from the command prompt and use its file open menu to navigate around instead. It’s not that helpful because you can only select 1 file in that menu, and you need to change the filter to *.* to see all files, but it kinda works for now.

Hopefully MS will fix that soon, their lack of testing is just unbelievable…

[admin]

@al3x, thanks for organizing the thread and sharing the workaround.

Is Microsoft using AI to write code or package programs now? There have been far too many problems lately.

[Bespoken]

No change to the File Manager failing with the Sept 14 OBE KB5129195.

[admin]

@Bespoken,

Thanks for continuing to follow up and confirming that the issue still persists after the Sept 14 OBE KB5129195 update.

If Microsoft ultimately does not fix this issue, it will indeed be a major problem for us, because SHGetFileInfo is called in multiple places in the program and cannot be bypassed by modifying the code. This means that until Microsoft fixes it, File Manager will be unavailable in the WinPE environment.

Best regards,

[admin]

We spent some time replacing the SHGetFileInfo API with other APIs and fixing some other issues, and finally got FileExplorer working on this version. Although it doesn’t perform as well as directly calling SHGetFileInfo, at least it’s usable now. Here is the download link:
https://www.easyuefi.com/backup-software...plorer.zip

After unzipping, please replace the corresponding files in the bin\WINPE\Program Files\FileExplorer folder under the installation directory.

To be honest, we didn’t want to spend time fixing this kind of WinPE bug (cleaning up Microsoft’s mess), because we have more important things to do.

[Bespoken]

Thanks @Admin. Confirmed that the replacement works on my PC's, and the performance appears to be fine.

The response to this Microsoft bug in WinPE is another great example of the commitment and support by the Hasleo team to their products. Well done!

[admin]

@Bespoken, thanks for the confirmation and kind words! Really appreciate it.

The problem now is that if the WinPE-related functionality returns to normal someday, we should switch back to the old version. However, we don’t have time to keep monitoring it all the time.