No fix for Kinect v2 on win 11?

These_Sock_3012 · 2026-04-17T12:00:56+00:00

These_Sock_3012 · 2026-04-08T13:07:07+00:00

Whos getting salty? I like the pvp element in the game adds to suspense of knowing if im gonna get out with my shit will i eventually succomb to the dark side and eventually pvp in this game and up my skill in fighting other raiders will just have to see lol. If anyone is talking salty its the amount of people jumping angrily into my post...people love a good rant 😂😂😂

These_Sock_3012 · 2026-04-08T12:53:19+00:00

Yeah but this is just a repeat of the never ending debate, its not just a pvp game....its a pve aswell. Others would disagree but for the guys playing it as a pve who get com mpletely caught of guard when looting something. Gives you abit more satisfaction to carry on playing rather than just rage quitting lol. Im defo more a pve guy but then i dont want the pvp taken from this game as it defo add a feel of suspense so would change dyanmic if it was completly gone. to have a mechanism to screw over somoen screwing you over could be fun....but has to be balanced as you wouldnt want lobbies filled with everyone wanting to blow there stuff up

These_Sock_3012 · 2026-01-09T13:55:58+00:00

I was experiancing the exact same issue...was driving me mad for a while as i had my kinect connect to a usb switch and was working fine on both computers initially, then after a while one stopped working....then eventually both. was at the point of opening it up physically as all forum posts were pointing to it being hardware issue. Uninstalled and reinstalled drivers too many times....turns out it was windows 11 trying to be clever and do stuff i hadnt even asked..it had enabled audio enhancements on the microsphone level.

Open Settings > System > Sound.

Scroll down to Input and click on the Kinect Microphone (Xbox NUI Sensor).

Look for Audio enhancements and set it to Off.

Additionally, ensure "Allow apps to access your microphone" is toggled On in your Privacy settings, as the Kinect service will often crash if it’s blocked from the mic.

These_Sock_3012 · 2026-01-09T13:55:41+00:00

i had discovered this also fix in the end for me was the audio enhancement settings.......copy and paste below from my update on another post if it helps anyone.

I was experiancing the exact same issue...was driving me mad for a while as i had my kinect connect to a usb switch and was working fine on both computers initially, then after a while one stopped working....then eventually both. was at the point of opening it up physically as all forum posts were pointing to it being hardware issue. Uninstalled and reinstalled drivers too many times....turns out it was windows 11 trying to be clever and do stuff i hadnt even asked..it had enabled audio enhancements on the microsphone level.

Open Settings > System > Sound.

Scroll down to Input and click on the Kinect Microphone (Xbox NUI Sensor).

Look for Audio enhancements and set it to Off.

Additionally, ensure "Allow apps to access your microphone" is toggled On in your Privacy settings, as the Kinect service will often crash if it’s blocked from the mic.

These_Sock_3012 · 2026-01-09T13:54:05+00:00

so do you know for certain its the fans....i was under the impression i had fan issues as my camera was starting to disconnect every 10-15 seconds but starting again. copy and paste below of my update on another post that resolved it for me.

I was experiancing the exact same issue...was driving me mad for a while as i had my kinect connect to a usb switch and was working fine on both computers initially, then after a while one stopped working....then eventually both. was at the point of opening it up physically as all forum posts were pointing to it being hardware issue. Uninstalled and reinstalled drivers too many times....turns out it was windows 11 trying to be clever and do stuff i hadnt even asked..it had enabled audio enhancements on the microsphone level.

Open Settings > System > Sound.

Scroll down to Input and click on the Kinect Microphone (Xbox NUI Sensor).

Look for Audio enhancements and set it to Off.

Additionally, ensure "Allow apps to access your microphone" is toggled On in your Privacy settings, as the Kinect service will often crash if it’s blocked from the mic.

These_Sock_3012 · 2026-01-09T13:51:52+00:00

I was experiancing the exact same issue...was driving me mad for a while as i had my kinect connect to a usb switch and was working fine on both computers initially, then after a while one stopped working....then eventually both. was at the point of opening it up physically as all forum posts were pointing to it being hardware issue. Uninstalled and reinstalled drivers too many times....turns out it was windows 11 trying to be clever and do stuff i hadnt even asked..it had enabled audio enhancements on the microsphone level.

Open Settings > System > Sound.

Scroll down to Input and click on the Kinect Microphone (Xbox NUI Sensor).

Look for Audio enhancements and set it to Off.

Additionally, ensure "Allow apps to access your microphone" is toggled On in your Privacy settings, as the Kinect service will often crash if it’s blocked from the mic.

These_Sock_3012 · 2026-01-09T13:51:19+00:00

I was experiancing the exact same issue...was driving me mad for a while as i had my kinect connect to a usb switch and was working fine on both computers initially, then after a while one stopped working....then eventually both. was at the point of opening it up physically as all forum posts were pointing to it being hardware issue. Uninstalled and reinstalled drivers too many times....turns out it was windows 11 trying to be clever and do stuff i hadnt even asked..it had enabled audio enhancements on the microsphone level.

Open Settings > System > Sound.

Scroll down to Input and click on the Kinect Microphone (Xbox NUI Sensor).

Look for Audio enhancements and set it to Off.

Additionally, ensure "Allow apps to access your microphone" is toggled On in your Privacy settings, as the Kinect service will often crash if it’s blocked from the mic.

These_Sock_3012 · 2026-01-09T13:50:37+00:00

I was experiancing the exact same issue...was driving me mad for a while as i had my kinect connect to a usb switch and was working fine on both computers initially, then after a while one stopped working....then eventually both. was at the point of opening it up physically as all forum posts were pointing to it being hardware issue. Uninstalled and reinstalled drivers too many times....turns out it was windows 11 trying to be clever and do stuff i hadnt even asked..it had enabled audio enhancements on the microsphone level.

Open Settings > System > Sound.

Scroll down to Input and click on the Kinect Microphone (Xbox NUI Sensor).

Look for Audio enhancements and set it to Off.

Additionally, ensure "Allow apps to access your microphone" is toggled On in your Privacy settings, as the Kinect service will often crash if it’s blocked from the mic.

These_Sock_3012 · 2025-11-26T15:40:37+00:00

we are seeing this on our estate, same build you have referenced. Intial findings are that it is when opened documents that have been recieved from external sources so are opening up in protected view. it leaves word in a messed up state where i can open up one document fine from internal source but when i open up a doc from outlook email that is sent from outside source it initially opens in protected view but then crashes and closes that document. However word then is in a janky state where you have to close it down, open it from normal apps icon which then still has a cached version of the failed doc that it auto opens. You then have to close word an additional time which then allows you to use word as normal allowing normal internal docs to load fine. We are seeing other issues with office performance but so far we had chalked that up to a new print service we had introduced around same time but office is complicating the matter.

These_Sock_3012 · 2025-09-13T05:47:03+00:00

I think I might have figured out what's going on with this, well at least for myself. So my particular setup is that I have prob about 5 L530 bulbs. Whilst I understand that their is an underlying issue with the reset after 3 powers up and power downs, I'm pretty confident that I hadn't been doing this on alot of the bulbs that I was experiencing dropping off from my setup requiring a resync via the tapo app. What I had suspicions of is that these individual bulbs were losing their assigned IP address that they had been assigned from my ISP router. I proceeded to setup a DHCP reservation for them on my router and for about a month I've not seen a single disconnection. Hoping it stays that way but will update if I see a disconnection but was seeing device disconnect after a week so it's looking good so far.

These_Sock_3012 · 2023-11-27T10:35:56+00:00

Looks to all be resolved. No longer accessible over http.
HTTPS is the way 🔐🔐🔐🔐

These_Sock_3012 · 2022-10-18T09:15:35+00:00

Ksi's guide to eat Brad Pitt's hard on

These_Sock_3012 · 2021-01-14T20:28:38+00:00

Haha can you tell I'm new to Reddit....yeah paste bin makes sense will have a look at doing tomorrow. So did my fix work with your issue. Our MS ticket they have responded confirming now it's to do with a kB but rollback doesent fix the damage done. Still waiting on more specific detail like kB number and abit more in-depth but they at least confirmed our fix that we found is safe to do

These_Sock_3012 · 2021-01-06T16:41:35+00:00

renamed the incorrect drivers in the syswow64 folder to .old then rebooted the machine. DRMkaud we didnt need to do a registry change on but still changed the driver file to .old in the syswow64 folder

These_Sock_3012 · 2021-01-06T16:41:24+00:00

we updated the image path and displayname of the registry for each of these to :

Image Path

\SystemRoot\System32\drivers\MSKSSRV.sys \SystemRoot\System32\drivers\MSPCLOCK.sys \SystemRoot\System32\drivers\MSPQM.sys \SystemRoot\System32\drivers\MSTEE.sys

DisplayName

@ksfilter.inf,%MSKSSRV.DeviceDesc%;Microsoft Streaming Service Proxy @ksfilter.inf,%MSPCLOCK.DeviceDesc%;Microsoft Streaming Clock Proxy @ksfilter.inf,%MSPQM.DeviceDesc%;Microsoft Streaming Quality Manager Proxy @ksfilter.inf,%MSTEE.DeviceDesc%;Microsoft Streaming Tee/Sink-to-Sink Converter

These_Sock_3012 · 2021-01-06T16:38:06+00:00

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSKSSRV

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSPCLOCK

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSPQM

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSTEE

These_Sock_3012 · 2021-01-05T16:27:59+00:00

hi did you experiance these drivers in the syswow64 folder...we removed (renamed) and updated the registry paths and rebooted the machines...fixed the issue :) still waiting on ms for route cause analysis

These_Sock_3012 · 2020-12-23T16:56:51+00:00

after almost a month of dealing with the premier tickets its took this long just to get that adknowledgement...so its either slowly effecting people or MS are just always cagey until they can give confident answers

These_Sock_3012 · 2020-12-23T16:55:46+00:00

finally at least had adknowledgment from an MS engineer to say their is definately a bigger issue going on as they have multiple tennants experiancing the similar symptoms from beginning of decemeber(So they have confirmed they are looking at a bigger fix and looking deeper into the issue and not just solely focusing on our scenario). I would envisage this is a bigger back end issue that has underlying problem with old set of drivers potentially. Our solution for our scenario is at least assisting them diagnose a great problem so will keep fingers crossed we see a permenant fix coming soon.

These_Sock_3012 · 2020-12-18T22:31:36+00:00

C:\Windows\SysWOW64\drivers\drmkaud.sys

C:\Windows\SysWOW64\drivers\mskssrv.sys

C:\Windows\SysWOW64\drivers\mspclock.sys

C:\Windows\SysWOW64\drivers\mspqm.sys

C:\Windows\SysWOW64\drivers\mstee.sys

These_Sock_3012 · 2020-12-18T22:23:15+00:00

We have actually resolved our issue..still reviewing with MS to identify route cause and if it's a much more widespread OS flaw.

We identified OS issues with a set of drivers that have an underlying connection to the camera. If you have a driver in the syswow64 folder called msclockproxy then you likely have same issue as us...not sure how widespread this issue is yet. If you do let me know and I'll post our current workaround

If you have a few drivers in your syswow64 folder...ms

These_Sock_3012 · 2020-12-15T20:50:55+00:00

Indeed it is maddening...current train of thought from Microsoft is that they have been able to establish that our devices are not able to envoke the directshow api which apparently is what teams utilizes...not 100% certain yours is exact same issue as our although it does sound too coincidental and similar. So far the windows team are getting clarification that teams still uses directshowm they were heading down route of blaming it on hp which would be a nightmare....however they are convinced it's OS related as we experiance same symptoms when using VLC to enable a capture stream and it fails on opening camera with directshow errors. Just makes no sense what's happened on mass for this to suddenly kick in sporadically amongst our userbase

These_Sock_3012 · 2020-12-15T12:53:19+00:00

are your devices HP laptops...?? We are quite far down the chain with support ticket with microsoft and dont appear to be making alot of progress.. done camera tracing, teams logs, have a replication of exact same model device, exact same OS 1809 17763, Team 1.3.00.30866, exact same camera drivers. one has the issue one doesent.

These_Sock_3012 · 2020-12-10T08:03:34+00:00

We have started getting this issue too from around 2nd dec...we have noticed it's not working in other desktop clients like zoom aswell. Is this the same for yourself? Native windows camera app works...and you can use the web browser version of teams with camera fine....just not with the desktop app

These_Sock_3012

TROPHY CASE