Comments
jkratena
@besser82 I just tested this on the VM with Fedora 43 with a newly created wine prefix.
Right after prefix was created, I ran winecfg and set Windows Version: to "Windows 11". Then I installed MetaTrader Administrator app - setup completed successfully...
... however, when I tried to run metatraderadmin.exe, I've got the same "A debugger has been found on your system... " prompt.
Exactly a same behaviour with MetaTrader 5 Administrator app
@besser82: It is set to Win 11 in winecfg, not working.
Is new wine prefix required to get it working?
MetaTrader applications (all of them) and some other apps with "anti tamper" protection refused to start with a prompt "A debugger has been found on your system, unload it from memory and restart your program"
0024:fixme:ntdll:NtRaiseHardError 0x50000018 4 0x3 0xe2f6e4 0 0xe2f6f4: stub
https://bugs.winehq.org/show_bug.cgi?id=58011 https://bugs.winehq.org/show_bug.cgi?id=58043
Updated successfully, no issues yet
Works fine here, can install 64-bit and 32-bit versions of llvm-devel alongside each other now - BZ#2365079
Sensitive apps are reporting that Windows Debugger is active with this version (10.4) and refusing to start:
"A debugger has been found running in your system please unload it from memory and restart your program "
No such issue with Wine 10.1 or 10.2
@luk1337: I checked this update thread again after some time hoping for a miracle... and here it is. You deserve a medal.
YES, it helped!
No need to recreate wine prefix etc., everything is running fine as before with existing wine prefix.
@mooninite: Is there anything we need to do to have existing wine prefixes working with 10.2 builds?
I was trying to follow your instructions regarding "alternatives -config" but no luck.
Creating a new wineprefix is no option for me
Thx in advance
Someone opened bug report for Ubuntu 24.04 LTS with the same issue on Wine bug tracker, we should do the same
Same issue as nucleo above
No issue after downgrading to 10.1 as well
Works fine, fingerprint unlock works again now
Fixed: https://bugs.kde.org/show_bug.cgi?id=499637 https://bugs.kde.org/show_bug.cgi?id=481086