Custom Query (16363 matches)
Results (961 - 963 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #18791 | invalid | VM starting failed with "Lacks WinVerifyTrust" at Windows 7 64bit with VB 5.2.18/20/32/33 and 6.0.10 | ||
| Description |
I cannot start VM after upgrading VB to 5.2.32 from 5.2.18 with below partial log at VBoxHardening.log. Full log file attached. Even though revert to 5.2.18, it was failed with same log, lacks winverifytrust. Uninstall & reinstall 5.2.18/20/32/33 and 6.1.10, the log was same. So, I cannot use VB anymore. One thing, Symantec Endpoint Protection 14.2.3335.1000 was installed before I upgrade VB to 5.2.32 and rebooted. Is this related with Symantec Endpoint Protection? I cannot uninstall and disable as I don't know the required password. I found similar case on this tracker, but I cannot resolve my case. Many thanks for your any hint !!! 1a78.eac: supHardenedWinVerifyImageByHandle: -> 22900 (\Device\HarddiskVolume2\Windows\System32\kernel32.dll) 1a78.eac: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume2\Windows\System32\kernel32.dll 1a78.eac: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\system32\kernel32.dll (Input=kernel32.dll, rcNtResolve=0xc0150008) *pfFlags=0xffffffff pwszSearchPath=0000000000000000:<flags> [calling] 1a78.eac: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume2\Windows\System32\kernel32.dll [lacks WinVerifyTrust] 1a78.eac: supR3HardenedDllNotificationCallback: load 0000000077a10000 LB 0x0011f000 C:\Windows\system32\kernel32.dll [fFlags=0x0] 1a78.eac: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume2\Windows\System32\kernel32.dll [lacks WinVerifyTrust] 1a78.eac: supR3HardenedDllNotificationCallback: load 000007fefd800000 LB 0x00067000 C:\Windows\system32\KERNELBASE.dll [fFlags=0x0] 1a78.eac: supHardenedWinVerifyImageByHandle: -> 22900 (\Device\HarddiskVolume2\Windows\System32\KernelBase.dll) 1a78.eac: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume2\Windows\System32\KernelBase.dll 1a78.eac: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=0000000077a10000 'C:\Windows\system32\kernel32.dll' 2238.26b4: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xc0000005 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 68 ms, CloseEvents); |
|||
| #18790 | duplicate | VBox 6.0.10: Windows guests crash when accessing shared folders -> duplicate of 18766 | ||
| Description |
After upgrades to version 6.0.10 all my Windows 7 x64 virtual machines (on Windows 10 x64 host) started to blue screen when trying to read or write to folders that were shared with the host. Errors are varied and always disk related (irql_not_less_or_equal). Already tried the extra pack 6.0.8 with version 6.0.10 and also gives the same error which leads to believe that is version 6.0.10 the problem. |
|||
| #18786 | invalid | Disks disappear in Windows client | ||
| Description |
I am using VirtualBox 6.0 on Ubuntu 18.04 with (mostly) Windows clients. Recently I noticed that sometimes disks disappear from Windows, so in the client. I thought first it was with one Virtual Machine where I use IDE and SATA, but today I also noticed it in a client that uses SATA and SCSI. Neither Windows nor VirtualBox reports any error. Some disks just disappear. After restart of the client all disks are there again. I recently had hard disk problems, but I can't really relate to that as everything seems just fine and no errors are reported. |
|||

