Written in 2011 – http://myitforum.com/myitforumwp/2012/06/19/resolved-microsoft-office-copy-and-paste-stopped-keeping-source-formatting-if-skype-click-to-call-is-installed/
I noticed recently that my copy and paste in Microsoft Office 2010 stopped keeping the source formatting. It was only allowing the paste of text only. If you were to check for paste special it would show only a capital A.
I noticed that if you closed all internet browsers except Firefox the issue would resolve.
Turns out SKYPE Click to Call Plug in is causing the issue
Ran into a lot of DCOM (DistributedCOM) errors on Windows 10 machines after upgrades. Looks like the TrustedInstaller from a previous application and the RunTime Broker did not give System and Local Administrators permission during a Windows 10 upgrade. It just an annoying thing but also slows down a windows 10 Login.
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
It would appear that an Apple application was installed on these machines at some point and that it did not do a proper install. The W10 upgrade exacerbated the issue due to missing security accounts after a W10 upgrade. The fix is to give local administrators and System rights to the DCOM. To do this you have to modify premissions on two registry keys and then change the DCOM premissions. Pretty easy to do.
Regedit Take Ownership
You will need to take ownership then set rights against two different keys. The keys are:
The silent upgrade of Windows 10 is dependent upon matching languages. This may seem obvious when thinking about English versus French. How about US-EN (409 or 1033) versus EN-GB (2057)? Turns out that the CB, CBB, etc version you download will really matter. As the error provided by SMSTS logs are opaque to say the least. Mike Terrill discovered the issue by running the upgrade in a loud (non silent) mode.
Unfortunately this means that you need even more versions of the ISO on your Distribution Points.
The WQL query for checking the language upgrade for EN-US
select * from Win32_OperatingSystem where OSLanguage = "1033" and OSArchitecture = "64-bit"
The WQL query for checking the language upgrade for EN-GB
select * from Win32_OperatingSystem where OSLanguage = "2057" and OSArchitecture = "64-bit"
The Percent complete of the Task Sequence popup rounds up.
I discovered this working through testing Windows 10 upgrade and bare metal. That means Microsoft thinks any action is at least 1%. it also means that an action is not complete until 101%. This explains why so many progress bars in the past showed 100% complete yet they are not. I wonder if anyone knows the reasoning and background story.