Beam gen2 stopped working with laptop via SPDIF all of a sudden; No stereo sound but Netflix apps and Dolby Digital testing works

I’m having the same issue and it’s been mentioned in these other two threads: 

I’d imagine this has somehow stopped working with a new firmware update or similar. I can’t imagine this won’t be fixed soon, as it both invalidates a previously working use case and the use of Sonos’ own optical->HDMI converter product. Any way one could use to get this to the attention of Sonos employees would be time well spent I think.

see also:

Transitionally I have established a PC connection

(Win11)>>>Sonos Roam (via bluetooth)>>>Group with Sonos Beam+2Play1

It delivers good stereo sound, but should be only a temporary solution as it is relatively laborious to use.

Is there a noticeable delay due to the Bluetooth+WiFi connection?

Also I can now confirm Netflix is working. So it seems Dolby Digital format works fine, but Sonos dropped the *regular* sound support?

@SmallhillCZ 

For me there is no remarkable delay, e.g. regarding lip synchronization in films or Windows operating sounds. But this probably depends on individual taste. It's best to try it yourself. If necessary, you can correct the audio delay in the app under TV dialogue synchronization.

Same setup. Same problem. Windows 10 and 11 both stopped working. Linux audio out via the CMedia sound card still works fine. This is 100% a Microsoft Windows issue. I have to admit that the previous CMedia driver was resulting in a lot of blue screen of deaths crashes and it was time for them to do something about it. This is though not a good solution neither.

@ChrisSchan

The route from the beginning of the Toslink cable including the Sonos Beam appears to be without any problems in my system, since, as mentioned, an Android tablet delivers perfect sound via an HDMI/Toslink converter. And the error occurs independently on two Win11 PCs, alternating with two external sound cards, one of which was purchased new, the other has been in operation with Sonos Beam for three years without any problems. So I also thought of Microsoft as the malefactor, possibly coincidentally together with Sonos.

But:
Read BlueC1's amazing note in the Sonos Ray thread https://en.community.sonos.com/home-theater-229129/sonos-ray-optical-connection-stopped-working-any-ideas-6894106
However, his suggestion could not be verified by everyone. - And I need to know it exactly before reorganizing my 13 Sonos devices.😁

And:
I had reset my Windows 11 system to the status as of May 1st (probably a point before the sound failure) using a backup - unfortunately without the hoped-for success. However, it may be that Windows immediately replaces old drivers with new ones when you switch it on....

@HPU 
I tested my setup (ID 0d8c:0102 C-Media Electronics, Inc. CM106 Like USB Sound Card, Sonos TOSLink  HDMI adapter, Sonos HDMI cable) on these setups.

• Windows 11 audio out is dead since about May 20th. [external usb sound card]
• Windows 10 audio out is dead since about the same date. Both coincide with Windows security updates. [external usb sound card]
• Ubuntu Linux  … audio just works fine. [external usb sound card]
• Sonos App on Android all works fine.

That’s the reason I’m very confident that this is not a Sonos issue. Otherwise my Linux setup would have stopped working too. And that’s the reason why i think trying to reset all Sonos devices will not work either.

I was actually thinking of getting a better Logitech external sound card as the driver of the C-Media one had been a source of constant Windows crashes (I only wiggled on the low quality USB cable of it and Windows crashed). But thanks for trying out this already. No need to waste money on this option.

Alternatively I was thinking of ditching the external USB card all together and use a monitor with built-in ARC/e-ARC support (i found only that the Samsung Smart Monitor M7 S43BM70 has ARC). But given the lackluster performance of it otherwise i’m not convinced by that.

@ChrisSchan 

I don't know enough about the specific technology in the depth. I noticed in passing that factors like compression and codecs can play an important role. Maybe the output on Win and Linux is different in this regard? - I actually notice an optical output signal with my eyes. What should it be?

I will be discussing the topic with Sonos Support for some time and will also contact Microsoft.

Don't you believe in the positive result of BlueC1?
Wouldn't you be satisfied with my interim solution with Bluetooth described above?

@HPU 
I checked the codecs i used in Linux. They are not different from those used in Windows. PCM uncompressed, AC3, etc. There is really no difference there. I think going via MS support might help, but they might reject working with the C-Media device drivers.

I do believe that BlueC1 found the right combination of firmware reset to get the Sonos Ray back working. I just do think that the case of the Sonos Ray is different, as the TOS-Link connection on the Sonos Beam is still working and there is a problem in Windows of accepting the correct parameters or drivers to work with an external sound card. The reason why i think so is that it is just working fine with a different OS (Linux or Android … which is a Linux system).

In addition to my suggestion from two weeks ago: I bought a Bluetooth/SPDIF adapter (available for as little as 11 euros) that worked straight away. This saves the hassle of creating groups every time you switch PC on. Good 2-channel stereo sound, good lip synchronization. I'm not expecting any quick help from Sonos or Microsoft anymore.

oddly enough I can play audio from windows media player ONLY and i can only change audio using the sonos app - not build in windows volume slider… VERY frustrating.

The windows updates in the last 2 weeks have fixed the driver compatibility issue. It's now working again for me in Windows 10 & 11. No more restrictions and so far no more crashes. 

@ChrisSchan

Thank you for your good information. I immediately checked it on my system, and it worked!
You were always convinced that MS was at fault, and you were right.
As I mentioned, I had set up a Bluetooth alternative in the meantime and had actually gotten used to it. But I have now gone back to the old configuration.
The whole process puts a spotlight on the questionable experts, both at Sonos and at MS. Of course, I don't expect them to identify every rare coincidence, but overall I felt very alone.