winuae 64bit not working on Windows 10

Hi !

The 32bit version works but the 64bit version not.
Anybody else with this problem ?

WinUAE is not functioning anymore

The program does not run correctly because of a problem.
The program closes, and you are notified when a solution is available.

Close programm

[Toni Wilen]

Unfortunately that message won't help. It only means "something went wrong".

Which winuae version? Please use latest 3.2 beta because previous 64-bit versions were mostly unsupported (due to lack of JIT support and others)

If it does the same, run it with -log command line parameter ("winuae.exe -log") and if it opens log window before it crashes, check directory where winuae.exe is located for log file winuaebootlog.txt, attach it. If log is missing but something gets output to log window, attach screenshot or text copy from the log window.

Thank you very much for your help !
Even with the public beta version it crashes.

Here´s the log file:

[Toni Wilen]

Does GUI open? (I thought you meant it crashes before GUI opens). Does it crash after emulation has been started? If it does, use latest beta and run it with -log -logflush command line parameters and attach winuaelog.txt ("winuae64.exe -log -logflush")

It should also create crash dump file. (winuae_xyz.dmp in same directory as winuae.exe), compress and attach/email it, thanks.

I can see the GUI but when I want to add for example the kickstart rom file or a floppy image of a game it crashes.

I Did what you said but I get only a text file and no dump file.

[Toni Wilen]

Ok... I had similar problem, some of TortoiseSVN or TortoiseGit shell extension seems to have a bug . Instant crash when opening any WinUAE file dialog. Crash was caused by a stack overflow in some TortoiseXXX DLL..

It still happened even if I simplify WinUAE as much as possible (As simple as MSDN example for SHCreateItemFromParsingName() function). Only happened when running 64-bit WinUAE under debugger.

Quick fix was to disable all "Tortoise overlay handler shim"s with ShellExView.

And how does this helps me ?
I downloaded the latest beta 3.2.0 Beta 20 RC 3 and still the same error.

[Toni Wilen]

It means you have at least one buggy shell extension installed (shell extension = custom entries in windows explorer, custom icons, custom entries in explorer properties window etc..)

You can download 64-bit ShellExView (http://www.nirsoft.net/utils/shexview.html) and use it to disable non-Microsoft extensions one by one until you find the one that causes the problem.

There is nothing WinUAE can do, it can't even detect the problem because crash happens in different process.

[zipper]

It's a PITA Windows behaviour, I do have something buggy in my extensions on my Win10 laptop and a long list to try. So far I just disabled all and enabled again to get rid of the error (Windows won't even open some folders).

[Saghalie]

Originally Posted by zipper

It's a PITA Windows behaviour, I do have something buggy in my extensions on my Win10 laptop and a long list to try. So far I just disabled all and enabled again to get rid of the error (Windows won't even open some folders).

For me the winuaebootlog.txt file shows:
F:\Program Files (x86)\Cloanto\Amiga Forever\Player\amigaforever.dll failed to open 193

So I figured I would check out that shell explorer that Toni suggested. I looked for anything Amiga Forever and found the Amiga Explorer was installed and it indeed used the amigaforever.dll. I disabled it and now everything works fine.

Regards,

Saghalie

[Saghalie]

Originally Posted by Saghalie

... I disabled it and now everything works fine.

I spoke too soon, it worked one time and now for some reason it keeps crashing out and failing to load the amigaforever.dll file. Not that that is the problem.

Whenever I try to load a cd image and go to the file selector, the program just quits and doesn't give me any errors.

Regards,

Saghalie

[midimax]

Originally Posted by zipper

... So far I just disabled all ...

Including the Microsoft extensions?

Because in regard to this problem I have disabled each and every non-Microsoft extension, even the 32-bit extensions. Without any luck.

[Leandro Jardim]

Originally Posted by midimax

Including the Microsoft extensions?

Because in regard to this problem I have disabled each and every non-Microsoft extension, even the 32-bit extensions. Without any luck.

I needed to disable Avast Antivirus shell extensions, and now WinUAE works, but the Avast pop-up menu on Windows Explorer has gone.

[Schlachtwerk]

Same Problem here, but i will not disable any secure features from Avast for WinUAE.

[Toni Wilen]

No stupid posts allowed.

Originally Posted by Schlachtwerk

Same Problem here, but i will not disable any secure features from Avast for WinUAE.

It is not a security feature. Just a shortcut.

[Schlachtwerk]

Okay now it will work THX

[Toni Wilen]

It is really odd that so many shell extensions fail that way now if application is 64-bit. There must have been some common example code that everyone copied which had some hidden bug or something like that..

Suddenly this is happening for me - WinUAE 64 bit version 3.4. I'm going to install the 32 bit version and see how that goes.

Quick follow up - it happens when I try to insert an adf from the f12 menu - it's almost like any time I have to fire up windows explorer from within 64 bit WinUAE, it crashes (Windows 10, no idea what shell extensions I have). Using 32 bit seems to make things work as expected.