In my situation, using Chrome Remote Desktop on Chromebook, the following version  (50) shows the same problem: 

Version 50.0.2661.104 (64-bit) Platform 7978.76.0 (Official Build) stable-channel auron_yuna

The Chromebook OS on the stable-channel does not upgrade past the version shown. This is being experienced two Chromebook units, both from Acer.

Adding to my previous comment, this is a problem observed (by me) only with Windows 10. I tested it on two Windows 10 machines and one Windows 7.  Problem only shows on the Windows 10 units, however, not on the Windows 7.

Same problem with Windows 10 using Chrome Remote Desktop version 51.  Uninstalling the Chrome Remote Desktop Host program and reinstalling version 50 fixes the sound problem, but updating to version 51 causing the sound issues again.

I am having the same problem but with a Windows 7 host after version 50.

So I am having the same issue, as well as my friend. 

I am going to try to install an earlier version to see if that helps, looks like it helped a few others.

For reference, previous updates can be found in the C:\Program Files (x86)\Google\update\download\ folder.  Just look through the folders for the ChromeRemoteDesktopHost.msi file.  Mine was in {B210701E-FFC4-49E3-932B-370728C72662}\0.0.0.0\chromeremotedesktophost-50.0.2661.22.msi

Just remember to uninstall the old CRD Host program from Programs and Features, and disable Google update in services and task scheduler.  Then you can install the older version, and that will get it working until a newer update fixes the issue.

If anyone doesn't have the old install file, I have it shared here: https://www.dropbox.com/s/rwx3tsuljw297sq/chromeremotedesktophost-50.0.2661.22.msi?dl=0

https://www.dropbox.com/s/rwx3tsuljw297sq/chromeremotedesktophost-50.0.2661.22.msi?dl=0

This .msi resolved the issue.  Granted it is an older version and not as smooth video playback as the new update, but audio is back in. 

Please fix!!!

Having the same issue on chromebook (use to remote a win7 PC).
My chrome version:51.0.2704.84 m

I could still use it normally last time (about a month ago), please fix it :'(
thanks!

not getting sound via remote desktop app on my chromebook. I run 2 chromebooks and run windows 10 on my pc. very annoying. I loved the fact that I could get sound via remote desktop on my PC . A very great shame that this is gone. Please fix

I have one of my Chromebooks (the new Acer flip type touch screen) on the Developmental channel, awaiting the implementation of the Android apps (access to the Google Play Store). That Chromebook is one of the first four targeted to get the first implementation of the Google Play Store. The current version on the Dev channel is: Version 52.0.2743.32 dev (64-bit).  That version still does not have problem fixed with the Remote Desktop lack of audio.  Perhaps they are waiting for version 53 (it was slated for mid-June, but that one still has not arrived), which is where the Android apps will first appear. 

 Issue 482932  has been merged into this issue.

Sorry, it's definitely my fault. A bug was introduced by change https://goo.gl/SUJ5aT, and fixed by change https://goo.gl/X90D1A. This change impacted versions between 2675 to 2706. So M51 is impacted, M52 should be fine.

Verified Fixed in 52.0.2743.33

How do we go about to resolve the CRD audio issue now, then?

Is there an update the consumer needs to install? I'm assuming you mean Chrome version 52.... how do we update it?

Thanks!

Yes, I mean Chrome version.
We are now actively testing M52, and will release it as soon as we can.
Before M52 has been released, downgrade to M50 and disable Chrome auto update is a possible solution. Dakre18 posted a solution in https://productforums.google.com/forum/#!msg/chrome/59-pB4bAk0s/2Ekz9V6GAAAJ.

Again, really sorry about this inconvenience.

Thank you for the reply and providing the Chrome 50 version solution.

Do we know when M52 version will be available so we can update? 

According to Chromium calendar, https://www.chromium.org/developers/calendar, we will have M52 release in the first week of Augest.

I'm glad you discovered the issue and fixed it, but losing audio is a pretty severe regression. Is there the possibility of a fix for an earlier release so it doesn't take until August? I'm on a chrome pixel, I can't see any way to fix this problem. This is the first time I've ever had a regression really hurt when moving forward to the new version of chrome.

An August release seems strange, based on the consequences people experience with this bug. Surely, this update could be prioritized.  I have,also noted that the developmental channel has Verizon 53 out, but the remote sound problem persists, so whatever fix is in store for 52 is being bypassed in 53.  Maybe a memo to the 53 dev guys might be in order.

Unfortunately we do not have beta or dev channel for remote desktop host. So installing beta or dev Chrome won't update remote desktop host software. I am talking with my team member to see if we can also setup also a beta or dev channel for remote desktop host.

And to NickKline@gmail.com, this issue is about the Windows host software. So you could always fix the issue by downgrade your Windows host software. The client software version does not matter.

I'd like to add my voice to nickkl...@gmail.com* - this is a severe regression, it's a serious pain to not have sound in the remote desktop, and it seems ludicrous that no update is possible until July the 26th even though the problem has already been identified and fixed. Any update on getting CRD into the beta or dev channels? Or failing that, would it be possible to get the fix by compiling from source as per https://www.chromium.org/developers/how-tos/get-the-code? I'm getting a bit desperate here; I was planning on making heavy use of remoting (including sound) next month and now I'm going to have to look at alternate solutions. I already tried downgrading to M50 through the .msi file linked by a couple of users above, but the problem persisted.

* zijiehe, users can choose to hide their full email addresses from everyone except project members, so it's probably not a good idea for those members to refer to the full addresses in their replies. :)

Thank you for the feedback. I am pretty sure downgrading to M50 can actually resolve the issue. But you will need to uninstall the M51 first, otherwise installation won't perform.

For the release, the date I have mentioned is the public Chrome release cycle, Chrome Remote Desktop host may not always release together with Chrome. But unfortunately we cannot talk about the release cycle of Chrome Remote Desktop in public bugs. Considering this issue is serious, we will release as soon as we are ready. (We really do not want to release a version which fixes one issue, but introduces another.)

Regarding to the beta and dev channels, as I have just talked with my team senior members, they have discussed this before. Since we won't update host software too often, maintaining different channels is not worthy enough. We will release a new version once there is a critical issue or a new feature.

Regarding to build by yourself, yes, it usually works. Though we should not ask users to build the binary by themselves.

Also thanks for the hint about the email addresses issue.

Anyone have a suggestion how to prevent my Win 10 64bit machine from
refusing to install M50, even after thorough uninstall of M51?
It just INSISTS on diverting to the current version from the Google
website, even though I try to install M50 from an archive...

?!?

You may find something useful at http://superuser.com/questions/974766/turn-off-chrome-updates.

Thanks, but it is an install obstacle not an update issue ... I can't even
get M50 onto the machine, much less keep it there.
Oh well....

Oh, you mean, even after installed M50, remote desktop client still asks you to install the host software?

I finally got an OFFLINE installer (from slimjet.com) for Chrome Version
50.0.2661.75, and that installed on both my Windows 10 platforms, whereas
trying to install online did an under the covers update.  THEN the tricky
part ... in order to get the back version of CRD to actually install, I had
to download the CURRENT version of CRD from Chrome webstore AND, while it
asked me to click that file, click the .msi for
chromeremotedesktophost-50.0.2661.22
INSTEAD.

...go figure...

ANYWAY, I now have sound from that config of Chrome/CRD and with update
turned off can wait for Chrome Dev to get their act back together...

Whew!

Sorry for the trouble, we will release M52, which resolved this issue soon.

Never mind my earlier comment, I think it's working! Thank you devs.

I HAVE SMAE PROBLEM , I UPDATE CHROME ALREADY ,
BUT STILL CAN HEAR ANY SOUND ....

Relax Kuo...@gmail.com, M52 will be released soon. You can follow the instructions above to downgrade to M50, or just wait for several days for M52.

I'm wondering how far behind the update is for Chromebooks. I have version 52 available on Windows but not for my Chromebook. (I think the update might only be available for Linux, OS X and Windows if I've done my research right). I've been trying to downgrade everything to version 50 but honestly it's a huge pain and seems ridiculously difficult. I know that stuff happens where things break, and I know this might not be a huge priority, but could Google please make it easier to downgrade stuff in the future? That way when things DO break we have some recourse that doesn't involve disabling services or editing registries. 

downgrading to 50 is actually easier than one might guess.
I've posted both extractor for Chrome and .msi for CRD to my Dropbox via
the following link:

https://www.dropbox.com/sh/i7eobte7mtifgiu/AADlEGTJxShQgZZipVoKcJnta?dl=0

Install the appropriate 32/64 Chrome 50 via the offline installer provided,
and TURN OFF UPDATES ASAP!
Setup to install "current" CRD from the chrome website, but when it
downloads a .msi and asks you to click on it, click on THIS ONE instead. (I
know, weird right? ...but this is the only way I've found that works!)
Voila!  you're good to go.

BTW, Chrome will occasionally tell you you are out of date EVEN IF YOU HAVE
UPDATE TURNED OFF
Don't bite.

RAHjr

ridiculous. every browser and applicatiion but chromme works, of an hour ago. This is tarhetted specific denial of service, I intend to boycott. Fuck you google. stole 35£ from me last week and now you block sound

what? I have to waiting for chrome M52 ??

@______________@  

I can't believe it ...... 

It's been a month now with no sound, so hope 52 comes out soon.

Just FYI, M52 has been released. You can now upgrade your host software.

Thank you so much!, mine upgraded automatically and it was very nice to have sound back

i HOPE "we" have documented how this occurred and will avoid a recurrence
in the future, yes?

I'm going to keep my old versions around JIC ... and test this upgrade
THOROUGHLY.

Well Guess WHAT!

The current Chrome download is NOT 52!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

it is 51.0.2704.106 -- IS THE FIX IN THAT?
I DON'T THINK SO.

GOOD THING I kept my Version 50.0.2661.75 installed
I would have been VERY ANGRY to try to unstring this mess AGAIN this weekend!

Well I'm running 51.0.2704.7 and it works fine, watching youtube using CRD as I write this. Not sure why but it is working just fine :)

Yes, I today downloaded Version 51.0.2704.106 (64-bit) and it works perfectly in the tests that I have run.  I just now remotely accessed a Windows 10 computer, which previously did not transmit any sound (for the past month or so) and now it works perfectly. 

Looks like the problem has been solved. Excellent work by the programmers.

update fixed it hooray!

Still no sound for me on 51.0.2704.106 m.

This fix is in M52, i.e. you will need to install a host software with 52.* as version number. This should usually happen automatically with Chrome auto update system. But if anything blocks your update (the updater has been disabled via registry, for example.), you can always uninstall host software through Windows programs and features control panel, and reinstall by starting Remote Desktop app in Chrome and enabling host. It will download the latest host software for you.

I'm afraid I'm still not getting any sound after upgrading to host software version 52.0.2743.48 on Windows 7. My remote device is a Chromebook running 52.0.2743.75 beta (64-bit). I'll happily provide more information if necessary.

Hi, Olli*@gmail.com,
Thank you for your feedback. We did find Windows might report a different and always zero volume level for some specific hardware. (Or I have not found a correct way to get system volume level.) An example is Lenovo Thinkpad X140e, it will have two playback devices once a headphone has been plugged in. Remote Desktop host, or the Windows API used in Remote Desktop host can only get the volume of the default device. So by setting one of them as default, and reconnect to the host can resolve the issue.

Please kindly let me know if this is the issue you are facing.

Bug  http://crbug.com/628814  has been opened to track the issue caused by switching default audio endpoint during the remote connection.

zijehe, yes, that seems to be the issue I'm facing. Windows reports four audio devices on my host machine:

HDMI connection to TV
3.5mm connection to speakers
Realtek Digital Output (unused)
USB connection to microphone with headphone jack

Setting any of them except the speakers as my default audio device, and then connecting through CRD, produces audio on the remote machine. Setting the speakers as the default device does *not* produce audio on the remote machine, even after a reconnect. Kind of a pain, because that's my default device most of the time, but at least I know the workaround now.

I hope that helps. I can copy and paste it to the other bug report you linked to as well, if you like.

Thank you Olli*@gmail.com, glad to know this workaround partially resolves your issue. But it's do weird only the speaker won't work in your scenario. I may need to find a device to reproduce your issue. As we do not have too many log entries for Windows API calls; it works like a black box for us.

Just in case of any misunderstanding, we have enabled volume control in Windows host. So you always need to unmute and set the volume into a reasonable level in both client and host machine to enable sound playback. I believe this has not been documented, but the behavior is consistent across different host platforms.

Sorry ... I don't believe you, and don't care even if what you say is true.

I'm using version 50..
I do NOT need the volume up high on the source system, and I get volume
JUST FINE on the local system.

Let me know when the website downloads version 52.

...AND...

I sincerely hope the work around described above is NOT the "fix" you've
put in version 52!!!!!
Currently ANYTHING other than MUTE on the remote/source system is
sufficient to drive adequate volume on the local system when using version
50
In my case I can NOT have the volume loud on the laptop that is on the
cable while hearing it on the Big Screen AllInOne which is on the wireless.
I use my AllInOne basically as a monitor, having the small screen more
powerful laptop RJ45 internet connected
The person in THAT room does NOT want to hear MY streaming stuff going on
in their ear.

Nor can I image that ANYONE READING THIS FORUM wants their stuff playing
loud on the system they are remoting into, right?

On 52.0.2743.75 beta-m (64-bit) now.
Sound still isn't working for me. 

Actually, I was having the same problem as above. My audio is going out to speakers through the motherboard audio (Realtek). Don't get audio using this configuation. Changing to my TV HDMI audio output as default and reconnecting it fixes it. Inconvenient but it works. Thanks!

Thanks to both Olli*@gmail.com and Pixel*@gmail.com, I will try to find a hardware to reproduce the issue you have mentioned, and see if anything we can do.

This could be  bug 628814 , which relates to output on Windows 10 on headphone, but could be a general issue with outputs on a Windows 10 device. 

My sound has stopped working and have no idea why.  How do I restore it? using hp chromebook bought 1 year ago

Hi, Kathy*@gmail.com,
Which kind host are you using? A Windows or Linux or Mac?
If the host is Linux, it won't be impacted by this bug. If the host is Mac, we do not support audio capturing in Mac now.
If the host is Windows, (since you have asked this question, I believe it should be able to work before.) have you updated your host software to 52.*? A known issue in 51.*, as discussed in this thread, blocks audio capturing. So you won't be able to receive sound from client with 51.* host software.
If you have already used 52.* host software, you may want to tune the audio volume level in both client and host, as this is a new feature in 52.* to make host software respect system audio volume level. (For full screen users, controlling audio volume directly from host machine is important. And this change also makes sure Windows host has a consistent behavior with Linux hosts.)
Olli*@gmail.com and Pixel*@gmail.com also mentioned for a certain hardware configuration, you may need to switch the default audio output device to something other than speaker and reconnect to get audio output. I am trying to reproduce the issue.

Hi, does anyone know if CRD works fine from Windows 10 Desktop PC hosting out to an ASUS Chromebook (I have an ASUS C300 to be more precise)?

I've done the rollback to version 50 as well as disabling all automatic updates in the registry as per a suggestion on this thread a few weeks ago and everything is working just fine. I was informed that this was the workaround until version 52 was released. 

But as per reading some of the comments here, I am afraid to update in case the sound won't work again :-(

If anyone tested it or can answer, it would be appreciated.

Thank you.

I wish Google DEV would please PUT THE MOUSE DOWN AND STEP AWAY FROM THE
COMPUTER!
...and please STOP changing interim conditions, ESPECIALLY chaning the way
volume has to be handled on the source system.

It IS REALLY STUPID to require turning up the sound on the source system
bothering whoever is in THAT ROOM just so you could hear it local to you,
don't you think?
If the source system is at work, your co-workers will NOT thank you for
doing this.
If the source system happens to be in the nursery where your internet
outlet is, your spouse is going to KILL YOU for waking the baby just so you
can stream stuff to your office.


THE WAY IT WORKS IN V50 IS JUST FINE, and it had better work that way again
in v52 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
In V50 one does NOT have to turn up the volume on the source system ...
ANYTHING OTHER THAN MUTE WORKS SWELL! ... and the volume one hears is
whatever you want on the local system.

SO PLEASE STOP TELLING US IT WORKS, since the website download v51.
AND PLEASE MAKE SURE IT WORKS THE SAME IN V52 THAT IT DOES IN V50!

It is bad enough that you broke it in the first place, but it is ABSOLUTELY
MADDENING that you would confuse EVERYONE about what state one gets in
Update.and how that works compared to V50

Is there PLEASE an adult in the room at Google DEV who can make this
madness STOP?

The change in behavior in M51 was intentional, see  bug 276753 . This is obviously a trade-off. There are many users who prefer the new solution.
Please open a separate issue if you are not happy with the way audio works in the current version, no need to spam this bug.