Repurchased VA - now V2 - problems with profiles - HELP!!

[Globespy]

So I decided to continue support of this very helpful program.
I mainly use for one game.
I have a profile for that game that auto-loads.

I thought that the main Voiceattack.settings export file from within the main VA program options was 'everything'? - I guess it does not include the profiles?
I am trying to export that profile, however when I click the export button I do not see any dialogue telling me where it's being saved to, nor the more important option of saving it as a .vap file, which I NEED to import to VA V2.
When this happens, VA V1 just closes, no error, just closes.

So where is the .vap file as I cannot find it, and Windows has searched my entire PC and cannot find it, at least not a recent save of today's date - most recent is Dec 2024, and that's missing a LOT of changes.

I tried opening VA V1 and duplicating the profile then exporting, same thing happens.

If there's somehow corruption in VA V1, I need a solution as the profile works perfectly, and without it there's no point in even using VA V2 if I have to spend hours putting all that info back in.

Additionally, Windows is telling me that support for it's voice recognition is ending, being replaced by some new bar thing on the top? How will VA V2 work without this?

Appreciate the help, really need it as in a bit of a panic!
Thanks!

Update:
So I tried using the .bat file in the new V2 install directory and seems it copied over the profile, however the same problem persists with the export profile function in VA V2 where there's no 'save as' dialogue and despite seeing the active and working profile in VA V2, it just force closes the app and the .vap file is nowhere to be found?
Even more confused!!

Update 2:
Seems that even with the freshly installed V2, the same problem that's been causing the outoing V1 still exists and I found it in EvenViewer - it's a 'KERNELBASE.dll' error that's causing this in the program>
Why is VA V2 even looking at the kernelbase.dll in this location? For x64 applications it should be using the kernelbase.dll version in Windows>SysWOW64 instead of System32??:

Faulting application name: VoiceAttack.exe, version: 2.1.6.0, time stamp: 0x674f0000
Faulting module name: KERNELBASE.dll, version: 10.0.22621.5189, time stamp: 0x45f9d0b6
Exception code: 0xe0434352
Fault offset: 0x000000000006016c
Faulting process id: 0x0x7394
Faulting application start time: 0x0x1DBC69BB948956E
Faulting application path: C:\Program Files\VoiceAttack\VoiceAttack.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 16423c2e-59ef-4744-b33a-d1e27f8f7d29
Faulting package full name:
Faulting package-relative application ID:

[Pfeil]

Unfortunately something appears amiss on your system. The dialog that should be shown is a standard Windows dialog, not a component of VoiceAttack itself.

You could try a system file scan, to see if that makes a difference: https://support.microsoft.com/en-us/help/4026529/windows-10-using-system-file-checker

Windows is telling me that support for it's voice recognition is ending, being replaced by some new bar thing on the top? How will VA V2 work without this?

The Windows Speech Recognition application is being removed. The underlying components, which are what VoiceAttack uses, will remain available.

Why is VA V2 even looking at the kernelbase.dll in this location? For x64 applications it should be using the kernelbase.dll version in Windows>SysWOW64 instead of System32??:

System32 stores 64-bit files. SysWOW64 belongs to the Windows On Windows 64 is the emulator that allows 32-bit applications to run on 64-bit platforms, and thus stores 32-bit files.

[Globespy]

Thank you for the reply!
It took some troubleshooting but seems that for whatever reason that I'll likely never know, after December 2024 things became somehow corrupted, even though the program/profile worked - it just wouldn't save.
I loaded a save from December 2024 and went through the save process and everything works as it should - no idea why Windows was saying it was a problem with its 'kernelbase.dll' as it was clearly only related to how it interacted with VA?

So, in the end the problem WAS actually VA/VA saves that were corrupt and causing all this!

BTW - moving forwards, if I choose the 'export' option in the main VA program that produces the 'VoiceAttack.settings' file, will that file incorporate everything regarding the program changes I made to suit my needs AND the profiles?
Or only the main program setup, and I would still need to export the profiles separately as .vap files?
Thank you, and the VA V2 seems like a nice update, with what I can tell slightly faster processing?
Just happy to support your work.
Cheers!

[Pfeil]

if I choose the 'export' option in the main VA program that produces the 'VoiceAttack.settings' file, will that file incorporate everything regarding the program changes I made to suit my needs AND the profiles?
Or only the main program setup, and I would still need to export the profiles separately as .vap files?

The "Export Settings" button exports the application settings, specifically. Profile settings and the profiles themselves are stored in the profile database.
Command snippets and TTS sound effects also have their own databases.

To back up those databases, you can copy the files in the folder opened using the "Click here to browse VoiceAttack's data folder." link on the "System / Advanced" tab of the VoiceAttack options window.

"VoiceAttack.dat" is the profile database, the "Backup" folder contains older copies of that file with a timestamp, "VAEffects.dat" contains TTS effects, "VASnippets.dat" contains command snippets.

[Globespy]

Would be cool to have a backup everything button. 

[SemlerPDX]

Would be cool to have a backup everything button. 

You could make a voice command in VoiceAttack to do that for you   

[Globespy]

Would be cool to have a backup everything button. 

You could make a voice command in VoiceAttack to do that for you   

Really? Can you help me with that if you already have something that does it, or something similar to learn from? OR point me to perhaps a section in these forums where I can learn how to go about creating this when I'm admittedly coming from a pretty 'green' starting point.
And thank you for your reply, never really thought about using voice for internal automation of the VA app, which is an oversight on my part.