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

[Jan Gruuthuse]

Keep notes on paper what you do.
When you got this working again: please post a summary.

[AQUAR]

Maybe looking at the checks to pass certification might give clues.

[Faiakes]

Tried version 23rd May...issue remains. 

Both Avidemux and qBittorrent (which also shares a similar problem with some of its options) are based on the Qt toolkit.
Is it something in the toolkit that needs updating to be compatible with Win10?

[Jan Gruuthuse]

nothing Avidemux can do: It is something local on your computer conflict, ...

[AQUAR]

@ Faiakes,

As I pointed out before - its quite possible that windows 10 handles API's more strictly for security reasons.
The compilers (including QT) will eventually catch up with these "features".

Meanwhile, can always keep exploring possibilities.

Avidemux executables are going to be at the mercy of these build processes.

My advice, don't run programs you need on the bleeding edge (not even avidemux itself!) unless you are willing to put up with instabilities.

[Faiakes]

@ Faiakes,
As I pointed out before - its quite possible that windows 10 handles API's more strictly for security reasons.
The compilers (including QT) will eventually catch up with these "features".
Meanwhile, can always keep exploring possibilities.
Avidemux executables are going to be at the mercy of these build processes.
My advice, don't run programs you need on the bleeding edge (not even avidemux itself!) unless you are willing to put up with instabilities.

Well for the time being, I will be switching to the Administator account.

Perhaps the development team should track and publish which Win10 builds works fully with.

I think it was fine up to build 14295 (10.0.14295.1005 ) - https://en.wikipedia.org/wiki/Windows_10_version_history

[AQUAR]

I don't think the ADM development team should or would track OS versions for compatibility.

As I said, eventually the open source contributors that work on compilers will catch up with OS developments.
That aspect is totally beyond the control of ADM developers as they are simply an enduser of these compilers  (just like we are just endusers of avidemux).

About the next post:
I am sure that a tracking log would be appreciated by windows 10 users.
Lets keep the log as the last entry in this thread so that it becomes easy to page and check if there is any change.

[Faiakes]

OK, I'll maintain a log here then.

Windows 10 build 13452 + Avidemux 28th May 2016 --> Issue remains

[Norbert]

Avidemux 2.6.12 64-bit is running on my Windows 10 system, with both File Open and Save dialogs.
I just performed an upgrade from Win 8.1 to Win 10, then installed Avidemux on a new directory (C/projects/avidemux).
Tested a short re-encode H.264 mp4 file with delogo filter, everything worked perfectly.

[Faiakes]

Avidemux 2.6.12 64-bit is running on my Windows 10 system, with both File Open and Save dialogs.
I just performed an upgrade from Win 8.1 to Win 10, then installed Avidemux on a new directory (C/projects/avidemux).
Tested a short re-encode H.264 mp4 file with delogo filter, everything worked perfectly.

Hi

Which build are you running?

[Norbert]

Win 10 Pro Ver 1511 Build 10586.318

[Faiakes]

Win 10 Pro Ver 1511 Build 10586.318

Yes, build 10586 was fine for me as well.

[Faiakes]

Hmmm, I seem to be narrowing down the issue.

I was forced to do a 'refresh' of my windows 10 installation and Avidemux was working as expected.

It would appear that my habit of disabling the the 'Open File - Security Warning' is related to it.
As soon as I applied the usual tweaks, the issue returned (and it would not go away even after I reverted said tweaks).

The tweaks are:
1) http://www.door2windows.com/disable-open-file-security-warning-message/
2) But more likely this:  http://www.sevenforums.com/tutorials/182353-open-file-security-warning-enable-disable.html
(Option 3)
It seems to have to do with the 'Attachment Manager'.
Now, I know this was a Windows 7 tweak, but it works either way.

I did make a system image this time, so I was able to restore my settings and all is well now.


EDIT: I booted up this morning and the issue has returned...I give up.

[Faiakes]

Win10, x64, build 14361 + Avidemux 30 May 2016 --> issue remains.

[Faiakes]

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