Search found 10 matches
- Fri Apr 12, 2019 2:01 pm
- Forum: Technical questions
- Topic: Initialization error 4 in x86 build
- Replies: 11
- Views: 7985
Re: Initialization error 4 in x86 build
I can confirm that the issue is fixed in the 1099 build.
- Wed Apr 10, 2019 3:58 pm
- Forum: Technical questions
- Topic: Initialization error 4 in x86 build
- Replies: 11
- Views: 7985
Re: Initialization error 4 in x86 build
Can you confirm yet if this is indeed a bug in VMProtect along with a possible ETA for a fix?
I have quite a few customers who need to use the x86 version of my product.
I have quite a few customers who need to use the x86 version of my product.
- Tue Apr 09, 2019 11:44 am
- Forum: Technical questions
- Topic: Initialization error 4 in x86 build
- Replies: 11
- Views: 7985
Re: Initialization error 4 in x86 build
Done, thank you for your help!Admin wrote:OK. Please send all files (the original binary + MAP + VMP files too) to info@vmpsoft.com
- Tue Apr 09, 2019 10:57 am
- Forum: Technical questions
- Topic: Initialization error 4 in x86 build
- Replies: 11
- Views: 7985
Re: Initialization error 4 in x86 build
When using VMProtect and running the resulting executable, VMProtect will detect a file modification and close the app. ... because the file was modified in the memory? It seems something changes your protected file at the runtime and VMProtect detects it and shows the error. The file is not modifi...
- Tue Apr 09, 2019 10:37 am
- Forum: Technical questions
- Topic: Initialization error 4 in x86 build
- Replies: 11
- Views: 7985
Re: Initialization error 4 in x86 build
There is definitely something wrong with VMProtect and x86 builds. I built a small test case which is literally the following C++ code: #include "VMProtectSDK.h" int DeactivateLicense(void) { VMProtectBeginUltra("DeactivateLicense"); VMProtectEnd(); return 0; } int main(void) { c...
- Mon Apr 08, 2019 8:57 pm
- Forum: Technical questions
- Topic: Initialization error 4 in x86 build
- Replies: 11
- Views: 7985
Re: Initialization error 4 in x86 build
Disregard this.
This was caused by a memory overwrite of 4 bytes in the application's startup code. I guess this corrupted something in a way that made VMProtect "unhappy".
This was caused by a memory overwrite of 4 bytes in the application's startup code. I guess this corrupted something in a way that made VMProtect "unhappy".
- Mon Apr 08, 2019 5:33 pm
- Forum: Technical questions
- Topic: Initialization error 4 in x86 build
- Replies: 11
- Views: 7985
Re: Initialization error 4 in x86 build
I updated my subscription in order to upgrade to the latest build 1097, and the issue persists. With build 1097, the "Initialization error 4" is gone, but now the x86 exe simply refuses to start - it looks like it starts but then immediately closes itself again. And again, the x64 build wo...
- Mon Apr 08, 2019 3:31 pm
- Forum: Technical questions
- Topic: Initialization error 4 in x86 build
- Replies: 11
- Views: 7985
Initialization error 4 in x86 build
Since upgrading to build v3.3.1.1076 on Windows, the x86 build of my application always fails to start with "Initialization error 4".
All options are the same and this used to work with prior versions of VMProtect.
The x64 build works fine.
Any ideas?
All options are the same and this used to work with prior versions of VMProtect.
The x64 build works fine.
Any ideas?
- Wed Jun 20, 2018 9:07 am
- Forum: Technical questions
- Topic: Support for automatic proxy server
- Replies: 3
- Views: 4086
Re: Support for automatic proxy server
Can the developers chime in on this?
As a customer, I'd be interested in whether this is something that can be fixed. I have clients that rely on this.
As a customer, I'd be interested in whether this is something that can be fixed. I have clients that rely on this.
- Fri Jun 08, 2018 1:39 pm
- Forum: Technical questions
- Topic: Support for automatic proxy server
- Replies: 3
- Views: 4086
Support for automatic proxy server
I have a client that uses an automatic proxy server which cannot connect to my activation server using VMProtect/WebLM. The problem seems to be that the proxy server is set automatically in the internet options, so that it is assigned whenever a user on the network gets his IP address via DHCP. When...