Hi
For some weird reason, no matter which version I use (latest is May 1) I cannot use the Open File function.
I can Drag & Drop a file but once I decide what to edit, it won't save either.
I have tried both .exe and portable versions.
I am on Windows 10 - build 14316.
--------------------------------------------------------------------------------
This issue has been resolved since build 14379
------------------------------------------------------------------------------------------------
Log:
Win10, x64, build 14379 + Avidemux 30th June 2016 --> Issue resolved
Win10, x64, build 14379 + Avidemux 02nd July 2016 --> Issue resolved
Win10, x64, build 14379 + Avidemux 04th July 2016 --> Issue resolved
Win10, x64, build 14379 + Avidemux 05th July 2016 --> Issue resolved
Win10, x64, build 14379 + Avidemux 06th July 2016 --> Issue resolved
Win10, x64, build 14379 + Avidemux 07th July 2016 --> Issue resolved
Win10, x64, build 14383 + Avidemux 07th July 2016 --> Issue resolved
Win10, x64, build 14385 + Avidemux 07th July 2016 --> Issue resolved
Win10, x64, build 14385 + Avidemux 12th July 2016 --> Issue resolved
Win10, x64, build 14388 + Avidemux 13th July 2016 --> Issue resolved
Win10, x64, build 14393 + Avidemux 17th July 2016 --> Issue resolved
Win10, x64, build 14393 + Avidemux 22nd July 2016 --> Issue resolved
Win10, x64, build 14393 + Avidemux 25th July 2016 --> Issue resolved
Win10, x64, build 14393 + Avidemux 26th July 2016 --> Issue resolved
Win10, x64, build 14393 + Avidemux 28th July 2016 --> Issue resolved
Win10, x64, build 14393 + Avidemux 29th July 2016 --> Issue resolved
Win10, x64, build 14393 + Avidemux 30th July 2016 --> Issue resolved
Win10, x64, build 14393 + Avidemux 03rd August 2016 --> Issue resolved
Win10, x64, build 14393 + Avidemux 06th August 2016 --> Issue resolved
Win10, x64, build 14393 + Avidemux 13th August 2016 --> Issue resolved
Win10, x64, build 14901 + Avidemux 13th August 2016 --> Issue resolved
Win10, x64, build 14901 + Avidemux 17th August 2016 --> Issue resolved
Win10, x64, build 14905 + Avidemux 18th August 2016 --> Issue resolved
Win10, x64, build 14905 + Avidemux 21st August 2016 --> Issue resolved
Win10, x64, build 14905 + Avidemux 23rd August 2016 --> Issue resolved
Win10, x64, build 14905 + Avidemux 24th August 2016 --> Issue resolved
Win10, x64, build 14905 + Avidemux 01st September 2016 --> Issue resolved
Win10, x64, build 14915 + Avidemux 01st September 2016 --> Issue resolved
Win10, x64, build 14915 + Avidemux 04th September 2016 --> Issue resolved
Win10, x64, build 14915 + Avidemux 05th September 2016 --> Issue resolved
Win10, x64, build 14915 + Avidemux 06th September 2016 --> Issue resolved
Win10, x64, build 14915 + Avidemux 08th September 2016 --> Issue resolved
Win10, x64, build 14915 + Avidemux 09th September 2016 --> Issue resolved
Win10, x64, build 14926 + Avidemux 09th September 2016 --> Issue resolved
Win10, x64, build 14926 + Avidemux 15th September 2016 --> Issue resolved
Win10, x64, build 14926 + Avidemux 16th September 2016 --> Issue resolved
Win10, x64, build 14926 + Avidemux 22nd September 2016 --> Issue resolved
Win10, x64, build 14931 + Avidemux 22nd September 2016 --> Issue resolved
Win10, x64, build 14931 + Avidemux 26th September 2016 --> Issue resolved
Win10, x64, build 14931 + Avidemux 27th September 2016 --> Issue resolved
Win10, x64, build 14936 + Avidemux 28th September 2016 --> Issue resolved
Win10, x64, build 14936 + Avidemux 04th October 2016 --> Issue resolved
Win10, x64, build 14936 + Avidemux 07th October 2016 --> Issue resolved
Win10, x64, build 14942 + Avidemux 07th October 2016 --> Issue resolved
Win10, x64, build 14942 + Avidemux 12th October 2016 --> Issue resolved
Win10, x64, build 14946 + Avidemux 15th October 2016 --> Issue resolved
Win10, x64, build 14946 + Avidemux 16th October 2016 --> Issue resolved
Win10, x64, build 14946 + Avidemux 19th October 2016 --> Issue resolved
Win10, x64, build 14946 + Avidemux 22th October 2016 --> Issue resolved
Win10, x64, build 14951 + Avidemux 22th October 2016 --> Issue resolved
Win10, x64, build 14951 + Avidemux 24th October 2016 --> Issue resolved
Win10, x64, build 14955 + Avidemux 24th October 2016 --> Issue resolved
Win10, x64, build 14955 + Avidemux 31st October 2016 --> Issue resolved
Win10, x64, build 14955 + Avidemux 04th November 2016 --> Issue resolved
Win10, x64, build 14955 + Avidemux 05th November 2016 --> Issue resolved
Win10, x64, build 14955 + Avidemux 06th November 2016 --> Issue resolved
Win10, x64, build 14955 + Avidemux 07th November 2016 --> Issue resolved
Win10, x64, build 14955 + Avidemux 13th November 2016 --> Issue resolved
Win10, x64, build 14955 + Avidemux 14th November 2016 --> Issue resolved
Win10, x64, build 14955 + Avidemux 15th November 2016 --> Issue resolved
Win10, x64, build 14955 + Avidemux 17th November 2016 --> Issue resolved
Win10, x64, build 14955 + Avidemux 20th November 2016 --> Issue resolved
Win10, x64, build 14955 + Avidemux 21st November 2016 --> Issue resolved
Win10, x64, build 14955 + Avidemux 24th November 2016 --> Issue resolved
Win10, x64, build 14955 + Avidemux 03rd December 2016 --> Issue resolved
Win10, x64, build 14955 + Avidemux 12th December 2016 --> Issue resolved
Win10, x64, build 14955 + Avidemux 13th December 2016 --> Issue resolved
Win10, x64, build 14955 + Avidemux 17th December 2016 --> Issue resolved
Win10, x64, build 14986 + Avidemux 17th December 2016 --> Issue resolved
Win10, x64, build 14986 + Avidemux 26th December 2016 --> Issue resolved
Win10, x64, build 14986 + Avidemux 30th December 2016 --> Issue resolved
Win10, x64, build 14986 + Avidemux 05th January 2017 --> Issue resolved
Win10, x64, build 14986 + Avidemux 11th January 2017 --> Issue resolved
Win10, x64, build 14986 + Avidemux 12th January 2017 --> Issue resolved
Win10, x64, build 15002 + Avidemux 13th January 2017 --> Issue resolved
Win10, x64, build 15007 + Avidemux 13th January 2017 --> Issue resolved
Win10, x64, build 15007 + Avidemux 16th January 2017 --> Issue resolved
Win10, x64, build 15007 + Avidemux 17th January 2017 --> Issue resolved
Win10, x64, build 15007 + Avidemux 19th January 2017 --> Issue resolved
Win10, x64, build 15025 + Avidemux 02nd February 2017 --> Issue resolved
Win10, x64, build 15031 + Avidemux 06th February 2017 --> Issue resolved
Win10, x64, build 15031 + Avidemux 10th February 2017 --> Issue resolved
Win10, x64, build 15031 + Avidemux 12th February 2017 --> Issue resolved
Win10, x64, build 15031 + Avidemux 21st February 2017 --> Issue resolved
Win10, x64, build 15031 + Avidemux 22nd February 2017 --> Issue resolved
Win10, x64, build 15048 + Avidemux 27th February 2017 --> Issue resolved
Win10, x64, build 15048 + Avidemux 04th March 2017 --> Issue resolved
Win10, x64, build 15055 + Avidemux 14th March 2017 --> Issue resolved
Win10, x64, build 15060 + Avidemux 14th March 2017 --> Issue resolved
Win10, x64, build 15060 + Avidemux 19th March 2017 --> Issue resolved
Win10, x64, build 15060 + Avidemux 20th March 2017 --> Issue resolved
Win10, x64, build 15063 + Avidemux 23rd March 2017 --> Issue resolved
Win10, x64, build 15063 + Avidemux 28th March 2017 --> Issue resolved
Win10, x64, build 15063 + Avidemux 30th March 2017 --> Issue resolved
Win10, x64, build 15063 + Avidemux 07th April 2017 --> Issue resolved
Win10, x64, build 16170 + Avidemux 12th April 2017 --> Issue resolved
Win10, x64, build 16170 + Avidemux 13th April 2017 --> Issue resolved
Win10, x64, build 16176 + Avidemux 19th April 2017 --> Issue resolved
Win10, x64, build 16176 + Avidemux 20th April 2017 --> Issue resolved
Win10, x64, build 16179 + Avidemux 20th April 2017 --> Issue resolved
Win10, x64, build 16179 + Avidemux 25th April 2017 --> Issue resolved
Win10, x64, build 16184 + Avidemux 29th April 2017 --> Issue resolved
Win10, x64, build 16184 + Avidemux 01st May 2017 --> Issue resolved
Win10, x64, build 16193 + Avidemux 09th May 2017 --> Issue resolved
Win10, x64, build 16193 + Avidemux 17th May 2017 --> Issue resolved
Win10, x64, build 16193 + Avidemux 25th May 2017 --> Issue resolved
Win10, x64, build 16193 + Avidemux 29th May 2017 --> Issue resolved
Win10, x64, build 16193 + Avidemux 01st June 2017 --> Issue resolved
Win10, x64, build 16193 + Avidemux 03rd June 2017 --> Issue resolved
Win10, x64, build 16193 + Avidemux 05th June 2017 --> Issue resolved
Win10, x64, build 16193 + Avidemux 07th June 2017 --> Issue resolved
Win10, x64, build 16193 + Avidemux 14th June 2017 --> Issue resolved
Win10, x64, build 16193 + Avidemux 15th June 2017 --> Issue resolved
Win10, x64, build 16199 + Avidemux 18th June 2017 --> Issue resolved
Win10, x64, build 16199 + Avidemux 23th June 2017 --> Issue resolved
Win10, x64, build 16199 + Avidemux 27th June 2017 --> Issue resolved
Win10, x64, build 16199 + Avidemux 28th June 2017 --> Issue resolved
Win10, x64, build 16199 + Avidemux 07th July 2017 --> Issue resolved
Win10, x64, build 16241 + Avidemux 23rd July 2017 --> Issue resolved
Win10, x64, build 16241 + Avidemux 26th July 2017 --> Issue resolved
Win10, x64, build 16257 + Avidemux 26th July 2017 --> Issue resolved
Win10, x64, build 16257 + Avidemux 03rd September 2017 --> Issue resolved
Win10, x64, build 16257 + Avidemux 07th September 2017 --> Issue resolved
Win10, x64, build 16296 + Avidemux 23rd October 2017 --> Issue resolved
Win10, x64, build 16299 + Avidemux 27th October 2017 --> Issue resolved
Win10, x64, build 16299 + Avidemux 31st October 2017 --> Issue resolved
Win10, x64, build 16299 + Avidemux 05th Novemeber 2017 --> Issue resolved
Win10, x64, build 16299 + Avidemux 14th Novemeber 2017 --> Issue resolved
Win10, x64, build 16299 + Avidemux 27th Novemeber 2017 --> Issue resolved
Win10, x64, build 16299 + Avidemux 29th Novemeber 2017 --> Issue resolved
Win10, x64, build 16299 + Avidemux 05th December 2017 --> Issue resolved
Win10, x64, build 16299 + Avidemux 12th December 2017 --> Issue resolved
Win10, x64, build 16299 + Avidemux 15th December 2017 --> Issue resolved
Win10, x64, build 16299 + Avidemux 27th December 2017 --> Issue resolved
Win10, x64, build 16299 + Avidemux 01st January 2018 --> Issue resolved
Win10, x64, build 16299 + Avidemux 05th January 2018 --> Issue resolved
Win10, x64, build 16299 + Avidemux 07th January 2018 --> Issue resolved
Win10, x64, build 16299 + Avidemux 13th January 2018 --> Issue resolved
Win10, x64, build 16299 + Avidemux 14th January 2018 --> Issue resolved
Win10, x64, build 16299 + Avidemux 20th January 2018 --> Issue resolved
Win10, x64, build 16299 + Avidemux 21st January 2018 --> Issue resolved
Win10, x64, build 16299 + Avidemux 23rd January 2018 --> Issue resolved
Win10, x64, build 17083 + Avidemux 08th February 2018 --> Issue resolved
Win10, x64, build 17093 + Avidemux 08th February 2018 --> Issue resolved
Win10, x64, build 17101 + Avidemux 08th February 2018 --> Issue resolved
Win10, x64, build 17101 + Avidemux 16th February 2018 --> Issue resolved
Win10, x64, build 17101 + Avidemux 22nd February 2018 --> Issue resolved
Win10, x64, build 17112 + Avidemux 28th February 2018 --> Issue resolved
Win10, x64, build 17123 + Avidemux 19th February 2018 --> Issue resolved
Win10, x64, build 17133 + Avidemux 05th April 2018 --> Issue resolved
Win10, x64, build 17134 + Avidemux 15th April 2018 --> Issue resolved
Win10, x64, build 17134 + Avidemux 17th April 2018 --> Issue resolved
Win10, x64, build 17666 + Avidemux 20th May 2018 --> Issue resolved
Win10, x64, build 17666 + Avidemux 04th June 2018 --> Issue resolved
Win10, x64, build 17666 + Avidemux 25th June 2018 --> Issue resolved
Win10, x64, build 17692 + Avidemux 02nd June 2018 --> Issue resolved
Win10, x64, build 17763 + Avidemux 01st Sept. 2018 --> Issue resolved
Win10, x64, build 18267 + Avidemux 26th Oct. 2018 --> Issue resolved
Win10, x64, build 18282 + Avidemux 28th Nov. 2018 --> Issue resolved
Win10, x64, build 18282 + Avidemux 30th Dec. 2018 --> Issue resolved
Win10, x64, build 18317 + Avidemux 18th Jan. 2019 --> Issue resolved
Win10, x64, build 18362 + Avidemux 2.7.3 2019 --> Issue resolved
Win10, x64, build 18362 + Avidemux 2.7.3 2019 22 Apr --> Issue resolved
Win10, x64, build 18362 + Avidemux 2.7.3 2019 27 Apr --> Issue resolved
Can you give more details about your windows 10 64-bit?
- Language of installed windows (standard English or other language?
- de-install avidemux and install again. Do a simple install, not a fancy (installing in some other location, ...)
- admin issues settings for the user that did install?
- ...
All I could think of, I don't have windows.
Are these dialogs missing or just not working?
If its just not working then its anyone's guess as to why the calling function fails.
If avidemux is set as the default program for specific video files will it open these files?
Eg ADM set as default to open .MKV - then double click on an .MKV file and will ADM load it?
Quote from: Jan Gruuthuse on May 03, 2016, 05:12:15 AM
Can you give more details about your windows 10 64-bit?
- Language of installed windows (standard English or other language?
- de-install avidemux and install again. Do a simple install, not a fancy (installing in some other location, ...)
- admin issues settings for the user that did install?
- ...
All I could think of, I don't have windows.
Hi
Thanks for the reply
Windows 10, 64bit, build 14328
Language: English
I am Admin
Un/reinstalled (64bit version) but problem persists.
Open File With - It works the same way draging a file works: the file will be loaded but once a clip has been selected, the Save button or menu do nothing.
Quote from: AQUAR on May 03, 2016, 11:54:34 AM
Are these dialogs missing or just not working?
Missing altogether...
It may happen if some files from older version of avidemux are still there
The simplest is to remove it completely and reinstall using the installer
see above.
Quote from: Faiakes on May 03, 2016, 05:31:09 PM
>8 >8
I am Admin >8 >8
You are running as user and did install as this running user? Depending how you install software, parts could end up in none intended places?
Try installing disconnected from network (pull cable) / internet (switch off Wifi)
with disabled AV,
Anti
Virus perhaps blocking some installation?
Don't disable AV whilst connected to network/internet
ps.:
recalling memories from ages ago.Try 3rd May 2016 build: http://www.avidemux.org/nightly/win64/
Copy all the files from the nightly in a newly created folder.
In that folder - rename avidemux.exe to avidemux_portable.exe.
Then double click on the avidemux_portable.exe to run the program as a portable version.
This way we can check if there are clashes with files from previous install's viz:
if all now works its a clash with older files, if the same issue crops up its probably something else.
Quote from: AQUAR on May 04, 2016, 09:24:31 AM
Copy all the files from the nightly in a newly created folder.
In that folder - rename avidemux.exe to avidemux_portable.exe.
Then double click on the avidemux_portable.exe to run the program as a portable version.
This way we can check if there are clashes with files from previous install's viz:
if all now works its a clash with older files, if the same issue crops up its probably something else.
Tried... the issue remains.
Apart form AppData is there another folder where Avidemux portable saves settings/profile/anything?
Note: I only use the portable version. I only installed the regular version to test the issue and uninstalled when I saw there wasn't a difference.
Quote from: Jan Gruuthuse on May 04, 2016, 04:20:00 AM
see above.
Quote from: Faiakes on May 03, 2016, 05:31:09 PM
>8 >8
I am Admin >8 >8
You are running as user and did install as this running user? Depending how you install software, parts could end up in none intended places?
Try installing disconnected from network (pull cable) / internet (switch off Wifi) with disabled AV, Anti Virus perhaps blocking some installation?
Don't disable AV whilst connected to network/internet
ps.: recalling memories from ages ago.
Try 3rd May 2016 build: http://www.avidemux.org/nightly/win64/
I use Malwarebytes Free version, so it's not running real-time.
Windows Defender is turned off.
I'm not certain if some part of Malwarebytes Free version would still be active?
If you have access to a second windows computer where you could test avidemux?
Could be just your computer, or some regional windows issue?
Hard to tell what is exactly going on ...
Quote from: Jan Gruuthuse on May 05, 2016, 05:13:24 AM
I'm not certain if some part of Malwarebytes Free version would still be active?
If you have access to a second windows computer where you could test avidemux?
Could be just your computer, or some regional windows issue?
Hard to tell what is exactly going on ...
I have tested the portable version on my work laptop (Win7 64bit) and it works fine.
Windows 10 issue? Computer issue?
- via windows 10 software remove installed avidemux installations
- next with file browser
-- search option include hidden files/ system folders
-- search for avidemux*
-- remove all remaining found avidemux* on your system drive
-- see if you then get a portable avidemux working (see AQUAR posting: regarding avidemux_portable.exe (http://avidemux.org/smif/index.php/topic,16753.msg74722.html#msg74722))
AFAIK the portable version of ADM has its operational parameters contained to the folder where ADM is located.
Really nothing much we can do to resolve a localised windows 10 issue here.
Just some suggestions:
. Verify the windows installation by running the system file checker program.
. Do system scans with anti malware programs (check out the bleeping computer web site!).
. Do a restricted startup by disabling all user startup programs (using MSCONFIG).
Throughout these efforts keep trying the portable ADM.
Portable & normal are the same
The ONLY difference is from where they load the plugins/config file
Quote from: AQUAR on May 06, 2016, 12:09:55 PM
AFAIK the portable version of ADM has its operational parameters contained to the folder where ADM is located.
Really nothing much we can do to resolve a localised windows 10 issue here.
Just some suggestions:
. Verify the windows installation by running the system file checker program.
. Do system scans with anti malware programs (check out the bleeping computer web site!).
. Do a restricted startup by disabling all user startup programs (using MSCONFIG).
Throughout these efforts keep trying the portable ADM.
Hi
I run sfc /scan, and DISM /CheckHealth, both reported no issues.
Tried Safe Mode, still no luck.
I just did a clean install of Win10 64 build 14332, disabled Windows Defender, no AV installed and STILL no luck (and this is with the portable version!!!)
What's going on?!?
Is it just me?
EDIT: I do get this when I try to run gpedit.msc (this is on the new clean install)
(https://avidemux.org/smif/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FSfMIp9t.png&hash=13670cb5b2a6050d472c38306d8f778e1b5b0e29)
sometime something went wrong.
Administrative Templates: network administrators control
You're on an Enterprise Windows 10?: contact your admin our search google for WinMaps.admx and your Windows version
That template is to set automated updating of maps.
Doesn't seem to have any bearing on this issue with "avidemux on the OPs copy of win10".
"Group Policy Editor" (gpedit.msc) (can allow/disallow plenty what a user can/can't do)
Most likely you need to download Group Policy Editor updated templates ...
Looks like you done something more then the average windows user.
I think this is a tangent to the issue of not seeing the file dialogs in avidemux.
But maybe the OP can tell us what policy item is targeted that might relate to the failure of these "inter program operations".
Hi
Thanks for all your replies.
I downloaded the new ISO for Win10 Pro 64 build 14332 and did a clean install.
I only noticed the above error when I tried to use gpedit.msc
I did so to disable the Open File Security dialogue and another little tweaks that I always do, and which have never affected avidemux before.
Do other people with windows 10 have the same issue?
Even weirder, this started half way through (not when I installed) build 14316 (I am on the Fast Insider ring)
You will have to wait until other end user "catch up" with progressions in windows 10.
If the OS continues to fail to respond to ADM's open file code then others will also soon start to report the issue.
Your issue could be reported back to Microsoft as that is the purpose of being in the fast insider ring.
Is there not some restriction in place, when writing to content on user Desktop?
OK here is some more info.
I tried to add ReShade (portable) to Fallout 4 and it's stupid UI would not work.
I gave up on it, only to realise the next day that just like Avidemux, it would not 'open' to add the Fallout.exe
Here is a link (http://www.mediafire.com/download/hd25q2558um47el/ReShade+2.0.3f1.7z) to that exact package.
So, in what way is the PreviewAssistant in ReShade similar to Avidemux?
EDIT: I have just opened an existing ticket (though there were no details) called File Open dialog.
If anyone else wants to follow it or chime in (I think you need the Feedback Hub app):
feedback-hub:?contextid=154&feedbackid=9051dfdd-9caa-4423-84a8-add3e3487765&form=1&src=2
Perhaps something changed (setting you made or windows function) not allowing running program calling another program? My guess
We should just see if that ticket bears fruit at some point.
IIRC the OP has this issue with a fresh install of the latest fast insider version of win 10.
Its probably an OS issue and outside the realm of avidemux.
May I urge people with Win10 machines to upvote the issue?
feedback-hub:?contextid=154&feedbackid=9051dfdd-9caa-4423-84a8-add3e3487765&form=1&src=2
Otherwise we'll never get an answer.
I would think that most avidemux/windows users are not on windows 10.
And those that are would probably not be using the fast insider releases.
Avidemux enthusiasts aren't going to be of much help to you on these types of issues.
Suspect it needs to become a mainstream issue before it can be "upvoted".
Well...thinking ahead? Start building some momentum?
I tested the 32 bit portable version April 16th, no difference
EDIT: I just run the Compatibility Wizard and it came back as: Program Incompatible
EDIT: Also found this: http://portableapps.com/node/50234
EDIT: Also found this: http://www.windows10forums.com/threads/portable-programs-in-windows-10.3216/
EDIT: I also tried to open the find IP filter button in qBittorrent and it doesn't work either. (Options > IP Filtering > ...)
EDIT: I opened a second ticket specifically for Avidemux: feedback-hub:?contextid=67&feedbackid=fb0e24a8-82de-4ba1-8140-cef48484e33d&form=1&src=2
The Microsoft Conglomerate would not allow free migration to windows 10 from windows 7 unless there is some kudos/payback in it for them.
The payback for them is that you, the end user, are slowly going to lose control over what the OS is meant to be used for.
Examples - meant for only approved programs, "spyware" for user profiling, cloud based subscription usage etc etc.
I refuse to downgrade to windows 10 from windows 7 (besides windows 7 is a better desktop OS).
And if window 7 becomes deprecated I'll migrate to Linux full time.
IMHO the OS is to serve my PC needs rather than being a vehicle for others to get to know me.
I do run win 10 in virtual box and don't mind the look and feel of it.
This issue smells to me like - Microsoft is telling you that "free - low budget" programs like avidemux are going to be in trouble.
Sometimes, you can't even install a second os like ubuntu on your desktop/laptop due to restrictions implemented by UEFI bios (Unified Extensible Firmware Interface) restrictions implemented by the producent.
Its why I always assemble my own PC from carefully selected parts.
No multi boot issues then with UEFI or BIOS.
Still prefer BIOS as its more familiar and also because I have no need for the features that UEFI brings.
IMHO Faiakes is on the bleeding edge of win 10 and that won't always be beneficial to the why/how you use your computer.
It will be interesting to see if this issue gets resolved.
Maybe try running avidemux with an super admin account (net user administrator /active:yes) and see if it works then.
Maybe try running avidemux in windows 7 compatibility mode.
Quote from: AQUAR on May 14, 2016, 12:42:54 PM
Maybe try running avidemux with an super admin account (net user administrator /active:yes) and see if it works then.
Maybe try running avidemux in windows 7 compatibility mode.
Is that with Win+R and then paste that command?
I have...Win7 nothing...Win8 nothing...even Vista....
I have checked permissions and Avidemux has full write access for all types of users.
No, its using the command prompt (with admin rights!) to set up the "admin plus" account.
After which you have to logout and log back into that "admin plus" account.
Never tried it myself - just something I read for getting install executable's on win10 to run when nothing else works (including the "normal admin" account!).
Thought it would be interesting to see if some permission issue exists but is allowed with such an account.
Quote from: AQUAR on May 15, 2016, 10:14:42 AM
No, its using the command prompt (with admin rights!) to set up the "admin plus" account.
After which you have to logout and log back into that "admin plus" account.
IT WORKS !!!So, what is the difference then between a local admin account and a 'super' admin account that Avidemux needs to overcome?
Microsoft taking control!!!!!!!!!!?
If it was me I'd investigate the beefed up "security" measures.
Purely speculative:
The implementation of the open file calling function is probably being hamstrung by win 10 for security reasons.
If that's the case the cross compiler used to build avidemux might catch up with any new requirements for that function (sooner or later).
Don't stay logged on as a super admin.
Can you make that setting by right clicking on the required executables? run as administrator?
@ Jan
I don't think that will work.
This super admin account is not a normal user defined admin account.
Only came across this "trick" on a site where they were discussing how to run installation binaries that fail to execute even with all administrative rights.
Windows 10 is a continually evolving OS and morphs by way of with forced updates for the typical home based user.
It seems to be going down the path of only running certified programs.
(Certified by Microsoft or by business doing self certification for their own programs).
There must a myriad of programs that windows 10 will eventually refuse to execute (maybe ADM will be one of them).
I despise any service that data mines or takes control on protective pretence (stupid users that need to be told what they need!).
Quote from: Jan Gruuthuse on May 16, 2016, 04:32:51 AM
Can you make that setting by right clicking on the required executables? run as administrator?
I already have done all that.
I even dived into permission and have taken complete control of the entire folder but not luck.
(https://avidemux.org/smif/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FQ5jEAsu.png&hash=4f814dc732d9048283f1a61d143968f2a9a9171d)
Is that not part of the problem having your programmes on D:\? I know in the past you could, done similar to save ssd ageing.
should you not update to avidemux Mai 8 2016? http://www.avidemux.org/nightly/win64/
Quote from: Jan Gruuthuse on May 16, 2016, 04:05:16 PM
Is that not part of the problem having your programmes on D:\? I know in the past you could, done similar to save ssd ageing.
should you not update to avidemux Mai 8 2016? http://www.avidemux.org/nightly/win64/
Thanks Jan
I did but more importantly it gave me an idea.
I run cmd with Admin Priviliges > secpol.msc > Local Policies > Security Options > User Account Control: Run All administrators in Admin Approval Mode > Disabled
(This may require Windows 10 Admin templates installed) I don't have to switch to super Admin to get Avidemux to work.
Avidemux works from both the C and the D drive.However, now my Start button does not work >:(
EDIT: That wasn't it. It was something else and after re-installing windows I have yet to replicate what I did.
Well, that narrows the issue down to the differences between win 10 UAC and win 7 UAC.
Start button not working is a common complaint on windows 10.
Just google on that and you will find lots of ideas on how to fix that.
Its been an interesting post that may well serve to help other ADM/win10 users .
I wasn't able to fix the start button so I reinstalled, and the above trick doesn't work.
It was something else I did and I can't figure out what >:( >:( >:(
Does the "super admin" still work?
Quote from: AQUAR on May 18, 2016, 01:39:43 PM
Does the "super admin" still work?
Yes, that still works.
I asked the head of IT at work for some tips.
I'll try a few more things out today.
Keep notes on paper what you do.
When you got this working again: please post a summary.
Maybe looking at the checks to pass certification might give clues.
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?
nothing Avidemux can do: It is something local on your computer conflict, ...
@ 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.
Quote from: AQUAR on May 26, 2016, 06:21:51 AM
@ 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 (https://en.wikipedia.org/wiki/Windows_10_version_history)
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.
OK, I'll maintain a log here then.
Windows 10 build 13452 + Avidemux 28th May 2016 --> Issue remains
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.
Quote from: Norbert on May 30, 2016, 12:18:31 PM
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?
Win 10 Pro Ver 1511 Build 10586.318
Quote from: Norbert on May 30, 2016, 12:31:13 PM
Win 10 Pro Ver 1511 Build 10586.318
Yes, build 10586 was fine for me as well.
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/ (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.
Win10, x64, build 14361 + Avidemux 30 May 2016 --> issue remains.
Win10, x64, build 14366 + Avidemux 15th June 2016 --> Issue remains.
Win10, x64, build 14367 + Avidemux 15th June 2016 --> Issue remains.
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
Quote from: Jan Gruuthuse on June 18, 2016, 05:22:23 PM
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.
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.
It will be probably an update of Qt5 that will fix the problem if it stays there
Win10, x64, build 14367 + Avidemux 21st June 2016 --> Issue remains.
Win10, x64, build 14367 + Avidemux 24th June 2016 --> Issue remains.
Win10, x64, build 14371 + Avidemux 24th June 2016 --> Issue remains.
Win10, x64, build 14371 + Avidemux 25th June 2016 --> Issue remains.
Win10, x64, build 14372 + Avidemux 25th June 2016 --> Issue remains.
Win10, x64, build 14376 + Avidemux 26th June 2016 --> Issue remains.
Win10, x64, build 14376 + Avidemux 30th June 2016 --> Issue remains.
Win10, x64, build 14379 + Avidemux 30th June 2016 --> Issue resolved!!!
(At least for the time being...)
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.
nothing was done here
gremlins at work ;)
Since build 14379 there are no longer simialr issues with qBittorrent where certain dialog windows would not 'pop up'.