VB-Audio's Forums

Hello,

I have an error message updating to Windows 24H2 telling me that I have a Voicemeeter driver that is not ready for.

Thanks,

Christian

Yes, this is what we are discovering this week.

Voicemeeter is ready for 24H2 but Microsoft seems to have had problems during the testing phase (June) with some users probably having beta version of Voicemeeter and they did not contact us in time to clear up the situation. Official Voicemeeter version works of course, but they anyway decided to stop Win11 24H2 installation in case of the presence of our latest driver: vbvoicemeetervaio64_win10.inf

We are searching for a solution, because uninstalling Voicemeeter before updating to 24H2 seems to be not enough, since they are still detecting the presence of our ".inf" file... that must be deleted or renamed i guess...

will come back soon.

Okay thank you. Because I was thinking of uninstalling Voicemeeter to reinstall it later.

You may uninstall it + reboot,
if not enough, you could uninstall it by the Windows Device Manager if always present... and reboot.

Otherwise i guess you will have to delete or rename our inf file that could be located in
C:\Windows\System32\DriverStore\FileRepository
in a sub folder called: vbvoicemeetervaio64_win10.inf_amd64_xxxxxxxxx

then the 24H2 update should work... and later after you will be able to re-install Voicemeeter.

Je vais essayer, par curiosité déjà. De toute façon, j'ai prévu de refaire mon Windows car je me suis acheté un nouveau SSD. Sinon peut-être avec des dé-sinstallateurs !

Oops I published in French!


I'm going to try, out of curiosity. Anyway, I planned to redo my Windows because I bought a new SSD. Otherwise maybe with uninstallers!

t's a hassle, we don't have permissions to delete or modify files in windows/system32.

You may do it by using cmd (command prompt) in administrator mode.

It's not possible in admin

C:\Windows\System32>cd\

C:\>cd C:\Windows\System32\DriverStore\FileRepository\vbvoicemeetervaio64_win10.inf_amd64_c2bd37de84fa6e4f

C:\Windows\System32\DriverStore\FileRepository\vbvoicemeetervaio64_win10.inf_amd64_c2bd37de84fa6e4f>dir
Le volume dans le lecteur C s’appelle Windows 11
Le numéro de série du volume est 1E58-F318

Répertoire de C:\Windows\System32\DriverStore\FileRepository\vbvoicemeetervaio64_win10.inf_amd64_c2bd37de84fa6e4f

26/06/2024 12:06 <DIR> .
02/10/2024 19:09 <DIR> ..
26/06/2024 12:06 12 104 vbvoicemeetervaio64_win10.cat
26/06/2024 12:06 26 019 vbvoicemeetervaio64_win10.inf
26/06/2024 12:06 58 452 vbvoicemeetervaio64_win10.PNF
26/06/2024 12:06 296 352 vbvoicemeetervaio64_win10.sys
4 fichier(s) 392 927 octets
2 Rép(s) 59 681 058 816 octets libres

C:\Windows\System32\DriverStore\FileRepository\vbvoicemeetervaio64_win10.inf_amd64_c2bd37de84fa6e4f>ren vbvoicemeetervaio64_win10.inf vbvoicemeetervaio64_win10.infbak
Accès refusé.

so, using cmd again in administrator mode, you may try this line to enumerate audio devices:

pnputil /enum-drivers /class MEDIA

to find the oem name related to vbvoicemeetervaio64_win10.inf and use this instruction to force deletion:

pnputil /delete-driver oemxxx.inf /force

So. I managed to uninstall the driver, and also managed to install 24H2. I have yellow drivers but it must be something else. I reinstalled VoiceMeeter it works correctly Thanks