Custom Query (16363 matches)
Results (1606 - 1608 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #17125 | obsolete | After last Windows Update 2 days ago, VM doesn't work anymore | ||
| Description |
Windows forced an update on my Lenovo laptop that is runnning Windows 10 and Vm doesn't work anymore. I am trying to add a Host-only network to the VirtualBox Manager in the Preference menu, and it keeps saying this Error: Failed to create the host network interface. Querying NetCfgInstanceId failed (0x00000002). Result Code: E_FAIL (0x80004005) Component: HostNetworkInterfaceWrap Interface: IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9} We use this software for our FIRST Tech Challenge robotics. Could this bug be fixed, thanks. |
|||
| #17119 | fixed | Crash on Windows 10 (client guest) shutdown | ||
| Description |
I know this is in Italian Let me know if I need to translate in English The host is a laptop with Windows 10. Virtual Box is 5.1.28 Nome dell'applicazione che ha generato l'errore: SearchUI.exe, versione: 10.0.10586.1106, timestamp: 0x59ae258b Nome del modulo che ha generato l'errore: VBoxOGLpackspu.dll, versione: 5.1.28.17968, timestamp: 0x59b8f746 Codice eccezione: 0xc0000005 Offset errore 0x000000000004966f ID processo che ha generato l'errore: 0x124c Ora di avvio dell'applicazione che ha generato l'errore: 0x01d3388aff48f1e7 Percorso dell'applicazione che ha generato l'errore: C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe Percorso del modulo che ha generato l'errore: C:\WINDOWS\system32\VBoxOGLpackspu.dll ID segnalazione: 38f54b06-0a23-4e62-bc24-2525de8aed69 Nome completo pacchetto che ha generato l'errore: Microsoft.Windows.Cortana_1.6.1.52_neutral_neutral_cw5n1h2txyewy ID applicazione relativo al pacchetto che ha generato l'errore: CortanaUI Mattia |
|||
| #17116 | fixed | Serial device data not transmitted to Win XP guest => fixed in SVN/next maintenance | ||
| Description |
VirtualBox V5.1.14 Host: Win 7 Ultimate Guest: Win XP Pro We attach a power supply unit (PSU) to serial port COM1 of the physical machine running Win 7. The PSU sends status data to COM1 permanently. In the guest (WinXP) the virtual serial port COM1 is mapped to the real serial port COM1. This is the serial port configuration in the guest:
In the guest an application should monitor the state of the PSU. Now the Problem: When we start the VM the application doesn't receive the status data initially. :( Only if we send any character from the VM to COM1, the status data is received by the monitor application as expected. Further we can see, if we don't send a character to COM1, close the VM and start it again, the PSU status data is received at once. This succeeds as long as we don't reboot the host. After rebooting the host the next time and starting the VM receiving the PSU status data fails again. It seems, that VirtualBox requires sending some data to the serial port first, before it is able to receive data from the serial port. By the way, running the monitoring application in the host works perfectly. We have deeper analyzed the problem by watching the IOCTL traffic. The results are described in detail in the forum thread https://forums.virtualbox.org/viewtopic.php?f=2&t=84667&sid=a6eb50e33e626459cd4dbf1a3748cc5f&p=402188#p402188 There you will also find screenshots showing the critical IOCTL sequences. Many thanks ! |
|||

