Custom Query (16363 matches)
Results (2035 - 2037 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16206 | worksforme | vboxvideo.ko unable to be inserted into kernel on CentOS 6/7 -> expected behaviour | ||
| Description |
Guest: CentOS 6/7, software development workstation install (with Gnome GUI) GuestAdditions: Installed and rebooted successfully, no errors. Trying to access VM via RDP, authentication method: NULL The screen resolution doesn't change. on ubuntu 16.04 for instance, the screen resolution changes automatically. Looking at list of modules inserted, I see vboxsf and vboxguest but not vboxvideo. On CentOS 7 find /lib/modules | grep vboxvideo /lib/modules/3.10.0-327.36.3.el7.x86_64/misc/vboxvideo.ko insmod /lib/modules/3.10.0-327.36.3.el7.x86_64/misc/vboxvideo.ko insmod: ERROR: could not insert module /lib/modules/3.10.0-327.36.3.el7.x86_64/misc/vboxvideo.ko: Invalid parameters On CentOS 6 find /lib/modules | grep vboxvideo /lib/modules/2.6.32-642.6.2.el6.x86_64/misc/vboxvideo.ko insmod /lib/modules/2.6.32-642.6.2.el6.x86_64/misc/vboxvideo.ko insmod: error inserting '/lib/modules/2.6.32-642.6.2.el6.x86_64/misc/vboxvideo.ko': -1 Invalid parameters The module is built correctly but doens't get loaded, which means I don't get the RDP resizing that I really want, in fact, that's the only reason I installed guest additions. |
|||
| #16204 | fixed | Virtualbox Driver doesn't have WHQL Certificate | ||
| Description |
Driver signing changed in Windows 10 1607 Version: Microsoft said: Starting with new installations of Windows 10, version 1607, the previously defined driver signing rules will be enforced by the Operating System, and Windows 10, version 1607 will not load any new kernel mode drivers which are not signed by the Dev Portal. OS signing enforcement is only for new OS installations; systems upgraded from an earlier OS to Windows 10, version 1607 will not be affected by this change. If your driver doesn't have Microsoft Windows Hardware Publisher Certificate (For Example:IDM Browser WFP Driver), Windows will block the installation of this driver. So Does Virtualbox should get a Microsoft Certificate? |
|||
| #16202 | fixed | Unable to start guests on Windows 10 Insider build 14971 | ||
| Description |
Windows 10 Pro (x64) Insider build 14971 arrived today and VirtualBox is know no longer to start any of my VM's The following appears in a dialogue box: Title: VirtualBox - Error In supR3HardNtChildPurify Message: supHardenedWinVerifyProcess failed with VERR_CR_X509_CPV_NOT_VALID_AT_TIME: (rc=-23033) Please try reinstalling VirtualBox. where: supR3HardNtChildPurify what: 5 VERR_CR_X509_CPV_NOT_VALID_AT_TIME (-23033) - Certificate path validator: The certificate is not valid at the specified time. I've tried reverting to VBox 5.1.6 & 5.1.7 and also installing the 5.1.9-111957 test build. The VBoxHardening.log file reports some kind of certificate validation problem with ntdll.dll in \Windows\System32: 118c.1b38: supHardenedWinVerifyProcess failed with Unknown Status -23033 (0xffffa607): Certificate is not valid (ValidTime=2088-08-14T12:05:18.000000000Z Validity=[2014-05-28T17:33:33.000000000Z...2029-05-28T17:43:33.000000000Z]): \Device\HarddiskVolume4\Windows\System32\ntdll.dll 118c.1b38: Error -23033 in supR3HardNtChildPurify! (enmWhat=5) 118c.1b38: supHardenedWinVerifyProcess failed with Unknown Status -23033 (0xffffa607): Certificate is not valid (ValidTime=2088-08-14T12:05:18.000000000Z Validity=[2014-05-28T17:33:33.000000000Z...2029-05-28T17:43:33.000000000Z]): \Device\HarddiskVolume4\Windows\System32\ntdll.dll |
|||


