Therefore, I would expect that a rebuild of 6.1.18 today or a new build of 6.1.20 would also be rejected by the VirtualBox hardening code. The major difference is the point in time when the code signature was created. r142917 all use the same expired Microsoft cross-certificate. This will add Microsoft's stamp of approval directly which is the new signing process they're describing at the URL mentioned above. They are already going through attestation signing today. Of course, release builds will be as before (except guest additions, that will need some thinking). So I can't test now with 142777 or 142894 for example. If you didn't download some of the older versions, you have no chance to do it later. I hope this would help to find the cause of this mess.Īnother problem here: there is no archive of the test builds. I put both VBoxHardening files (from pack installation and VM start itself) in archive.
If I install the previous version (142299), the installation goes without problems, but at the start of the VM I get the messages, described by the others above. More details may be available in 'C:\VBoxMachines\XP\Logs\VBoxHardening.log'. The virtual machine 'XP' has terminated unexpectedly during startup with exit code 1 (0x1). The only change is the build of Virtual Box, and indeed reverting back from 142917 to 142777 fixes the problem.įailed to open a session for the virtual machine XP. The previous developer build: 6.1.19 142777 was fine.
(XP 32 bit, but also same for a 64 bit Windows 10 guest and 32 bit Windows 7 guests) With developer build Virtual Box 6.1.19 142917, I receive the following (or similar) when trying to start any VM Am running Windows 8.1 Pro 圆4 fully patched (build 9600.19941).
0 kommentar(er)
