Bonjour à vous,
J'ai un Lenovo THINKPAD T15G , le son fonctionnait parfaitement avec windows 11 22H2, mais depuis que je l'ai réinitialisé, je n'ai plus de son et aucun pilote ne foncitonne
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
My audio is not working after upgrading to 22H2. My computer is an ASUS less than one year old. I have tried to reinstall the Realtek driver without solving the problem.
Looking in the devicemanager the Realtek driver has this error after each time I have reinstalled the driver:
Device INTELAUDIO\FUNC_01&VEN_10EC&DEV_0294&SUBSYS_104313B2&REV_1000\5&205ca6cb&0&0001 had a problem starting.
Driver Name: oem88.inf
Class Guid: {4d36e96c-e325-11ce-bfc1-08002be10318}
Service: IntcAzAudAddService
Lower Filters:
Upper Filters:
Problem: 0x0
Problem Status: 0xC00000E5
Is there any ideas of what I can try to get this working again?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Bonjour à vous,
J'ai un Lenovo THINKPAD T15G , le son fonctionnait parfaitement avec windows 11 22H2, mais depuis que je l'ai réinitialisé, je n'ai plus de son et aucun pilote ne foncitonne
Although I followed meticulously all that is suggested in this (IMO, the best Website to Date, in terms of numerous alternative 'checks' to try, to resolve the problem) none has succeeded. Thank you all the same, Raju, for the exhaustive pointer.
'Sound' problems seem so widespread one might hink there just has to be a better way to infuse the OS with a common sound set-up.
Excuse the off-thread remark, but getting Windows + P on my HP to work with my external IiYama only (bottom choice) has proven equally impossible and I'm on the latest 22H2 22621.755, as I write). And meanwhile the inability to expunge mis-typed email addresses remains unresolved too. All major issues, IMO).
Part of the problem is that it varies between OEMs. Asus, Acer, Lenovo et al each have their different interfaces. Asus (imprudently) discontinued support for its ICEPower just as 22H2 and a subsequent update came out. Speaking of which: yesterday I updated to "2022-10 Cumulative Update Preview for .NET Framework 3.5 and 4.8.1 for Windows 11, version 22H2 for x64 (KB5018341)", which did not resolve the sound issue.
Although I followed meticulously all that is suggested in this (IMO, the best Website to Date, in terms of numerous alternative 'checks' to try, to resolve the problem) none has succeeded. Thank you all the same, Raju, for the exhaustive pointer.
'Sound' problems seem so widespread one might hink there just has to be a better way to infuse the OS with a common sound set-up.
Excuse the off-thread remark, but getting Windows + P on my HP to work with my external IiYama only (bottom choice) has proven equally impossible and I'm on the latest 22H2 22621.755, as I write). And meanwhile the inability to expunge mis-typed email addresses remains unresolved too. All major issues, IMO).
There is no known fix for this issue. I have tried countless attempts at correcting this problem and I am no novice.
My wife has the same issue with 22H2 on her PC we have tried to fix it to no avail.
I tried a rollback which resulted in completely totally destroying my o/s altogether.
Evidently Microsoft has attempted some patches and "fixes" for this issue already but so far none of them have worked for us and the updates do not correct the issue either.
It is what it is. We the consumers are the beta testers now. Quality control @ Microsoft is greatly wanting.
Agreed - and OEMs like Asus are often left holding the bag.
There is no known fix for this issue. I have tried countless attempts at correcting this problem and I am no novice.
My wife has the same issue with 22H2 on her PC we have tried to fix it to no avail.
I tried a rollback which resulted in completely totally destroying my o/s altogether.
Evidently Microsoft has attempted some patches and "fixes" for this issue already but so far none of them have worked for us and the updates do not correct the issue either.
It is what it is. We the consumers are the beta testers now. Quality control @ Microsoft is greatly wanting.