[Bug]: Driving Conflict

[YXFY123]

Version

trunk/main

Host OS Type

Linux

Host OS name + version

Linux Mint 22.2 kernel6.14.0-29

Host Architecture

x86

Guest OS Type

all

Guest Architecture

x86

Guest OS name + version

All

Component

Unspecified

What happened?

虚拟电脑名称: win10

Driver name clash. Another driver with the same name as the one being registered exists. (VERR_PDM_DRIVER_NAME_CLASH).
返回 代码:
NS_ERROR_FAILURE (0x80004005)
组件:
ConsoleWrap
界面:
IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}

VBox.log

How can we reproduce this?

Installing Clash

Did you upload all of your necessary log files, screenshots, etc.?

• Yes, I've uploaded all pertinent files to this issue.

[TommiPrami]

VM Name: Win10pro

Driver name clash. Another driver with the same name as the one being registered exists. (VERR_PDM_DRIVER_NAME_CLASH).
Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}

Seems that same happens me for all my Virtual Guersts, with VirtrualBox 7.2.2

Windows 11 Host and Guests Win10/11

[arohr]

Same error here: Host Ubuntu 24.04, Guest: Ubuntu 24.04
Virtualbox v7.2.2

[Plus5BattleAxe]

Same error here as well.
Host = Arch (kernel = 6.16.7)
Guest = all (Arch, Win 11)
VirtualBox 7.2.2

[PeteParis]

the error relates actually to the recent release of a new extension pack 7.2.2, with the old one presumably leading to a new conflict. Note however that the new extension 7.2.2 will not update automatically today (see todays related bug report) and needs to be downloaded manually from the TV site. Do the update and the conflict is gone.

[Plus5BattleAxe]

the error relates actually to the recent release of a new extension pack 7.2.2, with the old one presumably leading to a new conflict. Note however that the new extension 7.2.2 will not update automatically today (see todays related bug report) and needs to be downloaded manually from the TV site. Do the update and the conflict is gone.

Worked! Thank you.

[arohr]

the error relates actually to the recent release of a new extension pack 7.2.2, with the old one presumably leading to a new conflict. Note however that the new extension 7.2.2 will not update automatically today (see todays related bug report) and needs to be downloaded manually from the TV site. Do the update and the conflict is gone.

Worked also for me. Thanks!

[YXFY123]

the error relates actually to the recent release of a new extension pack 7.2.2, with the old one presumably leading to a new conflict. Note however that the new extension 7.2.2 will not update automatically today (see todays related bug report) and needs to be downloaded manually from the TV site. Do the update and the conflict is gone.

ok，thankyou