| 1 | | Hi Yirkha, |
| 2 | | |
| 3 | | It looks like this issue may have reappeared after this week's major Windows 10 update for users of VirtualBox 4.3.30. I get the same Windows event signature and the same behavior, and a trace with {{{ procmon.exe }}} shows that the last process system event is {{{ QueryNameInformation }}} against {{{ ntdll.dll }}}, and then {{{ WerFault.exe }}} is invoked and the process is cleaned up. The really unfortunate bit is that I can't simply update to the latest build because even the latest Vagrant for Windows release doesn't support VirtualBox releases after 4.3. |
| 4 | | |
| 5 | | So, I'm curious whether one of these solutions is a possibility: |
| 6 | | |
| 7 | | * a test or patched build which disables the {{{ rtldrPEValidateDirectoriesAndRememberStuff() }}} function for 4.3.x (or even an earlier release). Depending on how much pain this validation saves, I'm wondering if it may even be a good idea to remove it permanently since each major Windows update is likely to cause a mismatch in the signatures again. |
| 8 | | |
| 9 | | * swapping in an older version of {{{ ntdll.dll }}} and possibly other DLLs. I imagine even if this method works for VirtualBox that it would likely cause issues elsewhere, though. |
| | 1 | For those using VirtualBox 4.3.x for Vagrant or other reasons: this issue cropped up again after this week's major Windows 10 update if you were running 4.3.30 rev 101610. Don't be like me and run numerous diagnostics and write a long post before realizing that the latest test build at https://www.virtualbox.org/download/testcase/VirtualBox-4.3.33-103933-Win.exe takes care of the problem. |
