This error is caused by registry key permissions. The first thing I did was to go in and change the permissioning to everyone on the key(s) it was not able to write to. This did no good. To get right to the solution after much more troubleshooting, I ended up deleting the Key and subkeys under the CLSID. This was the only way I was able to resolve the issue. I am not saying to delete every key under CLSID, but only the one specified in the error message and its subkeys. This resolved the issue and caused no other issues with the rest of the office suite. I would recommend backing up the key before doing this.
31 October 2013
Home »
» Microsoft Lync 2013: Error 1406 Could not write value to key
Microsoft Lync 2013: Error 1406 Could not write value to key
Related Posts:
Optiplex 9010 Blue Screen during driver installation Recently, I went through and updated the drivers for the Optiplex 9010 from Dell's enterprise driver site. I then imported the drivers into MDT and imaged a 9010. When the system started to install the devices, it crashed. A… Read More
SCCM and MDT Master Kill Switch With the advent of mass deployment errors such Emory University and CommBank, there needs to be a master kill switch. I also read several months ago about a University in one of the Scandinavian countries that… Read More
Microsoft Ignite Guide for First Time Attendees I have been coming to the Microsoft Ignite convention since it's inception in 2015. The first conference held in Chicago had a lot of fallacies. It was the first time Microsoft had combined the conferences into one. Since th… Read More
Infineon TPM Vulnerability Report using SCCM (CVE-2017-15361) This weekend, I listened to Security Now's KRACKing WiFi podcast Episode 633 where they discussed the TPM vulnerability. Finding out exactly what to look for was tedious. I finally ran across Lode Vanstechelman's … Read More
Fix for A connection to the deployment could not be made This error is very annoying when running through a build. I Googled and found this fix to it by Kyle Beckman. The trick is delaying the LiteTouch.wsf from trying to execute the next task before network connectivity is … Read More
Could you please share the CLSID resides Lync Registry path
ReplyDelete