virtualbox.org

180c.14fc: *0000000060c90000-0000000060c90fff 0x0002/0x0080 0x1000000 \Device\HarddiskVolume3\Windows\System32\itcspea64.dll.000
180c.14fc: supHardNtVpScanVirtualMemory: Ignoring unknown mem at 0000000060c90000 LB 0x1000 (base 0000000060c90000) - 'itcspea64.dll.000'
180c.14fc: 0000000060c91000-0000000060c92fff 0x0020/0x0080 0x1000000 \Device\HarddiskVolume3\Windows\System32\itcspea64.dll.000
180c.14fc: supHardNtVpScanVirtualMemory: Ignoring unknown mem at 0000000060c91000 LB 0x2000 (base 0000000060c90000) - 'itcspea64.dll.000'
180c.14fc: 0000000060c93000-0000000060c93fff 0x0002/0x0080 0x1000000 \Device\HarddiskVolume3\Windows\System32\itcspea64.dll.000
180c.14fc: supHardNtVpScanVirtualMemory: Ignoring unknown mem at 0000000060c93000 LB 0x1000 (base 0000000060c90000) - 'itcspea64.dll.000'
180c.14fc: 0000000060c94000-0000000060c94fff 0x0008/0x0080 0x1000000 \Device\HarddiskVolume3\Windows\System32\itcspea64.dll.000
180c.14fc: supHardNtVpScanVirtualMemory: Ignoring unknown mem at 0000000060c94000 LB 0x1000 (base 0000000060c90000) - 'itcspea64.dll.000'
180c.14fc: 0000000060c95000-0000000060c97fff 0x0002/0x0080 0x1000000 \Device\HarddiskVolume3\Windows\System32\itcspea64.dll.000
180c.14fc: supHardNtVpScanVirtualMemory: Ignoring unknown mem at 0000000060c95000 LB 0x3000 (base 0000000060c90000) - 'itcspea64.dll.000'

mpack wrote:I do not believe that WinTrust.DLL is the source of your problem.

Basically, VirtualBox believes you've been hacked. It discards this strange DLL, which leads to the error.

Previous occurrences of this symptom were also from Russian users - apparantly it's due to some kind of security or VPN software that's popular in Russia (InfoTeCS?), however VirtualBox has not detected it (it is not listed in the "adversaries" section of the hardening log). If you know what this software is then you might try uninstalling it as a test, or add VirtualBox as an exception to whatever it does.

Lodegin wrote:I read in other post that virtualbox can ignore process of this program. How can i do it?

Mpack wrote:try uninstalling it as a test, or add VirtualBox as an exception to whatever it does.

scottgus1 wrote:

Lodegin wrote:I read in other post that virtualbox can ignore process of this program. How can i do it?

Please post the link in a text file or insert enough spaces in the link to stop the no-links-first-day filter from triggering on the link.

Virtualbox does not have a 'whitelist' feature to ignore other programs which are injecting themselves into Virtualbox's space unnecessarily. Some of these other programs have exclusion features that can tell them to stay out of Virtualbox. Check if your crypto-security program has such an exclusion feature, and exclude all folders and files related to Virtualbox and your VMs.

To see if this program is causing the trouble:

Mpack wrote:try uninstalling it as a test, or add VirtualBox as an exception to whatever it does.

scottgus1 wrote:Thanks for the link. Unfortunately, while it appears o discuss the same program you are dealing with, the link does not show any way to allow Virtualbox to run while itcspea64.dll is invading Virtualbox. The recommended action was also to uninstall InfoTeCS.

Though InfoTeCS is a security program, its methods, like many other security and antivirus programs, act just like malware to work. Virtualbox cannot tell if InfoTeCS is malware or not.

You may be able to ask InfoTeCS support about this glitch, maybe they know a way to exclude Virtualbox. The Virtualbox developers have worked with 3rd-party software providers to achieve coexistence. Or if this is a work computer you can ask the boss about getting IT to exclude Virtualbox from InfoTeCS.

Lodegin wrote:cause it's russia (yes 'r', not 'R')

mpack wrote:On the contrary. You are writing in English, a language which requires that proper nouns be capitalized on their first letter. Hence the correct form is "Russia" and not "russia".

mpack wrote:Whatever the purpose of the software, it appears to be invasive like other security software (and malware), and it is presumably unsigned or it would be allowed. VirtualBox will block all unsigned invasive software.

(1) the DLL never had a valid certificate - e.g. malware, free software, or the vendor made a mistake

fth0 wrote:FWIW, it doesn't matter here if itcspea64.dll.000 is correctly signed or not, the error would occur anyway. Your only chance is to prevent the software from invading the memory of the VirtualBox processes.

fth0 wrote:Thinking about your situation again, another alternative came to mind:

You could perhaps uninstall the software, create a VirtualBox VM and install and use the software within the VM ...

Lodegin wrote:If it will be lost i need restore it in government service.

scottgus1 wrote:What would happen if your computer died? You'd need to back this up somehow.

scottgus1 wrote:To cut to the chase, Virtualbox cannot run until InfoTeCs stops invading Virtualbox's space. Virtualbox does not contain any way to authorize InfoTeCs' invasion. I know it sounds like a real bother, but InfoTeCs is using the same method as malware uses to invade other programs' space, and Virtualbox can't allow that malware method to invade Virtualbox, so the host PC doesn't become a rogue DDOS/ransomware bot participant.

If InfoTeCs does not have an exclusion feature, then the situation is at an impasse. You'll have to decide between InfoTeCs and Virtualbox, or set up your PC so it can dual-boot two host OS's: one with InfoTeCs and one with Virtualbox.

If you can figure out how to back up InfoTeCs to transfer it to a different PC, then you can transfer it into a VM. If that is not possible then we're stuck.