Just realized that this could also be in 
Component:Internals>Installer>Components instead of Component:Internals>Media

thanks for the report clink2013@gmail.com. I just tried Beta x64 myself and found that it is stuck in "Checking for status..." and stuck there.  We are looking into what could be causing this.

In the mean time, might I suggest either Stable Channel or Canary? I've tested both, which are currently working (CDM downloads, updates, and NFLX works). 

I just installed "Version 49.0.2623.87 m" and now it:

1. WidevineCDM reports there is a New update
2. Click update
3. Update starts to download and then a couple seconds later it reads 'Component not Updated'

Deleted: screen.PNG 57.8 KB

	screen.PNG 57.8 KB View Download

'Component not updated' after a download means that an error has occurred when installing Widevine CDM. 

To understand more about the error we could turn on logging:
https://www.chromium.org/for-testers/enable-logging

@clink2013 : when you uninstall, do you also delete browsing data?  That should delete your user profile directory (defaulted to "c:\users\<yourID>\appdata\local\google\chrome\user data\")?  

if I uninstall & make sure to tick "Delete browsing data" checkbox (which deletes my user profile directory above), and reinstall beta, I get the CDM just fine.

I think there might be an issue w/your user profile. quit all of chrome (all chrome.exe processes should be terminated), delete the following directory ("c:\users\<yourID>\AppData\Local\Google\Chrome"), launch Chrome again, and try chrome://components. Chrome should succeed in downloading & installing the CDM.

NOTE: when I repro'd this, I failed to delete the old user profile directory. Stable channel (what I was on previously) is 32bit. Beta is 64bit -> I think this is what caused my problem (and yours).

@ericde I just uninstalled the the Stable and reinstalled the beta building. I made sure I selected the option to delete the browsing data.
I also went into the c:\users\<myID>\AppData\Local\Google\Chrome and deleted the folder, launched chrome and I produced the same result as in comment 4.

@sorin I have attached the file log of chrome_debug after turning on logging. This was done I tried @ericde solution.

Deleted: chrome_debug.log 184 KB

chrome_debug.log 184 KB View Download

Just tried Mac 50.0.2661.37 and I can update CDM from 866 to 885. I'll try on Windows now.

Tried Canary (M51) and Beta (M50) on Windows and I can get CDM 885 in both cases. It took about 4-5 seconds to update so it appears to be a bit slower than normal, but it works.

@xhw On the Beta (M50) and the Stable 49.0.2623.87 m it either gets stuck on "Component Not Updated" or "Checking for Status..." and leaves me at version 0.0.0.0

I'm going to try the Canary (M51) version now. Will post an update. 

Version 51.0.2687.0 canary (64-bit) Produced the same result. It left me with a "Component Not Updated". I have attached the chrome_debug log that I used to log the Canary version. 


I find this whole situation weird because I have never had this problem before and I've been using chrome for years. 

It sounds like there are two issues: getting stuck at Checking for Status... and Component Not Updated.

The log shows evidence of Component Not Updated. The component was successfully downloaded, verified, and unpacked, but could not be installed. This can happen for the following reasons:
(1) The hash file could not be written.
(2) The component manifest could not be read.
(3) The component version is invalid.
(4) The path to install to already exists and cannot be deleted.
(5) The install files could not be copied from the temp dir to the install dir.
(6) The installed CDM is incompatible with Chrome (module, interface, or host version is bad).¹
(7) The installed CDM does not contain the expected CDM file for the user's platform.

¹ericde@: Is there anything about the version of Windows in here?

I can't repro on Windows 7 64-bit (I don't have 10) using x64 M50 Beta; given that we serve the same CDM file and that it verified correctly on your system, I doubt there is an issue with the served payload. It seems more likely there's a situation with your user-data-dir (out of quota/disk, Chrome does not have write permissions, etc).

Assuming you do not have limited quota/disk,could you try running chrome with the following command-line flag?: --user-data-dir="C:\Users\%USERNAME%\TestChromeDataDir" and verify that you still encounter the issue?

One takeaway here for the dev team is that we need better logging about why the installation fails.

@Waff I have almost 500Gb free on my disk. I have also tried doing all of this when right clicking chrome and selecting to "run as administrator". 
I will try to run the command-line "--user-data-dir="C:\Users\%USERNAME%\TestChromeDataDir" but won't be able to until after I get back to my desktop. I'll post an update later.

Do you want me to attach anything after running chrome with that command line? 

Does this repro with the Chrome canary build?

We could land right away more logging statements to understand what is going on.

Thanks for helping us debug, we really appreciate it.

Trying with Canary is also an good idea. Canary will use a separate user-data-dir by default, so if the component can install using --user-data-dir, I expect it to also work in Canary.

If you experience the same outcome ("Component Not Updated"), there's no need to attach another log. If you do have a case where you get stuck at "Checking for Status...", I would be very interested to see a log for that run.

@sorin Last night I tried the Chrome canary build (see comment 12) and it produced the "Component not Updated" ... However, I just tried it on the same canary install from comment 12 and I was able to get it update the WidevineCDM to version  1.4.8.885

@Waff I just tried to run chrome 50.0.2661.49 beta-m (64-bit)with the command line "--user-data-dir="C:\Users\%USERNAME%\TestChromeDataDir" and it still would not update the WidevineCDM
 

I will land changes soon to facilitate more logging for the canary builds. However, it appears that the issue does not repro reliably in Canary, but it is worth a try.

At this point, I suggest we do the following: use a tool called procmon which can give us a trace of file system activity.

https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx

Would you be willing to give it a try? If yes, we can discuss how to set it up and what to look for. Then, you could email me a trace (be aware that it will contain privacy-sensitive data from the target computer) or we can analyze here, if we are successful setting the filters and tell you what to look for.

We also need to be careful not to lose this repro on the Beta channel.

Hm. I really expected a new user-data-dir to solve this problem. Did anything show up in that directory? (In particular, was a WidevineCDM folder created there and does it have any contents?)

Are you running any antivirus software that might be interfering with copying .dlls around or something like that?

@cfink2013 : per comment #17 - and assuming both the beta & canary builds are 64bit, could you try copying the c:\users\<yourID>\AppData\Local\Google\Chrome SxS\User Data\WidevineCDM folder over to c:\users\<yourID>\AppData\Local\Google\Chrome\User Data\, kill all Chrome processes, then restart Chrome and tell us it it picks up the CDM in chrome://components?  the version you have now for canary (1.4.8.885, 64bit) has been shipped down to M50/beta channel too and verified against M50 already to have worked by our QA.

@ericde I was able to copy the folder into the Chrome\user data\ and it worked that way. The beta chrome now shows that it is updated and Netflix does work. 
I suspect that if there is an update in the future it won't be able to update it thought(maybe i'm wrong).

@waff There was a WidevineCDM folder created but it does not have anything inside of it. I am currently running Symantec Endpoint Protection (required for internet access at University) but I did disable it yesterday and tried to update the WidevineCDM with no luck, so I re-enabled it. 

@sorin I will be willing to do it and email it to you, if it gives privacy sensitive data I rather not post it for the public. Should I go in and delete the WidevineCDM @ericde had me do?  

Thank you. I am glad it worked. Please let us know if we can repro again in Beta or Canary. I just landed code to output more logging from the installer. The logging will be available in the Canary channel first.

If we can repro again, then we can to procmon route, which can tell us which file system operation fail, and could help understand the installer failure.

@sorin I'm interested in going the procmon route to try and give you guys more information and to see why it doesn't install for me. 
I just deleted the WidevineCDM folder out of both the Canary user data folder and the beta user data folder and killed all chrome processes. 

Now it will not longer download the WidevineCDM for the beta or Canary build.

cfink2013: Do you still see this issue happening?

No response from the reporter. Mark as WontFix for now. Feel free to reopen if this still happens.