Windows 10 - no Open File/Save dialog [Solved]

[Faiakes]

Win10, x64, build 14367 + Avidemux 15th June 2016 --> Issue remains.

[Jan Gruuthuse]

Most likely the issue can't / won't be solved by avidemux developer(s). The developer(s) don't have access to your computer or can't reproduce your specific situation.
Consider installing Linux alongside your windows (2nd hardrive, dual boot), seek expert help doing so, If you never done this before. UEFI bios = possible risk of loosing your windows installation

[Faiakes]

Most likely the issue can't / won't be solved by avidemux developer(s). The developer(s) don't have access to your computer or can't reproduce your specific situation.
Consider installing Linux alongside your windows (2nd hardrive, dual boot), seek expert help doing so, If you never done this before. UEFI bios = possible risk of loosing your windows installation

The issue is solved by using the built-in Admin account, so Linux is not necessary.

The issue resides somewhere between the standard Windows 10 Admin account and a standard Windows 10 Local account.

[AQUAR]

I don't mind the updates that the issue remains/resolves with the latest combinations of win10 and adm2.6.
It might be of interest to these win10 users when/if the issue disappears or if a policy tweak is found to work around it.

[mean]

It will be probably an update of Qt5 that will fix the problem if it stays there

[Faiakes]

Win10, x64, build 14367 + Avidemux 21st June 2016 --> Issue remains.

[Faiakes]

Win10, x64, build 14367 + Avidemux 24th June 2016 --> Issue remains.

[Faiakes]

Win10, x64, build 14371 + Avidemux 24th June 2016 --> Issue remains.

[Faiakes]

Win10, x64, build 14371 + Avidemux 25th June 2016 --> Issue remains.

[Faiakes]

Win10, x64, build 14372 + Avidemux 25th June 2016 --> Issue remains.

[Faiakes]

Win10, x64, build 14376 + Avidemux 26th June 2016 --> Issue remains.

[Faiakes]

Win10, x64, build 14376 + Avidemux 30th June 2016 --> Issue remains.

[Faiakes]

Win10, x64, build 14379 + Avidemux 30th June 2016 -->       Issue resolved!!!

(At least for the time being...)

[AQUAR]

I wonder if this was due to an updated compiler being used to build avidemux?
From your combination this does not seem to be the case, instead it looks like a resolution to a "bug issue" with windows 10.

Interesting, do let us know if the situation reverses again. 

[mean]

nothing was done here