# Roon Extension Manager v0.11.9 \[Obsolete\] **URL:** \ **Category:** Roon API\ **Created:** [June 5, 2017, 9:50am UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632 "2017-06-05T09:50:08Z")\ **Posts on this page:** 1\ **Showing post:** 40
**Author:** ![Jan\_Koudijs](https://community.roonlabs.com/user_avatar/community.roonlabs.com/jan_koudijs/32/48346_2.png) [@Jan\_Koudijs](https://community.roonlabs.com/u/Jan_Koudijs)\ **Post date:** [September 17, 2017, 9:32am UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/40 "2017-09-17T09:32:59Z")
> [@Roon Extension: Roon Web Controller v1.2.0](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/68): > > There is only one core, running an an HP MicroServer Gen 6 running Windows 10 Pro 64bit. > RoonExtensions are installed on the same server. > Here is the logfile. Hi @seagull, Your issue has similarities with the one Geoff had, so I would like to follow up the discussion here (also not to hijack the Web Controller thread). Looks like the Harmony extension got corrupted. Can you try the following to recover from this? - Type services in the Windows search bar and open the Services application - Select the Roon Extension Manager in the list and stop it - Delete the extension manager log file, it has become big - Type cmd in the Windows search bar and open the Command Prompt application - Update the harmony extension: `npm update -g roon-extension-harmony` - Check if the update is successful, it should print a hierarchy of node modules - Start the extension manager service again Please supply me with the newly created log file if it still doesn’t work. I’m investigating how the system can get into this state, it might be triggered by a core that goes down… --- _[View the full topic](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632)._