Hi guys,
I have a small VisualBasic6 application which I boxed with EnigmaVirtualBox for several years now. After applying the latest Windows 11 24H2 December cumulative update the Application starts with an Error "Component [filename] or one of its dependencies not correctly registered: a file is missing or invalid". I generated the application with the latest version of Enigma Virtual Box again, I tested also a fresh installation of Windows 11 24H2.
I created for testing a new project with no code, only GUI and added the controls. Then I boxed this application too, same error. The boxed applications runs on Windows 11 23H2 Dec24 Update, but also not on Windows 11 24H2 Dec Update.
Enigma Virtual Box Settings: added 2 .dll-files and 6 .ocx-files with file compression, file vritualization and register the .ocx-files
Did anyone else get the mentioned error message on your application after applying Windows 11 24H2 Dec24 update?
Existing Boxed Application not running on Windows 11 24H2 Dec24 Update
Re: Existing Boxed Application not running on Windows 11 24H2 Dec24 Update
Hi, please check if you have the following option enabled: Options - Map executable files with temporary file
Re: Existing Boxed Application not running on Windows 11 24H2 Dec24 Update
Hi, thanks for your fast reply. I had the option mentioned disabled. After enabling the boxed version of the application starts fine again. I was so focused on finding a solution within Windows and my environment, that I forgot to check available options in Enigma Virtual Box. The last changes I made in Project-File was about two years ago. Usually I only use the commandline functionalities in my build process
Re: Existing Boxed Application not running on Windows 11 24H2 Dec24 Update
This option has to be enabled by default for all projects, but we found many our customers disable it.
This option, btw, is quite required, to provide maximum compatibility with different applications and operation systems. It also does not provide any vulnerability or anything like this. Using this option does NOT mean EVB extracts files to the disk, no way, it only creates small empty dummy files on the disk to help protection emulate file calls in memory.
So this option is safe and required to be enabled.
This option, btw, is quite required, to provide maximum compatibility with different applications and operation systems. It also does not provide any vulnerability or anything like this. Using this option does NOT mean EVB extracts files to the disk, no way, it only creates small empty dummy files on the disk to help protection emulate file calls in memory.
So this option is safe and required to be enabled.
