VirtualBox.dll causing crash on New Machine Creation

[Chuckers]

I'm trying to use VB on a Win 7 Pro 32-bit PC but every time I click on the "New" icon or go to Machine >> New, to create a new machine, VB quickly crashes. Report claims VirtualBox.dll is the culprit.

Anyone know why this would happen and what the fix is, if any?

I already tried uninstalling and reinstalling 3 times with restarts and still having this issue.

Here's the crash report:

Problem signature:
Problem Event Name: APPCRASH
Application Name: VirtualBox.exe
Application Version: 5.2.2.19230
Application Timestamp: 5a15a9b9
Fault Module Name: VirtualBox.dll
Fault Module Version: 5.2.2.19230
Fault Module Timestamp: 5a15a9cc
Exception Code: c0000005
Exception Offset: 001eda27
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

[JonesG]

Solved.

Uninstall Ver 5.2.2 and install Ver 5.1.30

I had the same problem with 5.2.2.
I checked the version on a second m/c I had VM running without problems and clicked update, it came back with 'up to date'. this was Ver 5.1.30.
So I installed Ver 5.1.30 on the PC I had the VirtualBox.dll problem and once installed the create new all worked prefect.

[Chuckers]

Thanks for posting that.

I also found out last night that it works if you run in compatibility mode (Win XP).

I'm getting a surplus PC soon and as soon as I refurbish it I'm going to see if I can run the latest version on that. If not, I'll downgrade like you suggest.

Would still be nice to know why this is happening, though.

[socratis]

Would still be nice to know why this is happening, though.

If you ever find out, please post it here as well please, so we can all benefit. Because I'm as sure as I'm writing this, that it doesn't happen on the majority of hosts out there. Most probably an antivirus or some "conflictus incognita"...

[mpack]

In the past this has always been due to a third party app installing a buggy shell filter. VirtualBox trips over it when it has to open a common shell dialog box.