Custom Query (16363 matches)
Results (1612 - 1614 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #17101 | duplicate | RDP connection failure | ||
| Description |
After updating the guest additions to 5.1.28 on a Windows 10 guest, I am getting errors with RDP clients - "Remote Desktop Connection has stopped working". Worked with 5.1.26, works on non-VirtualBox systems, and works if I remove the guest additions. I get the following error logged: Faulting application name: mstsc.exe, version: 10.0.10240.17184, time stamp: 0x580ee9a2 Faulting module name: VBoxOGLpackspu.dll, version: 5.1.28.17968, time stamp: 0x59b8f746 Exception code: 0xc0000005 Fault offset: 0x000000000004966f Faulting process id: 0xd64 Faulting application start time: 0x01d3323e84eb3d97 Faulting application path: C:\Windows\system32\mstsc.exe Faulting module path: C:\Windows\system32\VBoxOGLpackspu.dll Report Id: a8105f28-28b8-4122-b3b0-226dec3879c9 Faulting package full name: Faulting package-relative application ID: |
|||
| #17098 | invalid | Windows crash when try use USB disk for DOS | ||
| #17095 | obsolete | Logfiles reporting "vminfo Error: Guest Property: Failed to query '/VirtualBox/HostInfo/VRDP/ActiveClient': VERR_NOT_SUPPORTED" after resume from hibernate in guest VM | ||
| Description |
Don't laugh. After resuming from hibernation in a Devuan 1.0 guest (with 5.1.26 GAs built from virtual CD), log messages begin appearing by the truckload: vminfo Error: Guest Property: Failed to query '/VirtualBox/HostInfo/VRDP/ActiveClient': VERR_NOT_SUPPORTED Granted, hibernating within a VM is not one of the smartest things a user can do, but there may be some reason someone feels driven to try this. Using VirtualBox's own save state/restore state feature is a much better approach, not to mention about 80-1000 times faster. Host is CentOS 6.9, with VBox 5.1.26. The workaround is to not to do this. Use the save/restore state feature of VBox instead. Duh. |
|||

