I can't use Audiolense

[winnie74829]

I have purchased Audiolense XO
When I press Run Measurement
Or creating new speaker settings will crash the software.
No message is displayed and the software is closed directly.
Visual C++ and dotnet framework 4.8 are already installed
I have also read most of the articles in the forum
I have tried deleting AI.ini and also tried the 32-bit beta version.
Also exclude related files from windows denfender
Even deleted the anti-virus software

My computer is ROG Strix SCAR 18 (2023)

Can anyone please help me?

 

[juicehifi]

So sorry to hear about your troubles.

Since you have problems with the speaker setup, it is certain that something is wrong with your operative system. Most likely some files are missing.

Perhaps the other version will work … 32 bit version. Or if you have another pc available you should try that.

There is one or two threads on the forum with successful fixing of the OS, so maybe you can find something there.

 

[winnie74829]

I don't have another PC
I just reinstalled Windows 11 last week
I've tried many older versions, both 32-bit and 64-bit
None can be used

I checked the event viewer
Displayed as follows

Failed application name: Audiolense.exe, version: 6.21.8385.21935, time: 0x639c524f
Failed module name: MtxVec.Fft.dll, version: 4.0.0.0, timer: 0x4b45ef50
Exception code: 0xc0000005
Error: 0x0000000000087efc
Failed handler identifier: 0x0x297C
Failed application start time: 0x0x1DAA9047CEF6955
Failed application path: C:\Program Files\Juice Hifi\Audiolense 6.21\Audiolense.exe
Failed module path: C:\Program Files\Juice Hifi\Audiolense 6.21\MtxVec.Fft.dll
Report identification code: 4218074e-b5a4-48e7-be9b-280a6872a9e4
Failed package full name:
Failed package-related application identifier:

I'm still trying to figure this out

 

[juicehifi]

Do you hav the c++ distro installed?

 

[winnie74829]

Yes, it has been installed countless times

 

[whoareyou]

This is a long shot.... Check your default directory and make sure it is local to the machine i.e. the documents folder is not a OneDrive folder in the cloud.
I think I had issues with this at one point when I accidentally enabled that ridiculous all too easy to miss MS "feature".