How to get Microsoft to resolve driver issues

AshForeth · 2025-02-06T08:36:35-0500

After the Windows 11 24H2 update, my Mic no longer work reliably. I have verified that the Mic continues to work on Windows 11 23H2 and Windows 10. I have also tried the usual debug like reinstalling drivers and disabling usb power management.

The Mic uses the OS usb drivers so there is no drivers on the manufacturer. I did contact the manufacturer, but they claim that this is a Microsoft issue because the Mic is a class compliant device. Here's my question,

How do you report this issue to Microsoft. I have use Feedbak hub, but I wonder if no one will respond unless there is a sufficient number of complaints.
Shouldn't the manufacturer work with Microsoft to resolve this issue, their mic is still on sale on Amazon. Sales will probably drop if it's gets reported in the review that it doesn't work with Windows 11.

spapakons · 2025-02-06T08:47:46-0500

See the installed updates. Those installed at the middle of January are known to cause such issues. Uninstall them and restart. You can hide them (block them) so they won't install again using Windows Update Show/Hide Tool or Windows Automatic Updates Manager (WAU Manager), both available at Major Geeks.

thecaretaker · 2025-02-06T08:50:28-0500

Are you able to uninstall the last preview windows update. It is known to have broken a few things. Then wait and hopefully MS will find a fix in the next update.

spapakons beat me to it!

neves · 2025-02-06T08:54:10-0500

Reverting back to Windows 11 23H2 - is the only reasonable solution. This build is still supported by Microsoft for the upcoming year. There's 400 millions devices using Windows 11 - and thousands of builds. For the sake of fairness (to everyone) - Microsoft devs - will (presumably) treat every driver issue by turn.

If you're asking for special privileges (taking the colossus amount of work into account), then what can i say... personally, i don't know anyone at Microsoft who has high enough authority or any of the dev handling drivers - to treat your case at a nepotism level. Point being - you'll just have to wait in the longest line in driver dev history. Since i am aware - that Windows 11 build 24H2 has tons upon tons of issue to resolve. Not really sure - the whole year will be enough to fix every particular issue (yours included). That's why - reverting back to build 23H2 - seems to be the most reasonable approach.

Just my 2 cents.

AshForeth · 2025-02-06T09:00:42-0500

I did uninstall the last update, but the issue did not go away. I kept uninstalling all of the 24H2 update until only 24H2 was left. The issue still presist. I am unable to go back because the laptop comes with 24H2 preinstall. I would have to reinstall evrerything from scratch.

What I did was try the same thing on a different computer with 24H2. I first verify that the mic is not working, then roll back each update just like on the first machine. Eventually things started working when I go back to 23H2.

One thing I notice is that rolling back updates on the first machine cause all sort of additional problems. The machine starts to have problems with the thunderport 4 hub. Whenever I leave the machine and come back later, the thunderbolt hub is disconnected and needs to be plug back in and it used to work before the rollback, so rolling back isn't a great solution, it causes more problem since my entire hub no longer works and not just the mic.

I am curious, how do you get Microsoft to fix these issues?

hsehestedt · 2025-02-06T09:18:21-0500

For the Thunderbolt issue, try disabling Fast Startup to see if that makes a difference.

Control Panel > Power options > Choose what the power buttons do > Change settings that are currently unavailable > Uncheck "Turn on fast startup" > Save changes

On the Mic issue...

You may have done this already, I just want to be sure. Did you go into Settings > System > Sound > Choose a device for speaking or recording > click on your device > Start test

What results does that give you?

If you want to report to Microsoft, select Start > All apps > Feedback Hub

Kees · 2025-02-06T09:24:45-0500

AshForeth said:
I am curious, how do you get Microsoft to fix these issues?

To my simple opinion: You will not be able to get MS to fix it on a personal complaint basis!
There are millions of Windows users in the world.
Would you expect MS to listen to every single user-complaint?

When I have troubles after some update of the Windows system, one of the first things I do is restore the system image I always make before doing a major update. By which the problem almost always is cured (at least for the time being) and I know I indeed have to find the cause in the update.

But I suppose you don't have the habit of making system backups?

AshForeth · 2025-02-06T09:28:14-0500

neves said:
Reverting back to Windows 11 23H2 - is the only reasonable solution. This build is still supported by Microsoft for the upcoming year. There's 400 millions devices using Windows 11 - and thousands of builds. For the sake of fairness (to everyone) - Microsoft devs - will (presumably) treat every driver issue by turn.

If you're asking for special privileges (taking the colossus amount of work into account), then what can i say... personally, i don't know anyone at Microsoft who has high enough authority or any of the dev handling drivers - to treat your case at a nepotism level. Point being - you'll just have to wait in the longest line in driver dev history. Since i am aware - that Windows 11 build 24H2 has tons upon tons of issue to resolve. Not really sure - the whole year will be enough to fix every particular issue (yours included). That's why - reverting back to build 23H2 - seems to be the most reasonable approach.

Just my 2 cents.

I agree with you, but is wondering what is the proper way of reporting these issue to Microsoft. Is feedback hub the way to do this? How would Microsoft for example know that there is an issue.

As for special privilege, I am wondering if manufacturer have more priority since their product will not sell if they don't work?

AshForeth · 2025-02-06T09:32:11-0500

Kees said:
To my simple opinion: You will not be able to get MS to fix it on a personal complaint basis!
There are millions of Windows users in the world.
Would you expect MS to listen to every single user-complaint?

When I have troubles after some update of the Windows system, one of the first things I do is restore the system image I always make before doing a major update. By which the problem almost always is cured (at least for the time being) and I know I indeed have to find the cause in the update.

But I suppose you don't have the habit of making system backups?

Thanks, my question remains.

What is the proper way to report an issue to Microsoft Feedback hub?
Should I pressure the manfacturer to pressure Microsoft to fix the issue?

I do backup daily, but you can't restore to a version that never existed on a new computer. The computer came with 24H2, I would probably have to reinstall. It took like 3 days to reinstall all of the apps, it may be easier to just get a new and different Mic if I can't get the manufacturer or MS to get it fix.

AshForeth · 2025-02-06T09:36:13-0500

hsehestedt said:
For the Thunderbolt issue, try disabling Fast Startup to see if that makes a difference.

Control Panel > Power options > Choose what the power buttons do > Change settings that are currently unavailable > Uncheck "Turn on fast startup" > Save changes

On the Mic issue...

You may have done this already, I just want to be sure. Did you go into Settings > System > Sound > Choose a device for speaking or recording > click on your device > Start test

What results does that give you?

If you want to report to Microsoft, select Start > All apps > Feedback Hub

Thank for the suggestion. Yes, Fast Startup has been disabled.
Also tried

Replaced cable.
Use different port, use a hub in-between.
Use different compouter.
Verified that device appear in sound manager and is set to default.
Verified that device has permission.
See if there are settings in bios that might fix the issue.
Delete devices and let windows reinstall.
Change power management to not disable USB by usb selective, and also power managment in device manager.

The MIc always work until there is inactivity and then the driver stops getting any input. I have never seen this behavior before.

neves · 2025-02-06T10:18:39-0500

AshForeth said:
I agree with you, but is wondering what is the proper way of reporting these issue to Microsoft. Is feedback hub the way to do this? How would Microsoft for example know that there is an issue.

Again, taking into account the huge number of people - with a similar build like yours (if not identical) - and same issue, there's probably enough reports as we speak to be taken into account. The fix - will be included in the monthly cumulative updates (maybe even the preview). So if you still wanna use 24H2 - just check each month and eventually - will work again (maybe even next patch).

AshForeth said:
As for special privilege, I am wondering if manufacturer have more priority since their product will not sell if they don't work?

They usually work together - it's the manufacturer who covers the updates - Microsoft will simply test them. But if it's a generic USB device - then it's something only Microsoft can/will solve. The manufacturer has no saying in that - since it's not custom made by them - so it doesn't need OEM (custom made) drivers.

hsehestedt · 2025-02-06T11:07:53-0500

AshForeth said:
The MIc always work until there is inactivity and then the driver stops getting any input.

When you say that there is inactivity, may I just ask for a little more detail? Does the period of inactivity go up to the point where the system enters sleep? In other words, I want to understand if the issue happens only when resuming from sleep.

pietcorus2 · 2025-02-06T11:14:20-0500

Tried this upgrade several times ( from 23H2 to 24H2) .
Still searching for a solution for the very slow booting , in 23H2 only 16 seconds , immediately after " welcome" , into 23H2 !
In 24H2 Im getting a black screen ( after "welcome" ) for about 30 seconds ...............!!
So the boottime went from 16 to 70 seconds !
Not funny watching a black screen , before opening 24H2 ............ :grrr:

Anyone faced this problem also , and has a solution ?
This booting problem keeps me in 23H2 , untill a fix will appear .........

hsehestedt · 2025-02-06T11:16:25-0500

On more idea to help me do some research:

Open Device Manager, right click the mic and select properties, go to the details tab. Under the heading "Property", select "Hardware Ids". Grab a screenshot.

Thanks!

How to get Microsoft to resolve driver issues

Member

My Computer

Well-known member

My Computers

Well-known member

spapakons beat me to it! ​

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Member

My Computer

Member

My Computer

Member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

spapakons beat me to it!